Unity Issue Tracker - UnityException: get_disableApplyMaterialPropertyDrawers can only be called from the main thread

Fixed

6.2.X

6.1.X

6.0.X

Fixed the "get_disableApplyMaterialPropertyDrawers can only be called from the main thread" exception that occurred occasionally with GPU Resident Drawer after a domain reload

Fixed the "get_disableApplyMaterialPropertyDrawers can only be called from the main thread" exception that occurred occasionally with GPU Resident Drawer after a domain reload.

See https://discussions.unity.com/t/unityengine-get-disableapplymaterialpropertydrawers-can-only-be-called-from-the-main-thread/1618450

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.

UnityException: get_disableApplyMaterialPropertyDrawers can only be called from the main thread

Unity: GPU Resident Drawer

Fixed

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

UnityException: get_disableApplyMaterialPropertyDrawers can only be called from the main thread

Unity: GPU Resident Drawer

Statuses

Fixed

Resolution Notes

6.2.XFixedFixed the "get_disableApplyMaterialPropertyDrawers can only be called from the main thread" exception that occurred occasionally with GPU Resident Drawer after a domain reload

6.1.XFixedFixed the "get_disableApplyMaterialPropertyDrawers can only be called from the main thread" exception that occurred occasionally with GPU Resident Drawer after a domain reload.

6.0.XFixedFixed the "get_disableApplyMaterialPropertyDrawers can only be called from the main thread" exception that occurred occasionally with GPU Resident Drawer after a domain reload.

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?