Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in [Package]
2.0.1
Issue ID
1171436
Regression
No
TextMesh Pro - Reload Assembly is called from managed code directly when importing Examples & Extras
When you import the TMP Examples & Extras, an error will appear in the console:
Reload Assembly called from managed code directly. This will cause a crash. You should never refresh assets in synchronous mode or enter playmode synchronously from script code.
UnityEditor.AssetDatabase:ImportPackage(String, Boolean)
TMPro.TMP_PackageResourceImporter:OnGUI()
TMPro.EditorUtilities.TMP_ResourceImporterProvider:OnGUI(String)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
1. Open Unity
2. Open the attached project
3. Go to Edit > Project Settings > TextMesh Pro
4. Select Import TMP Examples & Extras
Expected Result:
Assets are imported without Reloading the Assembly direct from code.
Actual Result:
Reload Assembly is called from managed code directly.
Tested on Windows 10.
Occurs with 2.0.1 using 2019.2.0b10, 2019.1.11f1, 2018.4.3f1
Does not occur with 2.0.1 using 2019.3.0a11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Add comment