Search Issue Tracker
Fixed
Fixed in 6000.0.53f1, 6000.1.11f1, 6000.2.0a9
Votes
5
Found in
6000.0.0b1
6000.1.0a1
6000.2.0a1
Issue ID
UUM-101193
Regression
No
UnityException: get_disableApplyMaterialPropertyDrawers can only be called from the main thread
Looks like ClassifyMaterialsJob.Run() calls Material::GetActualRenderQueue() in C++ down the line, which can throw (EnsurePropertiesExistForVariants) if not called from the main thread. ClassifyMaterialsJob needs to run truly on the main thread to avoid the exception.
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
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
Resolution Note (fix version 6000.2.0a9):
Fixed the "get_disableApplyMaterialPropertyDrawers can only be called from the main thread" exception that occurred occasionally with GPU Resident Drawer after a domain reload
Resolution Note (fix version 6000.1.11f1):
Fixed the "get_disableApplyMaterialPropertyDrawers can only be called from the main thread" exception that occurred occasionally with GPU Resident Drawer after a domain reload.
Resolution Note (fix version 6000.0.53f1):
Fixed the "get_disableApplyMaterialPropertyDrawers can only be called from the main thread" exception that occurred occasionally with GPU Resident Drawer after a domain reload.