Relative path for project?

Content Creation Composer

 

Hi I'm working on the multi-machine setup. Does Aximmetry support relative path?

For example, I've set the project root D:\TestProject\ on the controlling machine, and set the project root ControllingMachine\TestProject on the satelite machine. And is it possible in the project node, I could set it something like Root\Test.uproject? So that both machines could get the right path?


Currently I always got the Remote File Sharing Problem. 


It would work if I set the project path as E:\text\\\DESKTOP-005IJLP\text\text.uproject.


Thanks.

   MEGO-XR

 
Profile Image
Eifert@Aximmetry
  -  

Hi,

In a multi-machine setup, you have to have access to the same folders and files by all the machines. You do this by sharing the project folder over the local network and then specifying that as the Root folder in each machine: https://aximmetry.com/learn/tutorials/for-studio-operators/setting-up-a-multi-machine-configuration/#project-root 

If you want the machines to use different files, you can use the System Params module's Engine pin to switch between files based on the machine's ID. For example:

This however will not work in the case of Unreal node in Aximmetry. Cause for example Aximmetry has to know the pins of the Unreal node before starting the compound.
So if you have different Unreal projects, but want them to be handled by Aximmetry in a multimachine setup where you would want different machines to load different Unreal projects. You could do it by putting the different Unreal projects into one Unreal project and separating them by levels (maps). You could load different levels on machines by using the System Params module's Engine pin and triggering a level change for that machine in Unreal using Get Aximmetry Trigger: https://aximmetry.com/learn/tutorials/for-aximmetry-de-users-unreal-engine-5/ue5-how-to-install-and-work-with-the-unreal-engine-based-de-edition/#get-aximmetry-trigger

Warmest regards,


 
Profile Image
dirkteucher
  -  

I would also like to use relative paths for the "Import source"


Aximmetry uses an absolute path to get the Unreal project file. For example "C:\unreal\GDS-Studio-Project\GDS_Studio_System.uproject"

But we have an aximmetry folder located here "C:\unreal\GDS-Studio-Project\GDS Studio Compound\GDS_Aximmetry_Compound.xcomp"

And this is stored in version control. So when we download the project to another drive or another location on a different machine we want to be able to use relative path to select the uproject file in the parent directory. EG: "../GDS_Studio_System.uproject"


Is this possible?

Relative path for project?

 
Profile Image
Eifert@Aximmetry
  -  

Hi Dirkteucher,

Please consider what was mentioned in my previous post if you are doing a multimachine project.

Otherwise, you can establish a relative path by initially adding a parent folder of your Unreal Project's folder to the Project root folders. This can be done at Edit -> Preferences - General. (Perform this action on every computer involved):
Relative path for project?

Note: Adding the folder containing the .uproject file to the Project root folders will not work, as the relative path must begin with the name of a folder.

Afterward, please restart Aximmetry. Once restarted, you have the option to update the Import Source to a relative path. This can be achieved by dragging and dropping the .uproject file into the Import Source field:

Warmest regards,

 
Profile Image
dirkteucher
  -  

Thanks for your response but no this does not solve the problem. We use a seperate network in the studio so cannot use a networked folder. And the second method you mentioned will still require us to manually select the locations for our source files in multiple places each time we pull a project from git which does not save us time or help improve our workflow.

Aximmetry could be improved by allowing relative paths in nodes that are linking to files on directories on the disk. I hope you put this on your roadmap.

 
Profile Image
Eifert@Aximmetry
  -  

Hi Dirkteucher,

It appears there might have been a misunderstanding. While it's necessary to select the parent folder of your source files for Project root folders on every computer, there's no need to overwrite the Import Source in the Unreal module each time you pull from the git. This step should be completed just once, and then the compound should be committed to the git:

For example:

On computer A, the Unreal project is located at:
C:\UEProjects\GDS-Studio-Project\GDS_Studio_System.uproject

On computer B, the Unreal project is located at:
D:\UEStuff\GDS-Studio-Project\GDS_Studio_System.uproject

In this case, you should add the following folder to the Project root folders:

On computer A the C:\UEProjects
On computer B the  D:\UEStuff

Then set the Unreal module's import source to [GDS-Studio-Project]:GDS_Studio_System.uproject in the git version of the compound.

Warmest regards,