Summary
With update 33.10, Perforce has become unusable as a revision control provider in UEFN. Way back in July of 2023, I reported that there is a “false error” that appears when setting up a perforce workspace ( [REQUEST] [BUG] Better Perforce integration with UEFN ) - this was a bit of an annoyance but you could just skip through it. However, with the update 33.10, the “X” button on the revision control setup dialogue was removed. The workaround was to simply exit the dialogue and UEFN would recognize that perforce was connected. Now, without the X, the only way to close the dialogue (because of the false error) is to close it from the task bar. But doing it that way leaves the revision control in the “Server Unavailable” state.
Additionally, due to past updates, many of the actions in the editor that used to automatically add, remove, or checkout files from Perforce stopped doing this. So the only real workflow to use Perforce is to ignore the UEFN integration and reconcile offline work in P4V. But due to the One File Per Actor system, in P4V, all you can see if name hashes for actors in the level. There’s no way to display the actual actor names without the UEFN integration.
If URC had all of the features we required (namely branching, multiple CLs, and finer control over access control) we’d happily switch, but for now Perforce is the only revision control that UEFN “supports” that has all of the features we need. I’d love to see the Perforce integration fixed ASAP. Thanks!
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
UI/Tools
Steps to Reproduce
Setup a UEFN project. Check it into Perforce using P4V. In P4V, go to Connection >> Environment Settings and click OK. Go back to UEFN, click the revision control settings. Select Perforce, and then click the p4config checkbox. Click OK.
Expected Result
It should accept the perforce connection and the revision control checkbox in the bottom right of UEFN should be green.
Observed Result
Instead, it gives an error like: "Connection Error: Workspace ‘X’ does not map into this project’s directory ‘C:\PROJECT_DIRECTORY’ - where X is the workspace name and C:|PROJECT_DIRECTORY is the actual path to the workspace on your PC. And because there’s no X to close the dialogue, the workaround of ignoring that error no longer works.
Platform(s)
windows
