Just store a local copy of the UE5 project folder under a common file path structure on each machine, for example “Documents/Aximmetry/Projects. Use the buit in Sync tool in Aximmetry to push updates to each machine or use the file sync/version control tool of your choice. 

That's what I did, although not with the Sync tool. Even when every machine was seeing the same local files in the same place, and each Render Config was set the same, I kept getting all sorts of Projects etc not found errors.

Well at least I know I was headed the right way, so thanks. I'll try just with one render machine and see where I'm going wrong.

I'm still missing something. I've got all the same files in the same directory structure on both the control machine and the remote renderer (see below). But when I Start the remote render, it immediately coughs up the error below in red. I'm running the .xcomp file on the control machine from the local drive, and there's a matching one of that on the remote renderer too. I just don't get it.

Hi,

You can have a local copy of the Unreal project on every computer with the same path, ensuring that the .uproject file is located in identical folders and drives on all machines. Afterward, you can set the Unreal module's Import Source to that path. Although you will receive a warning about a sharing problem, you can safely disregard it:

You should keep the Aximmetry libraries meanwhile in shared folders and make sure all computers have the same networked path (shared folder) as the Project Root folder in the Preferences of Aximmetry.

However, it is highly recommended to make this work with network paths (shared folder), potentially by preloading your levels (sections) or by having a faster router for your local network between the computers. Having the project centralized in one location greatly helps in editing it, and enables you to make quick changes between shots.

Warmest regards,

Yes, that's what I'm doing, and it's not working. I'm used to seeing that Sharing Problem dialog popup (and dismissing it), but the error I'm getting is more fundamental. The remote machine won't even start. In the Engine Status popup, I'll see it say "Running" for a split second, and then that error I referenced above shows up, and the renderer dies on the remote machine.

We're still running Composer build 2023.1, but that shouldn't matter, should it? There must be something else in our config somewhere that's not right.

Paul

Hi Paul,

You can not dismiss this error:


All your project root folders should be network paths, and they must be identical on every computer. Network paths, for example, can be shared folders or drives, and they typically start with "\\", like:

By doing so, you should no longer encounter the error stating that Projects are not shared.

Note that when you set the import source of the Unreal module to a direct path — one that starts with the drive letter, rather than to one of Aximmetry's project folders — the Unreal project isn't required to be in a shared folder or be part of the Project root folders.
However, the Aximmetry libraries (namely Common and Common_Studio) must be located in shared folders and be part of the Project root folders.

Running on version 2023.1 should not affect this, as these requirements have remained the same since then.
Note, starting with Aximmetry 2024.1 you can install multiple versions of Aximmetry on a computer, so you can easily test your setup with the newest version of Aximmetry.

Warmest regards,