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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment