After Migrating to UE5.5; Perforce in Visual Studio tries including everything

AreYouTheBot020
Sat, 10 May 2025 16:17:20 +0000
Programming & Scripting

my team have been working in EGS installed UE5.1, and we decided to move to EGS installed UE5.5; The migration was successful, but now Perforce is behaving strangely.

when I generated a new .sln for the new engine version it includes a bunch of programs, and tools that were not there before, so when I try to attach P4 to VS through the Helix Core extension I get hundreds of attempts to include files from /Engine.
with log statements like:

[Error: P4API.NET] 10/05/2025 08:19:57.3630 : Failed: Path 'd:\Unreal\UE_5.5\Engine\Source\Programs\AutomationTool\AutomationUtils\CommandEnvironment.cs' is not under client's root 'D:\Perf\MyProject'.
and
[Fatal: Next Exception] 10/05/2025 08:19:57.3770 : Perforce.P4.P4Exception:Path 'd:\Unreal\UE_5.5\Engine\Source\Programs\AutomationTool\AutomationUtils\ScriptManager.cs' is not under client's root 'D:\Perf\MyProject' .

this is by design to ensure no cross contamination and bloat in the repository, as this is a EGS install
I went into the p4ignore and added
“/Engine”
to the directories list, but it still is attempting to add hundreds of things which inevitably cause the IDE to lock up, and crash.

I think this has to do with the .sln including a /Programs, /Rules directory which all have hard references to engine files, and Perforce is trying to include those, but I can’t get access to the setting until I attach the Helix Core Extension to the project which is where the IDE crashes.

1 post - 1 participant