Search Issue Tracker
By Design
Votes
1
Found in
2022.3.19f1
2023.2.8f1
2023.3.0b4
6000.0.0b11
Issue ID
UUM-62384
Regression
No
Visual glitches in the material's Preview window and Game view flickers when having a shader graph fullscreen material selected
Reproduction steps:
1. Open the attached “Repro“ project
2. Open the “Assets/Scenes/“ Scene
3. Select the “Fullscreen Effect Samples Showcase” GameObject in the Hierarchy
4. Change the Fullscreen Effect to “Custom Night Sky“ in the Inspector
5. Select the “Assets/Samples/High Definition RP/14.0.10/Fullscreen Samples/CustomRenderTargets/NightSky_Material.mat“ Material in the Project window
6. Observe the Game View and the Inspector’s Preview window
Expected result: Game View doesn’t flicker, Material is clearly displayed in the Preview window
Actual result: Game View flickers, visual glitches are seen in the Preview window
Reproducible with: 2022.3.19f1, 2023.2.8f1, 2023.3.0b4
Couldn’t test with: 2021.3.34f1 (couldn’t downgrade)
Reproducible on: M1 MacOS 14.2
Not reproducible on: No other environment tested
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.