Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.2.4f1
2019.3.0a1
2020.1.0a1
Issue ID
1183014
Regression
No
Renderer components cause Behaviour missing warnings to appear when recompiling in Play Mode
Repro steps:
1. Open user attached project
2. In the Hierarchy window, select "Main Camera" and add a "Sprite Renderer" component
3. Enter Play Mode
4. In the Project window, from the Assets folder, open "testScript.cs", change the string in line 10 and save the file
5. Go back to the Editor
Expected result: Script is compiled and no warnings appear
Actual result: "The referenced script (Unknown) on this Behaviour is missing!" warning appears
Reproducible with: 2017.4.32f1, 2018.4.10f1, 2019.2.7f2, 2019.3.0b5, 2020.1.0a6
Note: Also reproducible with Sprite Mask, Tilemap and SpriteShape Renderers
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
- [Rendering Debugger] Shortcut in documentation to open window doesn't work
- The "Compress Tilemap Borders" function is not working when used via the Context Menu or through Script
- HDRP Sorting Priority not working when Render Pass is locked on a parent material
- [XR] Camera view rendered by the RenderTexture is not updated at runtime when XR is enabled
- Lens Flare occlusion is slightly delayed when Anti-aliasing is set to TAA
Resolution Note (2020.1.X):
This issue is widely present with a lot of Unity's built-in Inspectors, and won't fully go away until each team fixes the Inspectors they own. The warnings are harmless and can be safely ignored. A workaround is to not select any Inspector when recompiling your scripts in Play Mode.