Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a11
2019.1.0a15
2019.2.0a1
Issue ID
1119019
Regression
Yes
[Frame Debugger] Incosnistent elements are drawn when previewing the same draw calls
Repro steps:
1. Open attached project "FrameDebuggerBug_2018.3.3f1.zip" and scene "SampleScene"
2. Enter play mode
3. Open the "Frame Debug" window and press the "Enable" button
4. In "RenderForward.RenderLoopJob", select its children and observe Game View
Reproducible with: 2019.1.0a11, 2019.1.0b1, 2019.0a2
Not reproducible with: 2017.4.19f1, 2018.3.3f1, 2019.1.0a9
Could not test with: 2019.1.0a10 (redirects me straight to 2019.1.0a6)
Notes:
- The issue is even more obvious with the transparent queue (TransparentQueue.mp4), but this cannot be previewed until bug #1107382 is resolved.
- Tested with the built-in render pipeline
- Can't get it to repro as easily in 18.3, and the draw order seems to have changed (Order.jpg attached). Trying upwards of 30+ times, sometimes the transparent purple cube shows, but it's very rare.
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note (2019.2.X):
The frame debugger works by replaying the scene and stopping rendering at a certain place. If something has changed in the flow (batching slightly differnt ect) then the result will be different. That is what is happening here.