Search Issue Tracker
Fixed in 5.6.0f3
Votes
0
Found in
5.6.0f3
Issue ID
898439
Regression
Yes
When Camera.targetTexture=null in the script on at least two Cameras, Camera Depth does not show objects in the correct order
Reproduction steps:
1. Open the attached project;
3. Open the scene "main";
3. Enter Play mode;
4. Press "Space" key;
Actual result: the sphere goes on the capsule.
Expected result: the sphere should stay where it is.
Note: If you disable "Render Target Set" script in an object "Camera 3", everything will work correctly. The problem happens because of targetTexture is set to null and when this function is set at least on two Cameras.
Reproduced with: 5.6.0a1, 5.6.0f1, 2017.1.0a6
Not reproducible with: 5.4.5p1, 5.5.0b1, 5.5.3f1
Regression introduced in 5.6 alpha
Note#2: verified with 5.6.1p1 version
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
- “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
artofcode
May 15, 2017 16:28
This is still an issue in 2017.1.0b5