Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.9f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1184385
Regression
No
[WebGL] Multiple Camera Viewports in fullscreen mode are rendered differently in WebGL builds than in the Editor
How to reproduce:
1. Open the attached project ("case_1184385-WebGlViewportsBug.zip")
2. Switch the targeted platform to WebGL
3. Open the repro scene ("SampleScene")
4. Enter Play mode and notice how viewports are displayed
5. Move the mouse to any of the viewports and press "Space" to focus that viewport
6. Exit Play Mode
7. Make a WebGL build and run it
8. Enter fullscreen mode
Expected results: Viewports are rendered the same as in the Editor
Actual results: Viewports are rendered differently, and some of them aren't visible
Reproducible with: 2017.4 32f1, 2018.4.10f1, 2019.2.7f2, 2019.3.0b4, 2020.1.0a3
Couldn't test with 2020.1.0a4, 2020.1.0a5 because of WebGL errors in the build
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
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Resolution Note (fix version 2021.1):
Overlay cameras (UI Camera) will no longer cause the fullscreen display to sometimes be incorrect
Fixed in 2021.1.0a3