Search Issue Tracker
Fixed in 5.6.0
Votes
1
Found in
5.6.0f3
Issue ID
897018
Regression
Yes
Camera Depth is ignored with 3+ cameras and one with different viewport
Repro steps:
1. Open attached projects "incorrect_camera_ordering" scene
2. Change "middle_camera_green" view port to (0.3;0;1;1)
4. See that the "front_camera_blue" depth is ignored
Expected: For the views to line up according to the depth
Actual: The camera that had the view port values changed is in from of the third camera even though it might be the nearest one in depth
Reproduced with: 2017.1.0a6, 5.6.0f3(f2, f1)
Working with: 5.5.3f1, 5.4.0f3
Attached video of repro
NOTE: Only reproducable with 3+ cameras. If 2 cameras are used the depth is correct.
Similar case that was marked as fixed(but isn't) is case #885051
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
coshea
Apr 20, 2017 11:34
This issue isn't fixed in 5.6.0f1
So why does the issue say fixed?