Default library assets lose paths when network rendering

[inkvisual]

Hi!

We are having an issue with the maps on forest pack presets becoming lost on nodes while network rendering with Pulze RM.
I determined this is due to the asset's paths being reliant on project paths that are present when a scene is created on machine A but can be missing when rendered on machine B.
The reason being that in our studio we have different artists working on different projects at once. So machine B using the MXP path config file of project Y may take a render job created by machine A using the MXP of project X and have missing files as a result.

I've searched the forums here for solutions and tried out the registry tweaks suggested here:
https://forum.itoosoft.com/forest-pro-(*)/configure-network-map-locations-for-reg-edit/msg30273/#msg30273

This is kind of ok, but still means that the paths being present for any given render node is dependent on a forest object having been created in whatever project that node happens to be in before
it takes a job on Pulze RM.

Our nodes are used as workstations during the day and take render jobs overnight. So the solution can't disrupt day to day work e.g. copying ini files as suggested here: https://forum.itoosoft.com/forest-pro-(*)/custom-paths/msg36997/#msg36997

The advice I found that I liked best was to resolve all references to absolute UNC paths: https://forum.itoosoft.com/forest-pro-(*)/install-library-on-network-storage/msg32297/#msg32297
However, this is a manual step that an artist would have to remember to take before sending their job to Pulze. We'd like to avoid such manual steps if possible.

So is there a way to get Forest Pack to automatically use the UNC path of the assets imported from the default Forest library rather than use the project paths?
Failing that, I'd be looking for a way to get Pulze RM to specify an MXP to use with each job, but that's for another forum!

Many Thanks,
Jack

[iToo]

Hi,

I don't know if RenderManager includes some tool to handle texture paths automatically.
As general rule in a default Max installation, we suggest to use the method described here for render nodes.

Basically, texture paths should be defined in 3dsmax.ini->BitmapDirs. This can be done manually or from Customize->Configure User Paths->External files.
In this way the Asset Tracker will locate and reassign the right path for each asset, without any user intervention.

Other way is to use the Asset Tracker to resolve the paths to UNC. But as you pointed out, this requires a manual process. I think the 'BitmapDirs' approach is much better.

In any case, Forest doesn't modfy in any way the path defined in the material, and there are several reasons to not do it.
In fact, we try to clean our libraries removing all paths, leaving only the file name.

How does your studio handle the paths for other shared assets (not Forest) ?

Regards,

[inkvisual]

I think I'd already fixed it without realising with the registry tweak to add all the paths of the additional libraries e.g. layered lawns etc. After implementing this I can't replicate the issue anymore!

I was missing the idea that Forest Pack is adding those paths defined in the registry keys whenever it is loaded, not just when we manually create a forest pack for the first time in a session.
So this adding of paths is being triggered whenever we load a scene that has a forest pack object in it.
So it triggers reliably whenever a node picks up a job, regardless of the project that node was using. Project files/MXP are irrelevant.

This makes a lot more sense to me than what I thought was going on!

For anyone finding this in future, the link in the following is good and should be followed, my conclusion after it is false and should be ignored:

I've searched the forums here for solutions and tried out the registry tweaks suggested here:
https://forum.itoosoft.com/forest-pro-(*)/configure-network-map-locations-for-reg-edit/msg30273/#msg30273

This is kind of ok, but still means that the paths being present for any given render node is dependent on a forest object having been created in whatever project that node happens to be in before
it takes a job on Pulze RM.

Thanks again!

[iToo]

I'm glad you could solve it.

I think I'd already fixed it without realising with the registry tweak to add all the paths of the additional libraries e.g. layered lawns etc. After implementing this I can't replicate the issue anymore!

In this case Forest is scanning all library paths, and adding the 'maps' folders to 'Customize->Configure User Paths->External files' automatically.
We included this mechanism to facilitate the rendering of the default libraries. It can be configured in the Library Browser->Preferences.