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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment