Search Issue Tracker
Fixed
Votes
0
Found in
5.0.2f1
Issue ID
698693
Regression
No
Material properties not updated at runtime until expanded in inspector
How to reproduce:
1. Open attached project
2. Open scene material_test_scene.unity
3. Play scene
4. Press the Space Bar to create and assign a material to the cubes
- Notice that apparently only the Albedo is assigned properly
5. Select one of the cubes in the scene view
6. Expand the Material inspector
- Note how the cubes get updated with highlights
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
SergeantBiscuits
Feb 06, 2022 00:42
This was happening to me when I had the emission color set to pure black by default. Setting it to anything other than pure black avoids the issue. Pretty sure DBURDEN1 is correct; Unity disables the emission component because it figures "well the color is pure black, which doesn't actually do anything, so I'ma just disable the whole color!"
GXMark
Nov 07, 2021 01:08
2020.3.22f1 still getting this issue. Setting the keywords but it does not update until opening a material inspector
AlexHogan
May 05, 2021 08:19
I appear to be running into this in Unity 2021.1.3f1
IvayloDev
Feb 18, 2021 15:18
Still not fixed (2019.4.11)
HinxVietti_WITL
Jan 26, 2021 03:38
Problem still in
2018.4.19 with tmpro 1.5.1
2019.4.16 with tmpro 2.1.3
UHDynamical
Jun 25, 2020 17:05
Nvm. It's just that the keyword for the _MetallicGlossMap texture is _METALLICSPECGLOSSMAP instead of _METALLICGLOSSMAP.
UHDynamical
Jun 25, 2020 16:54
2019.4. The issue still exists.
BlackOpsBen
May 28, 2020 05:04
I am experiencing this issue on 2019.3.13f1. I am glad to see I could find more people with this issue, but concerned that supposedly this bug was fixed.
Wothanar
Sep 09, 2019 19:53
DBURDEN1 dosnt work to me the Material.EnableKeyword() . im using meshbaker plugin for a work and normals are not good via runtime and i need to set them via runtime after a runtime bake, any new how to solve this?
RiseUpGames
Jul 31, 2019 05:51
Just came across this and thought I'd share my workaround (bug still exists in 2018.4.4). In my case I was changing a shader and later needing to restore the material back to its original shader. Setting the shader worked, but restoring it resulted in this bug.
Workaround was to simply make a copy of the material before modifying the shader, and then using the copy to change the material back to its original state later when needed:
Material originalMaterial = new Material(renderer.material);
renderer.shader = newShader;
.... // sometime later
renderer.material = originalMaterial;