After upgrading our project to UE 5.7.X, we noticed weird behavior when trying to rename assets in Unreal Editor (see repro steps). We’re pretty sure it wasn’t the case in earlier versions of the engine. Is this behavior something intentional with 5.7?
Have an 5.7.4 game project + UE 5.7.4 Engine downloaded from Epic’s P4 stream (`//UE/Release-5.4` stream)
Both the game and the engine are added to P4 source control
Create a new asset (for example blueprint) and submit it to the P4 depot
Rename the same asset in Unreal Editor - notice the popup showing and the renamed file being treated as a new file in P4V instead of a renamed file (see attached screenshots)
Hi Kryzsztof, I think I see what may be happening - for some reason the deferred add from the initial copy of the file has not yet run when the copy operation happens, which is what performs the integrate, and this error is coming from Perforce directly because of that order of operations being out of sync. Is the team running with auto add new files to source control enabled or disabled? I’m just curious as it’s not a report we see often, but we typically have auto add new files setting enabled.
I understand why we’re loosing the connection with redirectors, but still, the popup is pretty confusing (especially for the non-technical part of our team). It suggests that something went wrong while the process has been finished successfully. Are there any plans to improve that?