Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
0.6.7
Issue ID
1138775
Regression
No
[WebGL][Adressables] Second camera turns black in WebGL split-screen build
How to reproduce:
1. Open the attached project ("case_1138775-black-camera.zip")
2. In Build Settings, set the target platform to WebGL
3. Build Addressable assets (Build Player Content)
4. Open the repro scene ("Scenes/SampleScene")
5. Enter the Play Mode
6. Click "Adressable.LoadSceneMode.Additive" button
7. Notice that both sides are in a different shade of pink
8. Exit the Play Mode
9. Build and Run the project
10. Click "Adressable.LoadSceneMode.Additive" button
Expected results: Both cameras are active
Actual results: Camera loaded with Adressables (on the right) remains inactive
Reproducible with: 2018.3.11f1,
Reproducible with Package version: 0.6.8
Couldn't test with 2017.4, as it lacks Package Manager and Adressables
Couldn't reproduce on 2019.1 and 2019.2, "Multiplayer-HLAPI" package gives errors when trying to build player content, and deleting the package seems to solve the issue.
Notes:
1. Deleting Multiplayer High-Level API package fixes the issue in 2019.1 and 2019.2 branches
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Try to use a verified version of addressables. Additive issues should be resolved.