Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
2020.1.0a3
Issue ID
1181146
Regression
No
[VCS] Both asset and .meta files within the folder are checked out when checking out "Only Asset file" on folders
How to reproduce:
1. Create a new project in your preferred workspace and open it
2. Connect it to Perforce
3. Create a new folder and a new material within it
4. Submit the folder and its contents
5. Right-click the folder -> Version Control -> Check out (other) -> Only asset file
6. Observe the Version Contol Window
Expected result: only the asset file is checked out for the material within the folder
Actual result: both the asset file and its .meta file are checked out for the material within the folder
Reproduced in: 2020.1.0a3, 2019.3.0b2, 2019.2.3f1, 2018.4.8f1, 2017.4.32f1
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note:
For this moment, checking out a folder as 'Asset only' checks out the asset(folder) and everything inside it (including metafiles). Due to complexity and high risk, it was decided not to fix it for this moment.