Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.30f1
6000.0.0b11
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-17928
Regression
Yes
[VCS] Local package files and Project Settings are automatically marked for add after VCS is reconnected/refreshed
How to reproduce:
1. Create a new project in your prefered workspace and open it
2. Connect it to Perforce
3. Add a local package (Drag a separate package to the "packages" folder)
4. Observe that its files are all automatically marked as add (This is expected since this is a local package)
5. Revert some of the files and refresh the VCS Window (Thre reverted files should be marked as "local" instead of marked for add)
6. Observe their status again
Expected result: the status remains "local" (the red dot icon)
Actual result: the status reverts back to "added local" (the plus sign)
Reproducible in: 2020.1.0a1, 2019.3.0b1
Not reproducible in: 2019.2.3f1, 2018.4.7f1
Note: This also means that the local package files or project settings cannot be reverted in the VCS Window, they will be re-added upon reconnect/refresh
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Resolution Note:
We will be revisiting this issue in six months when we plan to make a great improvement in the P4 plugin.