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
- [URP][Lighting] The skybox doesn't render after changing the settings of the Material when using the URP Render Pipeline
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
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.