Search Issue Tracker
Duplicate
Votes
0
Found in
2018.2.3f1
2018.2.4f1
Issue ID
1073362
Regression
Yes
Script doesn't find the reference to the necessary namespace after reimporting Scripts
How to reproduce
1. Download user's attached project "PhoenixPointStripdown-ScriptableObjectsBroken.zip"
2. After opening the project in the Assets folder right-click on the "Code" folder and select Reimport.
Expected result: Script does find the reference to the necessary namespace and none warning are thrown
Actual result: Console throws a bunch of warnings "No script asset for Asset. Check that the definition is in a file of the same name." will pop up.
Reproducible with: 2018.2.3f1, 2018.2.4f1, 2018.4.5f1
Not reproducible with: 2018.19f2, 2018.2.2f1
Note: Take a look at a warning "No script asset for RemoveActorEffectDef". Check that the definition is in a file of the same name." Selecting the mentioned scripts should show in the Inspector window at the top: "No MonoBehaviour scripts in the file or their name does not match the file name". Even though the filename does match the class name inside.
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
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
- UnityEvent does not get pasted to a uGUI component when trying to copy it from a Script
This is a duplicate of issue #1071188