Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.45f1
2021.3.18f1
2022.2.7f1
2023.2.0a4
Issue ID
UUM-22160
Regression
No
Perforce VCS doesn't show Pending changes when moving an ignored folder which causes a de-sync between P4 and the filesystem
How to reproduce:
1. Install the P4D Server
2. Run the server on localhost:1666
3. Open P4V and create a new Workspace that includes the attached project
4. Open Unity and go to Version Control (Project Settings > Version Control)
5. Select Perforce
6. Enter the User, Password, Workspace name, Server Address and press Connect
7. In Unity, Move the “Folder“ folder (Assets) into the “RootFolder“ (Assets)
8. Go to P4V
Expected result: There are Pending changes that show that the “Ignored~” folder was moved
Actual result: There are no Pending changes that show that the “Ignored~” folder was moved
Reproducible with: 1.17.6 (2020.3.42f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0b15, 2023.1.0a19)
Reproduced on: macOS 12.5 (Intel)
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
- 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
Resolution Note:
Marking it as Won't Fix as it seems a behavior in Asset Database handling tracked hidden files. There's little we can do from the Perforce plugin standpoint without heavily affecting the Editor's performance, and the customer seems to have a workaround
Resolution Note (2023.2.X):
Marking it as Won't Fix as it seems a behavior in Asset Database handling tracked hidden files. There's little we can do from the Perforce plugin standpoint without heavily affecting the Editor's performance, and the customer seems to have a workaround