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
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
- Loading animations are hitching or stopping when using "SceneManager.LoadSceneAsync" to load new scenes
- [sw-unity-6-1] GameObject child is created in the last GameObject of the hierarchy instead in the selected GameObject by right clicking
- Lens Flare is misaligned when modifying the Camera's Viewport Rect
- [Linux] Crash on RenderEventsContext::ExecuteCommandBuffers when creating a new Material while in Play Mode
Add comment