Perforce Integration Renaming / Moving Workflow Bugs?
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?
asked Jul 14 '14 at 07:51 PM in Bug Reports
The current (4.10) behavior is improved: it does a
The best way to follow the history of an asset is with the p4v Revision Graph (Ctrl+Shift+R).
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.
answered Jul 15 '14 at 08:42 AM
Tom Sarkanen STAFF
Follow this question
Once you sign in you will be able to subscribe for any updates here