Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0f3
Issue ID
1006954
Regression
No
Some Command Buffers are not rendered in the Frame Debugger right after opening the project
How to reproduce:
1. Open attached Unity project "WetSurfaceDecals"
2. Select WetDecals --> Decal1 in the Hierarchy window
3. If there is wet effect on the selected object, reopen project until it disappears
Expected result: Armchair looks like it is wet (1006954_Expected1.png). In the Frame Debugger all three Command Buffers are rendered (1006954_Expected2.png).
Actual result: Wet effect is not visible on the "Aermchair_old" gameobject (1006954_Actual1.png). In the Frame Debugger only two Command Buffers are rendered (1006954_Actual2.png).
Workaround: Disable and enable Main Camera.
Reproducible with: 2018.2.0a3, 2018.1.0b10, 2017.3.1p3, 2017.2.2f1, 2017.1.3.p2, 5.6.5p2.
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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Resolution Note:
Minor / rare