Search Issue Tracker
By Design
Votes
2
Found in
4.5.1p1
Issue ID
614055
Regression
Yes
Wrong warning shown when there is a script name mismatch
To reproduce:
1. Open attached project
2. Open scene Test. It contains a few scripts. One of them is named TestC, but in the script the class is named TesC (name mismatch)
3. Enter play mode - notice that the warning is "The referenced script on this Behaviour is missing!" and not "File and class name doesn't match"
Regression since 4.3.4f1
Explanation: If you try to add an existing MB whose class and filename don't match, you get a warning about the names not matching.
If you take an MB that has already been added to some GameObjects ("TestC") and change the class name (to "TesC"), then Unity can no longer find the MB that was referenced ("TestC")
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment