Source Control - Renaming an asset should keep its history in source control!

[Sebastien_Binet]

I would like to suggest that the unreal engine editor 4.17 be improved to better handle the source control history when renaming/moving assets.

Currently, when the artist renames an asset (AName_PhysicsAsset.uasset to ANewName_PhysicsAsset.uasset) in the content browser then fixes-up redirectors, this results in a loss of all AName.uasset history.

In the attached pictures, we can see that after all the operation the ANewName_PhysicsAsset.uasset has only one version in Perforce History.

Would it be possible to improve unreal Editor code to use the Perforce “Rename/Move…” functionality so the history would be kept when the artists rename asset?

[Sebastien_Binet]

@**kjustynski: **Perforce handles correctly the history when we rename directly in the P4V UI.

[ianFisch]

This still seems to be an issue in Unreal Engine 4.26!!!

When I move or rename a uasset, the perforce history of that asset only goes back as far as when it was moved/renamed (see image below).

This is pretty unacceptable in the year 2022!

It basically discourages developers from keeping assets organized, since renaming or moving something destroys your ability to see its revision history.

This isn’t an issue in the Unity game engine. Just saying.