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
- Getting a deprecated package for JetBrains Rider pop up when opening or creating a project
- [Android] Volume level of the same audio file is different on Samsung Galaxy Tab A8 between 2023.3.0b3 and 2023.3.0b4
- ‘Expected end of value’ warning occurs when a property declaration includes five or more variable references
- Crash on BurstCompilerService::CompileAsync when entering Play mode in a specific scene
- InvalidOperationException when using Game Camera Preview in Scene window with a custom RenderGraph pass
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.