Renaming / Moving in UE4 with perforce integration may be working as expected right now (According to a few other answers I have read), but I have to ask if there will ever be a way to keep asset history in perforce when performing a rename or a move. Right now when you rename or move a .uasset it creates a re-director with the same name as the old and adds a new file in perforce with the new name at the new location. The issue with this is that it destroys history in perforce… without knowing where the file used to be located, you end up getting the new file without any of its revision history in it. Is this planned to be added in the future or is this kinda like a “deal with it sorry” type situation. I feel it negates a lot of what perforce is there for and feels like it is a bit of a jenky setup.
Would a possible solution be to have the redirector embedded in the actual uAsset itself kinda like how it used to do in UE3 packages so that way in p4 you can literally call a rename or a move?
We are working on this - we wanted to ship this feature (retaining history with copy/move) in 4.3, but it was reverted close to release because of a few issues we discovered. Pretty certain we should have it for 4.4 and the code is already in the master branch for subscribers to check out if they want here.
Are there any updates on this? Is this feature still only available in the source code? I didn’t see any release notes concerning this and I still have the same issue as chriszuko and I’m using 4.6.1. My team deals with it, but it’s less than ideal. Of course this works if done inside of Perforce, but then you break all references inside of Unreal, and we’ve ultimately decided that is far worse.
This is already a noted issue in our database (UE-5259) - I’ll bump it and try to get it addressed soon. I think it already works only in the case that a redirector is not left behind in place of the old file (which is seldom the case).
Right now when you rename or move a .uasset it creates a re-director with the same name as the old and adds a new file in perforce with the new name at the new location. The issue with this is that it destroys history in perforce… without knowing where the file used to be located, you end up getting the new file without any of its revision history in it.
The current (4.10) behavior is improved: it does a p4 integrate and p4 resolve on the file when copying/moving it to maintain the history (you can even see these commands in the Output Log). However, UnrealEd still doesn’t use p4 move – it always creates an object redirector. This means that you won’t see this history in the simple History pane in perforce, but within the History pane there is an “Integrations” tab that will show this history. (I think this limitation is caused by the resolve method – I know it’s possible for integrations to show up in the History panel but they don’t in this case.)
The best way to follow the history of an asset is with the p4v Revision Graph (Ctrl+Shift+R).