Search Issue Tracker
Won't Fix
Votes
6
Found in
2017.2.0f3
Issue ID
960822
Regression
Yes
"Refresh case sensitivity..." errors are thrown when importing materials exported from Unity 5.x to Unity 2017.1.0a3 and later
How to reproduce
1. Create a new project
2. Import the attached "TestMaterialPackage (5.5.0f3)" into newly created project
3. Press CTRL+R a few times (or right click on Project window and press "Refresh")
Expected result: No errors appear
Actual result: "Refresh case sensitivity failure. Asset: Assets/Surface.mat..." errors appear
Regression introduced in - 2017.1.0a3
Reproducible with - 2018.1.0a1, 2017.3.0b6,2017.2.0f3, 2017.1.2p2, 2017.1.0a3
Not reproducible with - 5.5.4p3, 5.6.3p4, 2017.1.0a2
Note: Issue only happens if exporting/importing materials into Virtual Drive that is mounted as FAT32, it does not happen on NTFS
-
neo102341
Jul 19, 2019 21:10
y have the same issue!!
-
GAZEREAPER
Jan 04, 2018 19:01
I have had this issue since every 2017.x version, and currently it has made me unable to even work on my project. Everytime i switch applications and go back to unity, it has to reimport everything. And currently when reimporting, unity automatically deselects the unity application so that when I select it again it has to reimport everything AGAIN and I'm stuck in an infinite loop without being able to do anything. I would VERY much appreciate it if this could be fixed without me having to swap every single project to a different drive.
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
- Shader Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
- The Editor hangs when opening a project that uses local packages and Version Control
- Area Light is culled when Camera Frustrum is outside the lights range
- The characters of the bottom option in the Scene View Debug Draw Mode dropdown menu are cut off
- Graph and Camera options for Render Graph Viewer disappear after maximising the window
Resolution Note (2019.1.X):
We have decided not to fix the issue at this point due to the very specific scenario it reproduces in. As a workaround one can export the package directly to an NTFS drive first.