Search Issue Tracker
In Progress
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X
In Progress in 6000.4.X
Votes
0
Found in
6000.0.54f1
6000.1.13f1
6000.2.0b11
6000.3.0a3
6000.4.0a1
Issue ID
UUM-112052
Regression
Yes
[WebGL] Material Override does not apply when using the debugger to apply it in a WebGL build
How to reproduce:
1. Open the attached “IN-107116” project
2. Open “Build Settings…” and build a WebGL project with the “Development Build” option enabled (File → Build Settings…)
3. Run the built project and press “CTRL” + “Backspace” to open the “Debug Manager” window
4. In the “Debug Manager” window select the blue arrows to navigate to the “Material” tab
5. In the “Material” tab under “Material Filters” change the “Material Override” to Rendering Layer Masks
6. Observe the built project window
Expected result: The “Material Override” applies a white effect on the build
Actual result: No effect is visible in the built project
Reproducible with: 6000.0.18f1, 6000.0.54f1, 6000.1.13f1, 6000.2.0b11, 6000.3.0a3
Not reproducible with: 6000.0.17f1
Reproduced on: Windows 11
Not reproduced on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
- Flickering bright white dots in the Scene when the Android Platform is selected and DX11 Graphics API is used with Iris(R) Xe Graphics GPU
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
Add comment