-
-
Notifications
You must be signed in to change notification settings - Fork 812
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UIEffect Frequently Causes TextMeshPro Text to Display as Black Blocks When Saving Prefabs in Editor #285
Comments
This is a minimal project to reproduce the issue:
This will reproduce the issue. |
Thank you! 👍 |
The issue is reproduced on my environment. |
github-actions bot
pushed a commit
that referenced
this issue
Dec 14, 2024
## [5.0.1](5.0.0...5.0.1) (2024-12-14) ### Bug Fixes * build AssetBundle error ([7374747](7374747)) * fix cutoff transition effect ([c893cb0](c893cb0)) * fix TextMeshPro shader (underlay and bevel) ([f39097a](f39097a)) * TextMeshPro objects appeared as black blocks when saving prefabs in prefab mode ([5889486](5889486)), closes [#285](#285)
🎉 This issue has been resolved in version 5.0.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Thank you for the update. I’ve updated to version 5.0.1 and everything works perfectly now. I appreciate your quick response and support! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
When using the TextMeshPro text component with UIEffect in the Unity Editor, saving the UI prefab often results in the TextMeshPro texts appearing as black blocks. This issue disrupts the workflow, especially for users who frequently save their work. Below are the detailed observations and steps to reproduce the problem.
Environment Information:
Steps to Reproduce:
Expected Result:
All TextMeshPro texts should display normally with the applied UIEffect after saving the prefab.
Actual Result:
Additional Details:
Temporary Workaround:
Making any modifications to a TextMeshPro component or the UIEffect component, or reopening the UI prefab, causes the affected text to display normally again. However, this needs to be done individually for each problematic TextMeshPro text, which is time-consuming and inefficient.
Impact:
This issue significantly hampers the development process by requiring repetitive fixes after each save, making it difficult to maintain productivity and ensure visual consistency in UI elements.
Request:
I would appreciate any assistance or guidance on resolving this issue. If additional information is needed, please let me know. Thank you for your support!
The text was updated successfully, but these errors were encountered: