Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
0
Found in
2019.3.0a1
2020.1
2020.1.5f1
2020.2
Issue ID
1278242
Regression
Yes
Fatal error is not thrown and Editor continues to function when working directory is changed with Directory.SetCurrentDirectory
Reproduction steps:
1. Open the attached project ("case_1278242-dirbug.zip")
2. Open the repro scene ("SampleScene")
3. Enter Play Mode
4. Exit Play Mode
5.Unfocus and re-focus the Editor
Expected result: Fatal error is thrown, explaining that changing the working directory is not supported
Actual result: Fatal error is not thrown, Editor continues to function, creating any asset yields errors
Reproducible with: 2019.3.0a1, 2019.4.11f1, 2020.1.6f1, 2020.2.0b3
Not reproducible with: 2018.4.27f1, 2019.2.21f1
Note: When setting Editor's working directory through a script, it has to be set back to the original path manually, or fatal error should be thrown explaining that this is not supported
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a1
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b11