Search Issue Tracker
By Design
Votes
0
Found in [Package]
7.0.0
Issue ID
1171013
Regression
No
[LWRP] Different rendering order in Scene and Game view when endCameraRendering is used
How to reproduce:
1. Open the attached project named Case_1171013
2. Open the SampleScene
3. Observe the Scene view, notice that the Spheres are behind the wall
4. Open the game view
Expected result: Spheres are rendered behind the wall as in the Scene view
Actual result: Spheres are rendered in front of the wall
Reproducible with: 2019.1.12f1(5.16.1), 2019.2.0b10(6.9.0), 2019.3.0a11(7.0.0)
Could not test with: 2017.4.30f1(No PackageManager), 2018.4.5f1(Some of the SRP methods used in the script were not available)
Package versions tested: 5.7.2, 5.9.0, 5.16.1, 6.5.2, 6.5.3, 6.7.1, 6.9.0, 7.0.0
Possible workaround: Changing camera's MSAA setting from "Use Pipeline Settings" to "Off"
Notes:
1. When 6.9.0 was used spheres would not render in the Game view and Camera Preview(Track_1171013_V1)
2. When 5.7.2 was used spheres would render in Game view and Camera Preview but would have different ordering(Track_1171013_V2)
3. Disabling MSAA in the camera settings seems to fix the issue
4. After MSAA is re-enabled Editor starts throwing "Setting anti-aliasing of already created render texture is not supported!" errors
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
- Only the left screen is rendering when using Render Graph Fullscreen Blit in Meta Quest 2
- Context menu with the "Revert" option doesn't appear when pressing the right mouse button on a "Vector2" or "Vector3" property in the Inspector of a custom shader
- Missing Render Feature "Full Screen Pass Render Feature" in any “Universal Renderer Data” asset when upgrading from 2022.3
- Inconsistent ParticleSystemVertexStream.PercentageAlongTrail data range in Trail Texture Modes except "Stretch"
- The Graph Debug Window can be right clicked through and the Node Workspace is manipulated instead
Resolution Note:
This behavior happens because the depth texture for the camera is not available when rendering objects in endCameraRendering. In order to access depth from camera you can inject a render pass in the event AfterRendering.