Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.2.X, 2021.1.X
Votes
0
Found in
2020.1
2020.1.7f1
2021.1
Issue ID
1283635
Regression
No
No VCS checks/actions on an moved asset in a Perforce workspace using drag-drop or AssetDatabase.MoveAsset
How to reproduce:
1. Connect to the Virtual Machine provided in the case edits
2. Click Asset Move > Scenario 2 in the opened project
3. After the move is finished check "Ignored Folder"
Expected Behavior: "Test Group" asset is marked as "Local"
Actual Behavior: "Test Group" asset is marked as "Added Local"
Reproducible with: 2020.1.8f1, 2021.1.0a1 (The VM was only set up for these two versions)
Note:
- If you create any other asset in that folder it will be marked as "Local"
- It seems that asset move does not work in other situations too (check case edits for Scenario 1 and Scenario 3)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0b8