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
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
artofcode
May 15, 2017 16:28
This is still an issue in 2017.1.0b5