Search Issue Tracker
Fixed
Fixed in 6000.0.62f1, 6000.2.11f1, 6000.3.0b9, 6000.4.0a4
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
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 Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note (fix version 6000.4.0a4):
6000.4.0a4 has the fix.
Resolution Note (fix version 6000.3.0b9):
Fix verified on 6000.3.0b10 (Hub)
Resolution Note (fix version 6000.2.11f1):
6000.2.12f1 : Fixed , verified, Screen shot in parent ticket.
Resolution Note (fix version 6000.0.62f1):
6000.0.62f1 : Fixed, verified. Screen shot in parent bug.