Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.3.0a8
7000.0.0a1
Issue ID
UUM-53266
Regression
Yes
[TextMeshPro] Button does not refresh text when opening a Project after deleting its Library folder
How to reproduce:
1. Open the user-attached “GlyphDemo.zip” Project
2. Open the “SampleScene”
3. Observe the bottom two buttons
4. Close and re-open the Project
5. Observe the bottom two buttons
Expected result: The “Show Glyph” text is visible on the bottom two buttons when first opened
Actual result: The “Show Glyph” Text is visible on the bottom two buttons only from the second time it’s opened
Reproducible with: 4.0.0-pre.1 (2021.3.31f1, 2023.1.16f1), 4.0.0-pre.2 (2022.3.11f1, 2023.1.16f1)
Not reproducible with: 3.2.0-pre.6 (2023.1.16f1)
Couldn’t test with: 2023.2, 2023.3 (TMPro merged into uGUI, and the issue either is not reproducible or a feature is missing required for reproduction of the issue)
Reproduced on: macOS Sonoma 14.0 (Intel), Windows 10
Not reproduced on: No other environment tested
Notes:
- To reproduce the issue again, delete the “Library” folder before opening the Project
- Couldn’t reproduce on a new Project
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
- Crash on [NSApplication endModalSession:] when saving while Play Mode is loading
- Incorrect Preferred Height calculation when a single text line uses different Font Assets
- [ShaderGraph] Redo Collapse Nodes action does not fully collapse the Nodes
- [Ubuntu] Mouse cursor is set box select mode after exiting VFX Graph's Rename Context function
- Unrecognized identifier DECLARE_STACK_CB error is thrown when VirtualTexture Property is used with Custom RenderTexture target
Resolution Note:
Thanks for the report. This is not something we are able to provide a full and automatic fix for at this time. It seems to be a rather unique issue that shows up in some existing projects, and once the workaround below is applied, the issue goes away. Please take a look at the workaround:
For the current workaround, we recommend users manually replace old GUIDs with new ones. Here are the lines to replace:
FontAsset:
TextMesh Pro: m_Script:
{fileID: 11500000, guid: 71c1514a6bd24e1e882cebbe1904ce04, type: 3}
TextCore: m_Script:
{fileID: 19001, guid: 0000000000000000e000000000000000, type: 0}
SpriteAsset
TextMesh Pro: m_Script:
{fileID: 11500000, guid: 84a92b25f83d49b9bc132d206b370281, type: 3}
TextCore: m_Script:
{fileID: 19002, guid: 0000000000000000e000000000000000, type: 0}
ColorGradient
TextMesh Pro: m_Script:
{fileID: 11500000, guid: 54d21f6ece3b46479f0c328f8c6007e0, type: 3}
TextCore: m_Script:
{fileID: 19003, guid: 0000000000000000e000000000000000, type: 0}
StyleSheet
TextMesh Pro: m_Script:
{fileID: 11500000, guid: ab2114bdc8544297b417dfefe9f1e410, type: 3}
TextCore: m_Script:
{fileID: 19004, guid: 0000000000000000e000000000000000, type: 0}