Search Issue Tracker
Active
Votes
1
Found in
2019.4
2020.2
2020.2.1f1
2021.1
2021.2
Issue ID
1311395
Regression
No
Custom View/Projection matrices not used when drawing Meshes with the CommandBuffer
How to reproduce:
1. Open the user's attached project
2. Enter Play mode
Expected results: When using the CommandBuffer to draw a mesh, the Projection and View matrices are used that have been set
Actual results: In the first frame the Projection and View matrices are used correctly when using the command buffer and then the Projection matrix of the active camera is used when using the CommandBuffer to draw a mesh
Reproducible with: 2019.4.20f1, 2020.2.6f1, 2021.1.0b7, 2021.2.0a6
Could not test with: 2018.4.32f1 (Errors downgrading)
Note:
Reproduces with: HDRP, URP and the default render pipeline
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader error db grows on each build
- Android ARCore build fails with 2019.4 due to outdated Gradle
- [tvOS] Visual artifacts are present when Ambient Occlusion is enabled and Dynamic Resolution is reduced
- Texture Importer Inspector throws errors when a built-in texture inspector is overwritten in C#
- Invalid AABB error is thrown when moving a Particle with Velocity over Lifetime and Limit Velocity over Lifetime modules
Add comment