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
- Editor crashes when loading RenderDoc with Graphics API set to OpenGLES2 or OpenGLES3
- [Windows] Development Build with no scenes shows a purple screen when using OpenGLES3 graphics API
- Shader variants take too much memory at runtime
- [HDRP][VFX] Output mesh with default shader is incorrectly sorted before the HDRP fog
- Error "'GamepadSpeakerOutputType' does not exist in the namespace 'UnityEngine'" occurs in the Console when building a project
Add comment