Search Issue Tracker
Fixed in 5.4.1
Votes
10
Found in
5.4.0b17
Issue ID
798640
Regression
No
[Standalone] Camera doesn't render to second monitor when set by script after first rendered frame
Steps to reproduce:
1) open user attached project
2) open project named "Mobile_Map_Test"
3) play in editor and see expected behavior (second monitor camera is rendering)
4) build for standalone and play
- Second monitor camera stopped rendering
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
- [Apple Silicon] HID descriptor warning pops up when opening the project
- D3D11 swapchain error pop-up appears and the Editor shuts down when opening a project
- [Shader Graph] Node input value links have rendering artifacts when moving the nodes
- [Linux][URP] Crash on GfxFramebufferGLES::Clear when entering the Play Mode when all Renderer Features are disabled, Native RenderPass and MainCamera's Depth Texture is enabled
- Mesh shadow is wrong when using Alpha Clipping in Shader Graph compared to the default "Lit" Shader
Felipe-Brito
Oct 26, 2017 15:06
I confirm the problem exists in 2017.2.0f3
Selezneva
Feb 01, 2017 03:35
I confirm the problem exists in 5.5.1
Tabu
Jan 22, 2017 16:39
This issue seems to have re-appeared in 5.5.0f3 :( Can you please reopen this issue?
Aras
Jun 16, 2016 07:37
Workaround: after changing target display, explicitly enable the camera (cam.enabled = true). Current code in the engine silently disables the cameras that have non-existing target displays set on them.