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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.