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
- Bloom effect is different from a standalone platform when a Scene uses HDRI lighting and the effect is used in WebGL
- Memory Leak when using InstantiateAsnyc to instantiate a large Prefab
- There are no checkboxes to enable and disable Volume Profile effects when in the Graphics Settings window
- “ArgumentException: Trying to use an invalid resource (pass Motion Blur)” errors are infinitely thrown when Motion Blur is used
- Inspector is not using the result of the last CreatePropertyGUI call when calling it for several times for one property
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.