Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2018.4
2019.4.1f1
2020.2
Issue ID
1263131
Regression
No
Editor does not inform the user that a project is located in an unsupported file system
Reproduction steps:
1. Create a new project in an unsupported file system (e.g. exFAT, FAT32)
Expected result: an error or warning message appears informing the user that the project is located in an unsupported file system
Actual result: the Editor does not inform the user that a file system is not supported
Reproducible with: 2018.4.26f1, 2019.4.6f1, 2020.1.1f1, 2020.2.0a20
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Add comment