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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
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.