Tweet
Up till now we have been working with "convert file paths to relative" in our preference settings.
From our workflow point of view we had choosen for this option to be able to be sure that all project scenes, maps, etc. would be stored in the project folder. And if necessary we could easilly move a folder without need to relink bitmaps, xref's etc.
Recently we started using distributed rendering. We noticed that all file paths need to be set absolute. This counts for for all xref's as for all maps inside the xref's. Otherwise the render servers would not be able to find them.
I was wondering how people on this forum encorparate this in their workflow?
We would prefer to use one standard. And up till now this was " convert file paths to relative" in combination with UNC. But as this does not work in combination with DR we are rethinking this workflow.
Would it not be more easy if DR could make use of local file paths?
From our workflow point of view we had choosen for this option to be able to be sure that all project scenes, maps, etc. would be stored in the project folder. And if necessary we could easilly move a folder without need to relink bitmaps, xref's etc.
Recently we started using distributed rendering. We noticed that all file paths need to be set absolute. This counts for for all xref's as for all maps inside the xref's. Otherwise the render servers would not be able to find them.
I was wondering how people on this forum encorparate this in their workflow?
We would prefer to use one standard. And up till now this was " convert file paths to relative" in combination with UNC. But as this does not work in combination with DR we are rethinking this workflow.
Would it not be more easy if DR could make use of local file paths?
