Search Issue Tracker
Active
Votes
0
Found in
6000.0.33f1
6000.1.0a10
Issue ID
UUM-91734
Regression
No
WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
Reproduction steps:
1. Open the attached “WebGLTerrain.zip” project
2. Open the “SampleScene”
3. Build and Run for WebGL (File > Build and Run)
4. Observe the WebGL Player in the browser
Expected result: The Scene in the Player loads
Actual result: The Scene is shown for a split second and then the Player turns black and “Validation: [Invalid CommandBuffer] is invalid….”, “Validation: [Buffer "UniformBuffer 35"] bound with size 4096 at group 1, binding 2 is too small.…” logs in the browser Console
Reproducible with: 6000.0.33f1, 6000.1.0a10
Couldn’t test with: 2021.3.47f1, 2022.3.55f1 (WebGPU backend not supported)
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- Does not reproduce if ‘WebGL 2’ Graphics API is used
- Only reproduces if ‘Use GPU Instancing’ is enabled on the Detail Mesh
- Reproduced on Microsoft Edge (131.0.2903.99), Google Chrome (131.0.6778.140) and Opera GX (114.0.5282.218), but did not reproduce on Firefox browser (33.0.3)
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
Add comment