Search Issue Tracker
By Design
Votes
0
Found in
2018.2.8f1
Issue ID
1082013
Regression
No
Refreshing an asset forces scripts to recompile during play mode, even if they are set to recompile only after play mode
Steps to reproduce:
1. Create a new project
2. In Preferences, set "Script changes while Playing" to "Recompile after finished playing"
3. Create a new script and attach it to any gameobject
4. Create a new text file
5. Enter play mode
6. Edit the script in a code editor
7. Edit the other created file
8. Refocus the editor
Expected result: other file updates, script does not
Actual result: other file updates causing the scripts to recompile
Reproduced on 2018.2.0a4, 2018.2.15f1, 2018.3.0b8, 2019.3.0a7
Feature introduced in 2018.2.0a4
Notes:
- this behavior has sometimes led to crashes on the user's end, but I was unable to reproduce that.
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
- [macOS] Unable to install VisionOS Module using HUB 3.8.0-beta.2
- NullReferenceException is thrown when pressing the "Enter" key to select an item in a ListView
- Burst internal compiler errors are thrown when creating a new 2D project
- Tile Paint action disappears from Undo History when Tile Selection tool has been used beforehand
- The pregenerated LightDefinition.cs.hlsl does not match the source LightDefinition.cs when regenerating shader includes
Resolution Note:
If both a script and a non-script asset are modified, then the reimport requires a script recompilation. This is because scripts can affect how assets are imported, and Unity doesn't know whether the script changes are important until it does the recompilation. So the current behaviour is by design, and can be avoided by only changing script assets OR non-script assets during play mode, but not both at the same time.