Search Issue Tracker
Active
Votes
0
Found in [Package]
2020.1.0a14
2020.2
Issue ID
1238846
Regression
Yes
[VCS] VCS Window doesn't always group assets correctly with its appropriate meta file
How to reproduce:
1. Create a new project in your preferred workspace and open it
2. Connect it to Perforce
3. Import a couple of assets (5-10 should suffice) of varying file name length
4. Open the VCS window (Window -> Asset Management -> Version Control) and observe how the newly-added assets are grouped up in the default changeset
Expected result: the assets in the changeset are grouped up as a single "unit" in a format of "Asset name +meta" when their states are the same
Actual result: some longer file name assets in the changeset are not grouped up and are shown separately even though their version control states are the same
Reproduces in:: 2020.2.0a8, 2020.1.0b5, 2020.1.0b1, 2020.1.0a15, 2020.1.0a14
Not reproducible in:: 2020.1.0a13, 2019.3.11f1, 2018.4.21f1, 2017.4.37f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment