Search Issue Tracker
Fixed
Fixed in 2021.3.26f1, 2022.3.0f1, 2023.1.0b18, 2023.2.0a13
Votes
5
Found in
2021.3.22f1
2023.2.0a10
Issue ID
UUM-33089
Regression
Yes
Console error “Enabling local keyword ‘WETNESS' for Material 'Disolve' has been skipped. This keyword cannot be enabled directly.“ when enabling a local keyword for a material
Reproduction steps:
1. Open the attached "dev-HDRP2021" project
2. Open "Assets/testcrossfade/OutdoorsScene" scene
3. Select the “Packages/Better Lit Shader/Example/Materials/Disolve.mat” material
4. In the Inspector window, find the “Wetness” setting and activate it (Go to Assets > Reimport All, if settings do not appear)
5. Observe the Console Window
6. In the Inspector window, in the “Wetness” dropdown settings activate “Use Effector”
7. Observe the Console Window
Expected result: Settings are applied without any console errors appearing
Actual result: Settings are not applied and console error appears: “Enabling local keyword ‘WETNESS' for Material 'Disolve' has been skipped. This keyword cannot be enabled directly.“
Reproducible with: 2021.3.21f1, 2021.3.22f1, 2023.2.0a1, 2023.2.0a8
Not reproducible with: 2021.3.20f1, 2022.1.0a1, 2022.1.24f1, 2022.2.15f1, 2023.1.0b1, 2023.1.0b12
Couldn't test with: 2020.3.47f1 (Shader Hidden/InternalErrorShader, can't open material)
Reproducible on: macOS Ventura 13.2.1 (M1 Max), Windows 10
-
bfoddy
May 02, 2023 16:08
This issue was introduced in an LTS dot release, frankly it is ridiculous that the fix has not been backported to that release.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2023.2.0a13):
Fixed in: 2023.2.0a13