Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.3.0a3
Issue ID
1162487
Regression
No
[VCS] Modifying texture import settings also checks out the asset itself in Perforce, not only the .meta file
It seems that when user modifies import settings of various assets, both the asset and the .meta file of it are checked out in Perforce. But changing the import settings only changes the .meta file contents, and thus the asset does not need a checkout.
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
- Incorrect Burst Exception Control Flow in Editor due to Mono Handling of calli instruction
- [Linux] Packman options to add package from Git URL doesn't always show the window directly below the + button
- "UnityEngine.SystemInfo.processorFrequency" logs a value of 0 on M1 macs
- Editor redirects to a broken page when pressing question mark "?" in the Inspector window
- Editor directs to non-existent page when pressing "Learn more..." for Asset Pipeline
Resolution Note (fix version 2020.1):
The behaviour has been changed - the imported assets will now checkout only their .meta file and natives ones check out both.