I’ve recently set up P4 and connected it to UE5. Working in P4V and Visual Studio is quick and painless but any time I have to go through the asset checkout flow in the editor it’s super slow.
I make a change to an asset, click save, and wait about 10 seconds while it queries if the file needs to be checked out. If the file was already checked out, it saves and I’m done otherwise it brings up the check out dialog, I click check out, wait 15 seconds, and then the file is checked out and the save completes.
If I disable version control, saving is basically instantaneous so it’s definitely the cause of the issue.
As far as my experience goes, this is just the way things are. It depends on the speed of connection to the P4V server from your computer, as far as I’m aware. I have worked on a few projects with a few different servers and my mileage varied when working directly from UE4/5, for sure. But it was always, ALWAYS slower.
If you figure out a trick or two to speed it up, I’d love to know about it!
I really hope that’s not the case. The P4 connection is super fast and all of these operations are effectively instantaneous when done through P4V or Visual Studio, so that would mean the UE5 integration is pretty bad if this is the expected behaviour.
Hopefully someone else will have some better news for both of us.
Yeah, both in p4ignore and in the stream settings. I’ve also tested that it works both from the command line and by trying to add those directories in p4v.
Cool, cool. Ok… Have you tried running UE5 with Verbose Logging for P4V?
In the DefaultEngine.ini, under [core.log], add “LogSourceControll=Verbose”. You could probably also use VeryVerbose for more granular logging. That might be able to help you determine any hangups it might be having once you do a few checkouts and submits.
Or according to google’s AI, they suggest using “-log -LogSourceControl=Verbose” in cmd as an argument when running unrealengine.exe but idk how much I trust that.
The TLDR is that UE5 uses the p4 info command a couple times during its process and that was slow. Digging into that, it was the reverse DNS lookup on the server which was the issue and that was happening because the server machine was connected to a VPN. Disconnecting the VPN immediately solved the issue.
