Author Topic: Relative path issue (actually absolute until template has been 'saved as')  (Read 1579 times)

0 Members and 1 Guest are viewing this topic.


  • Community Member
  • **
  • Posts: 1
    • View Profile

I have setup my template to have relative path on all inputs and outputs, also to auto-refresh inputs and "Save the file every time the world machine is built".
The "Default Relative File Path" is set as well.

When I copy the template itself to a new location, load up the template and run the build.. The input/output file locations are still loaded and saved to my previous location, it is not relative.
The relative locations are updated correctly if I load up the template from it's new location and then choose save as, overwrite the file again from the interface. Only after this is done, will the relative paths work.

In order to fix our automation scripts, we need to find a workaround or get a bug fix from you guys.

Any ideas?