Search Issue Tracker
Fixed
Fixed in 6000.5.0a6
Won't Fix in 6000.4.X
Votes
0
Found in
6000.0.65f1
6000.2.15f1
6000.4.0b4
6000.5.0a4
Issue ID
UUM-131996
Regression
No
Errors indicating that TMP Extras were not Imported logged when opening the Render Pipeline Converter Window while in Play Mode
Steps to reproduce:
- Create a new URP Project
- Enter Play Mode
- Open the RPC Window (Window > Rendering > Render Pipeline Converter)
- If no Errors are present, Close the RPC Window and repeat step 3
- If no Errors are present, Exit Play Mode and repeat step 3-4
Actual results: 2 Errors "Failed to import package with error: Cannot import package in play mode.
UnityEditor.AssetDatabase:ImportPackage (string,bool)
TMPro.TMP_PackageUtilities:ImportExamplesAndExtras () (at ./Library/PackageCache/com.unity.ugui@bd6c5edc6ec3/Editor/TMP/TMP_PackageUtilities.cs:1050)
TMPro.TMP_PackageUtilities:ImportExamplesContentMenu () (at ./Library/PackageCache/com.unity.ugui@bd6c5edc6ec3/Editor/TMP/TMP_PackageUtilities.cs:1040)" are logged
Expected results: The RPC Window is opened without issues at all times in Play Mode, TMP Extras are loaded correctly beforehand
Reproducible with versions: 6000.0.65f1, 6000.2.15f1, 6000.4.0b4, 6000.5.0a4
Not reproducible with: 6000.3.4f1 (UUM-132083 issue happens instead)
Tested on (OS): Windows 11
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note:
Fixed in 6000.5.0a6
Resolution Note (fix version 6000.5.0a6):
Fixed in 6000.5.0a6
Resolution Note (6000.4.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.