Search Issue Tracker
Not Reproducible
Votes
1
Found in
5.4.0f3
Issue ID
823783
Regression
Yes
Editor crashes in RenderingCommandBuffer::ExecuteCommandBuffer
Steps to reproduce:
1. Open the attached project.
2. Press play.
As a result, Unity crashes in RenderingCommandBuffer::ExecuteCommandBuffer and it's only reproducible on 5.4
Reproduced on: 5.4.0p2, 5.4.0f3, 5.4.0f2.
Didn't reproduce on: 5.3.6f1, 5.3.5f1, 5.3.4f1, 5.2.5f1
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Guillaume-Swing
Sep 29, 2016 16:00
Seriously that is super sad that there is so much regression this days with 5.4.
I understand that there is a lot of optimisations and changes going on... but still, those are serious crashes with no obvious workaround :(
So we are stuck in previous version of Unity after having passing some time to upgrade the code, rebuild Libraries and hoped that this will fix other vsync issue (that were not fixed for us). I'm loving it'