Search Issue Tracker
By Design
Votes
0
Found in
2022.3.65f1
Issue ID
UUM-113303
Regression
Yes
Color grading and texture rendering issues while in Play Mode in a specific project
Reproduction steps:
1. Open the attached “repro_IN-85043“ project
2. Open the “Assets/Core/Scenes/Main.unity“ Scene
3. Enter the Play Mode
4. Once the main screen of the game loads, press any key and select “Start“
5. Observe the loaded screen
Expected result: Background image and the image inside the circular border in the bottom-right is displayed
Actual result: Background image is jittered and the image inside the circular border in the bottom-right is not displayed, instead a solid black color is shown
Reproducible with: 3.4.0 (2021.3.44f1, 2022.3.49f1, 6000.0.22f1)
Not reproducible with: 3.3.0 (2023.2.0a20)
Reproducible on: Windows 10 (22H2), Windows 11 (10.0.22631) (user’s)
Not reproducible on: No other environments tested
Notes: Not possible to test the Player as the build executable asks for a Steam account with a license
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Thanks for reporting this and sharing the details! This behavior seems to be a side effect of the recent fix for the issue “Fixed grid gizmo is visible through geometry when Post Process Layer is enabled.”
(https://docs.unity3d.com/Packages/com.unity.postprocessing@3.5/changelog/CHANGELOG.html#340---2023-12-11)
In the editor, the OnRenderImage API does not use the ImageEffectUsesCommandBuffer attribute. Rolling back the previous fix would unfortunately bring back the original grid gizmo problem, so instead, we’d recommend trying the following workarounds:
1. Portrait rendering issue
Disable the Directly to Camera Target option in the PostProcessLayer.
2. Background jittering issue
This is caused by a change in depth format precision. When ImageEffectUsesCommandBuffer is disabled in the editor, the depth format changes from D32S8 to D16. Manually setting the render texture’s depth buffer format to D32 should prevent this.
We hope these steps help you move forward without reintroducing the previous issue. If you have any more questions or run into anything else, please don’t hesitate to reach out!