Switching solution configuration in Unreal project is very slow
I often need to switch between different solution configurations, e.g. between a Server and a Client version of our Unreal project, to be able to build and test each one.
In Visual Studio this operation is basically instant. But in Rider, this takes almost two minutes while it is ‘Syncing projects…’, without even counting the subsequent ‘Processing files’ stage.
It appears to be spending most of this time regenerating JSON files under the `Intermediate\ProjectFiles\.Rider\Win64\` directory, but I expect the content here is going to be exactly the same each time I switch.
Is there any way to speed this up? Or maybe an existing issue I can vote on to encourage someone to look into improving this?
Please sign in to leave a comment.
Hello Ben,
Thank you for contacting Rider Support and for sharing your feedback. It is true, Rider re-generates project files on solution configuration change. We have this request registered on our tracker: RIDER-118508 Consider speeding up switching Target Game<->Editor. It is on our radar, and we have an idea for the improvement. However, I have no ETA to share on when this will be implemented.
Do you open your project via the .sln file? If so, you can try switching off the Regenerate project properties on configuration change in Settings | Languages & Frameworks | C/C++ | Unreal Engine.
Unfortunately, I have no other suggestions at hand right now. Please tell me if the suggested option helps or not.
Have a nice day!
I'm developing a multi-player Unreal game using the Rider IDE. When opening up a Rider UProject switching between Editor/Client and Server targets does take 2 mins plus. But if you open up a Rider project this does not exclude the modules stopping source code development. In fact in the latest Rider compiler macros #if UE_SERVER etc don't just grey out the code but now dim a proper syntax highlighted version of the code.
The way i work is to leave it in Editor target and simply allow the packager to rebuild the code when i test my server.
Probably not the perfect solution but it seems its the fastest iteration i have found using this setup.
I don't have a problem editing the source files, but around compiling and debugging, and stepping through areas where the flow is quite different for client, editor, and server builds. There really isn't a workaround for that - except using Visual Studio which does not have this problem.