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
- [macOS] Project fails to load when Virtual Artifacts are Corrupted
- Long scheduler times on main thread when using InstantiateAsync with a singular massive Prefab
- The project hangs upon opening it when importing the "discrete_rank2_vector_v2_0.onnx" file
- Opening the Look Dev hangs the Editor when the window is opened for the first time in the project or after deleting the Library folder
- Look Dev has blurry icons on 4k monitors
Add comment