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
- ScrollView clips content when under an ancestor that has a filter set
- "Retrieving array element that was out of bounds" error thrown when attempting to remove a column from a Multi-Column List View
- Multi-Column List View horizontal scroll resets to left most position when scrolling vertically
- Floating License is lost for concurrent jobs
- Warning "Failed to insert item" is logged when Assigning Project to Organization's Project in the Project Settings
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.