Search Issue Tracker
Fixed in 1.5.0 & 2.1.0
Votes
31
Found in [Package]
1.3.0
Issue ID
1093101
Regression
No
Text Mesh Pro components inside prefabs remain in the 'Overrides' drop-down menu even after applying their changes
How to reproduce:
1. Open user-submitted project (NestedPrefabBug)
2. Open the scene 'SampleScene'
3. Select the 'Canvas' GameObject and attempt to override changes to (Mesh Filter) and Text Mesh Pro (Script) components
Expected result: changes in the components are applied in the prefab and the 'Overrides' drop-down indicates that there are no overrides
Actual result: the (Mesh Filter) and Text Mesh Pro (Script) components remain in the 'Overrides' drop-down menu even after changes are applied
Reproducible with: 2018.3.0b9, 2019.1.0a8
Notes:
Note that there is no (Mesh Filter) component on the 'Text' GameObject upon first opening the project, it only appears after overriding the Canvas prefab
The (Mesh Filter) component always reverts to an empty string upon overriding the changes
Comments (13)
-
fben
Feb 09, 2019 22:35
Still present in 2018.3.5.1f1
Surprising not more people complain about it. -
CaelumNoctis
Feb 08, 2019 09:07
Still bugged in 2018.3.3f1.
-
radraghag
Dec 27, 2018 18:15
That is super annoying please fix ASAP
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note (fix version 1.5.0 & 2.1.0):
This issue has been resolved and will be fixed in the next release of the TMP package for Unity 2018.4 which will be version 1.5.0 and in TMP package version 2.1.0 for Unity 2019.x.