Search Issue Tracker
By Design
By Design in 2020.3.X
Votes
1
Found in
2020.3.40f1
Issue ID
UUM-15984
Regression
No
Render Feature causing black screen only on some iOS devices
How to reproduce:
1. Download and open the attached "FogErrorTest" project
2. Build and deploy the project to iOS
3. Observe the screen
Expected result: The screen is not black
Actual result: The screen is black
Reproduced with: 2020.3.40f1, 2021.2.19f1, 2021.3.11f1, 2022.1.17f1, 2022.2.0b8, 2023.1.0a12
Reproduced with: iPhone 6S (iOS 13.3.1)
Not reproducible with: iPhone 12 Pro (iOS 15.6.1)
Comments (1)
-
F11B0T
Oct 11, 2022 22:48
Confirmed this bug not happening either on iPhone 7 or iPad Pro 2nd (they use same chip generation), so it should be a bug for only iPhone 6s or lower based chips.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Duplicated groups and incorrect grouping in UI Builder when using UxmlElementAttribute: libraryPath
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
- Crash on UNITY_FT_Render_Glyph_Internal when Generating Font Atlas in the Font Asset Creator Window
Resolution Note:
The project shows an error message "You can only call cameraColorTarget inside the scope of a ScriptableRenderPass. Otherwise the pipeline camera target texture might have not been created or might have already been disposed."
This is likely the cause of the perceived issue. Please reach out again should the issue persist after fixing the error
Resolution Note (2020.3.X):
The project shows an error message "You can only call cameraColorTarget inside the scope of a ScriptableRenderPass. Otherwise the pipeline camera target texture might have not been created or might have already been disposed."
This is likely the cause of the perceived issue. Please reach out again should the issue persist after fixing the error