Search Issue Tracker
By Design
Votes
1
Found in [Package]
10.0.0-preview.26
Issue ID
1273307
Regression
No
GameObjects are not visible after entering Play Mode when calling the CommandBuffer.SetViewProjectionMatrices function
How to reproduce:
1. Open the attached project's Scene labeled "New Scene"
2. Observe the Cubes in the Game View
3. Enter the Play Mode
3. Observe the Cubes in the Game View again
Expected result: Cubes are visible after entering Play Mode when calling the CommandBuffer.SetViewProjectionMatrices function
Actual result: Cubes are not visible after entering Play Mode when calling the CommandBuffer.SetViewProjectionMatrices function
Reproducible with: 2019.4.9f1, 2020.1.5f1, 2020.2.0b2 (7.3.1, 10.0.0-preview.26)
Couldn't test with: 2018.4.27f1 (4.10.0-preview)(ScriptableRendererFeature doesn't exist)
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
- Typos in High Definition 3D sample tutorials
- “Handles.Repaint called outside an editor OnGUI" error is thrown in the Console when creating a new Tile Palette from the Tile Palette Overlay in Scene view
- Shader Graph window icon is blurry and low quality when the Shader Graph is created using the Universal 2D template
- “Export HDRP Sky to Image” command error message does not indicate that Game view must be visible
- Adaptive Performance Settings Framerate field doesn't display the "supported without VSync" warning, when the field is collapsed in Build Profiles
Resolution Note:
The cubes stop rendering because your render pass sets the view and projection matrices to identity and the pipeline doesn't restore the camera matrices per-pass. This is by design as it would incur in extra overhead to restore all matrices per-pass. It's expected from a custom render pass that if you change the matrices you need to restore it afterwards.