Perforce - something totaly wrong

  1. I have my usual workspace and file which mentioned as latest 20 revision.

  2. I have new workspace and latest file revision mentioned as 14. I have just created that workspace and geted latest revision.

  3. I can clearly see my 981 commit in second workspace where mentioned that file revision was changed to 18 (after in another revision to 19 and 20). But if I try to get this revision in second workspace it told me that there is no such revision.

  4. I have another sympot: some files which was in depot sometimes mentioned as not in depot.

  5. Sometimes files which were deleted from depot appearing again.

I don’t undestand where to begin to dig that problem.

I think the problem is in our workflow process. Some people commiting changes of assets through unreal engine. And someone commiting them through p4 visual tool.

Ok, with have found the root of all problems. Folders renaming.

  1. Install linux perforce server, add unreal engine project to depot

  2. Create directory test

  3. Add blueprint testActor

  4. Submit this blueprint to depot.

Now I want to rename test to Test. What should I do ? Unreal engine have no such feature. And here I have to report about 2 bugs:

  1. If I will try to rename folder from test to Test2 and after that to Test, I will get two folders: Test2 & Test with same blueprint. And UE4 won’t display blueprint in second Test folder.

  2. If I will copy test to Test2 in explorer, remove test from perforce, rename Test2 to Test and add it to perforce then blueprint testActor will stay in test by inner information.

So, main question is: how to fix it ? Some recache?

You have come across the redirector system. When you rename “test” to “Test2”, a new asset called a redirector is left at the old location with the same name. You can see this asset in UE4 by enabling the “Show Redirectors” filter in the content browser (in “Other” section of the filters menu).

If you want to remove the old “test” folder and its contents, you will need to right click and “Fixup redirectors in folder”. This should update references to your redirector to point at the newly copied asset. You can then commit these changes to source control.

If you move assets around outside of UE4, as with bug #2, the editor will not be able to keep track of references to that asset so errors can easily occur.