Search Issue Tracker
By Design
Votes
0
Found in
5.4.2p3
Issue ID
849361
Regression
No
Windows Player crash on Camera.RenderWithShader after Screen.SetResolution
Windows Player build crashes after executing following scenario couple times:
1. Set custom target buffers for camera with Camera.SetTargetBuffers
2. Change resolution with Screen.SetResolution
3. Call Camera.RenderWithShader (This is where it crashes)
Reproduction steps using attached project:
1. Open attached poroject (849361_Crash.zip)
2. Build & Run,
3. In Resolution Dialog select non native resolution and click Play
4. Click Change Resolution button few times
Expected result:
Resolution should change on every button click
Actual result:
Player hangs and crashes
This project contains scene with two cameras. Camera named "Camera" is here only for bug observation purposes and bug would reproduce without it.
The script that causes bug is attached to Main Camera.
Reproduced on:
Unity 5.2.5f 5.3.3f1 5.4.2p3, 5.5.0b11, 5.6.0a2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher
- Crash on RtlLookupFunctionEntry when using 10 or more GameObjects with Articulation Body component in the scene
- Polygons are created on the opposite side of the Sprite when the Sprite boundaries are above the edge of the Texture
- Render Graph Viewer Resource list becomes shrunk after using a filter that yields no results
- [Android] [Vulkan] "VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT" not added on some Android devices to "2D Colour Attachment"
Add comment