Rider for Unreal: attempts to connect to Perforce for installed Engine
Answered
I'm using Rider for Unreal with an installed engine, and my project is kept in Perforce. When I try to configure Perforce, it reports connection errors, because it attempts to use Perforce both for my project and for the engine. The engine isn't versioned -- it's installed by the Epic Games Launcher.
Is there any way to tell Rider to ignore the Engine for Perforce operations? I've attempted to create a .P4CONFIG in C:\Program Files\epic games that has an empty P4PORT, but that seems to just make it fall back to the system defaults.
Please sign in to leave a comment.
Hello Jorgen
Perhaps the error message mentions engine roots, if so please check mapped directories under Preferences | Version Control and remove unnecessary folders from there.
Ruslan Kuleshov, this is what it shows, is that what you mean by mapped directories?
My understanding is that the engine and the game are different "projects", in MSVS & Rider parlance -- but I don't see how to show the settings for a specific project. Any guidance?
Jorgen Yes, thank you for provided screenshot.
You can specify the game directory by click on Plus sign or clicking in <Project> and then pencil picture.
I just ran into the same issue with an installed vanilla version of the engine. What's suggested above does not solve the actual issue. Even specifying only the project directory as an absolute path, no other directories, results in non-functioning version control:
I ran into the same issue, and the solution ahead does work for me. I have removed the entry for <Project> in the Version Control settings window, and added the directory where my project and its P4CONFIG file is located to make it work.
Javier, thanks for pointing that out. I tried again with your directions and the root directory containing the p4config actually worked. I was sure I had tried it before already...
One thing to point out as well is that just changing the directory and then testing the connection still produced the error for me - I had to click the Save button on the settings (exiting the dialogue), then when I went back and tested the connection it worked.