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
- Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
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.