Hi, how does file path resolution work for nested instances? It appears as if all paths are relative to the current project and not to each file instance. Can anyone verify this? And is this good or bad?
I have several life-long projects, one of which is a model of my appartment. For this I have used bits and pieces from my old appartment model and the projects are separated in folders for use as file instances. Here are some example files and how they are arranged in folders: Project root: Apartment.prj Project Root/Textures: (Images used for textures in the main building) Project root/Furniture: Computer Rack.prj Project root/Furniture/Textures: (Images used for textures in the various pieces of furniture) Project root/Furniture/Equipment: Computer.prj Project Root/Furniture/Equipment/Textures: (Images used for textures in the equipment) The main project, "Apartment.prj", includes a file instance referring to "Furniture/Computer Rack.prj". The computer rack, in turn includes a file instance referring to "Equipment/Computer.prj". When working on "Computer Rack.prj", the geometry can be loaded, but when working on "Apartment.prj", the geometry of "Computer Rack.prj" can be loaded, but thge geometry of "Computer.prj" is not shown. I only use relative paths in the file instances as I sometimes work on a different PC where the location of the project root is different. Is there a way to make the paths relative to each file instance or is there a better way to organise the pieces? The idea here is, of course that the same furniture and equipments is supposed to be used in different projects without the need for tedious copying and version management. Best regards, Fredrik
