UE5.5 Remote Executor throws double Slashes Exception

[Rauhm Private (Rauhmnacht)]

Hello,

we are currently trying to setup royal render as the render farm solution for our university's animation program.

We got most application up and running, Unreal Engine originally already worked with the 5.4 version and the file server being mapped to the PCs Z: drive.

But with UE's 5.5 update, as well as our IT department using the Z: drive for a different file server, running parallel to the render farm used file server, it started acting up.

We changed the UNC Mapping to be using the G: drive as well as experimenting with a new project file on the 5.5 version, but when we try to set the Default Remote Executor it crashes Unreal Engine and throws the following error.

I am really sorry for the bad image quality, it was very late when I started gathering some material for this post.

In general I am very thankful for anyone who may has some input on what we did wrong here. It feels like this shouldn't be that big of a problem to figure out, but we have already  been working on this for 10+ hours, and are no step closer to solving this than at the beginning.

Best regards,
Philip.

[RR, Schoenberger]

Hi

 

 

I have taken a look into our support system.
We have a support ticket about Unreal 5.5 issues.

As far as I read our Unreal connection developer has been in contact with some Epic engineers

and they have been able to reproduce the issue.
Their answer was on 5. March that it will be fixed “with the next release”.
5.5.4 was released a few days later, so I assume that version does not include the fix yet as they probably need some days to roll out new fixes.

 

 

> We changed the UNC Mapping to be using the G: drive as well as experimenting with a new project file on the 5.5 version

Just to verify:

You did try a drive mapping for the package?
As the image states it is using an UNC path.

And I know UNC paths do not even work for loading a scene in batch render.

 

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

 

[Rauhm Private (Rauhmnacht)]

Hi,

thanks for the quick response,

actually I wasn't aware of 5.5.4 being out yet.
I tried our setup on that version too, but it did not change anything, so yeah it seems like the fix is not yet in the 5.5.4 version.

Because of the UNC path, I am not sure if I entirely understand what "drive mapping for a package" means.
We configured the RR Server to use the G:/ as its Drive Mapping, see the screenshot below, which lead to above results

We also tried out if the "Do not convert Drive Letters ..." setting would change anything, but it caused UE5 to crash with the same error message, displaying the G:/ Path.

But either way, thanks for the heads up that it is actually an UE issue.

I'll test out if the 5.4 version is still working,

that would at least be a temporary solution,

to show the students how the system is supposed to work.

Sincerely,

Philip.

[RR support, Acampora]

Hello Philip,

I am working on the RR Unreal Engine workflow and although I managed to reproduce the double slash error once, it just stopped happening on my system.

It is a false positive as the faulty path is our python environment path, not an asset location. Version 5.5.4 fixed an issue with headless render so it's a good idea to update to the last version.

About the issue, does it persists if you create another project or delete that project cache?

Kind regards,

Paolo

Royal Render Team

[Rauhm Private (Rauhmnacht)]

Thank you Paolo for the heads up,

I tried setting up the remote executor in UE5.5.4 on a completely new project (even a game project, reactivating the movie render Queue plugin),

But I still got the same error message as shown on my first post.

Sincerely,

Philip.

[RR support, Acampora]

Hello Philip,

We have found the reason for that error: please open the file DefaultEngine.ini and the other *.ini files in your Project\Config folder with a text editor. You will find a setting in the moviepipeline section pointing to \\file_server\RR_ROOT\render_apps etc.

Please remove those lines to be able to start your project again.

Also, please replace the files

\RR_ROOT\render_apps\_submitplugins\UnrealEngine_5\Python\init_unreal.py
\RR_ROOT\render_apps\_submitplugins\rr_original\UnrealEngine_5\Python\init_unreal.py

\RR_ROOT\render_apps\_submitplugins\UnrealEngine_5\Python\MoviePipelineRoyalSubmit.py
\RR_ROOT\render_apps\_submitplugins\rr_original\UnrealEngine_5\Python\MoviePipelineRoyalSubmit.py

\RR_ROOT\render_apps\_config\3D21__Unreal_Engine_MoviePipeline.cfg
\RR_ROOT\render_apps\_config\rr_original\3D21__Unreal_Engine_MoviePipeline.cfg

with the one from this .zip

http://www.render-server.de/download/support/040108_UE_config.zip

Kind Regards,

Paolo

[Rauhm Private (Rauhmnacht)]

Hello Paolo,

sorry for the long wait.

I wanted to wait with changing the config files, until after our IT department has updated the render farm to the latest version (w are now on 9.1.15), as this very well could have also been a reason for why it didn't work.

I did now first try making a new E5.5.4 Game project and set the remote executor there, but it still crashed after the remote executor was selected.

I did then try to replace the config files with those you send over the zip file. Reopening the project and trying to set the remote executor again, but without any luck, it still crashed.

On the positive, at least I can still open the file, as it seems to crash before it is able to do any changes to the config.

Kind Regards,

Philip

[Rauhm Private (Rauhmnacht)]

We recently got to test a UE5.3 File and can confirm it works on the older version.

Is there any new update regarding the issue, or plans regarding UE5.6?

Kind Regards,

Philip