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
- SerializedPropertyChangeEvent is invoked when initially binding PropertyFields in custom Editor
- UI Panel is not visible when HDR and STP filter are enabled
- Crash on GfxDeviceD3D11Base::DrawBuffersIndirect when opening a specific project
- OnTriggerExit2D is called in Play mode when undoing component adding
- Builds fail with "Execution failed for task ':launcher:checkReleaseDuplicateClasses'" error when the newer version of the In-App Purchasing package is installed on a specific project
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.