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
- "Custom Function" Node "Input" type changes do not immediately show mistmatch errors when set to an incompatible type in Shader Graph
- My Assets list is populated with Asset Packages when setting how many Packages to display before clicking the Load button
- Hub shows 6.0 as Latest LTS when opening a project after deleting its 6.3 Editor version
- Localization Group Rules bypasses Locale logic when SharedGroup asset provided
- UI Toolkit World UI Text Field unfocuses immediately when clicking on it using XR Controller
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.