Usage Flags are not correctly marking Materials as dirty when automatically setting and with using a Source Control method.
Compact Repro Steps from User:
"To reproduce:
Create a entrance level that opens when the editor opens. Create secondary level that you can chose to load from the File menu. Create a test material. Just a colour into albedo will do. DO NOT APPLY THIS MATERIAL TO A STATIC OBJECT. Then submit this material into perforce. Once it has been submitted apply the material to a static mesh in the secondary loaded level. It will automatically tick 'used with static lighting' in the test material and ask you to check out the material. DO NOT CHECK OUT THE MATERIAL. Save only the secondary level with the material applied to the static mesh. Close UE4.
Open UE4 again into the entrance level (the one without the test mat applied to a static mesh). Open the test material. Used with static lighting is not ticked. Expected behaviour. Now open the test level (the level with the static mesh with the applied material). Note that in the material 'used with static lighting' gets ticked. However the material does not become marked as changed with a star [Image Removed] ! It should be."
RESULTS: When Level02 is opened the Usage Flag is checked true in Material but the Material is not Marked as Dirty
EXPECTED: Usage Flag Change should mark Material as Dirty
i have this problem UE4CC-Windows-58DC12AF4B97F057BD108FBFF569B2E9_0000
Installer 4.10 failed with error code R-1603
I am not able to find world outliner how to enable it?
Delay nodes occasionally don't fire the "Completed" output in a nativized build
Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows
Head over to the existing Questions & Answers thread and let us know what's up.
1 |
Component | UE - Rendering Architecture - Materials |
---|---|
Affects Versions | 4.8, 4.8.1 |
Created | Jun 24, 2015 |
---|---|
Resolved | Aug 18, 2021 |
Updated | Nov 2, 2021 |