Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2020.1.0a6
2020.1.0a12
Issue ID
1197429
Regression
Yes
Scripts cannot be loaded when they contain an odd number of "*" signs in a commented line before a namespace
Steps to reproduce:
1. Open the attached "ScriptBug" project
2. Select "Directional Light" GameObject in the Hierarchy window
3. Open the "NewBehaviourScript" script which you can find in the Inspector window
4. Uncomment lines 6, 7 and 12
5. Press "Save" and open the Unity Editor window
Expected result: The script "NewBehaviourScript" which you can see in the Inspector window is loaded without errors
Actual result: "The associated script can not be loaded" error appears under the "NewBehaviourScript" script
Reproducible with: 2020.1.0a6, 2020.1.0a15
Not reproducible with: 2017.4.35f1, 2018.4.14f1, 2019.2.15f1, 2019.3.0f2, 2020.1.0a5
Note: If you delete or write one more "*" in the first line of the script, the script loads without any errors
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Add comment