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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment