Populate and DBR

[Anonymous]

Has anyone had any luck rendering populate people using DBR? 

Because the textures are stored locally the slaves dont have access to the local temp file and therefore cant render the texture.

is there any way around this?

Thanks

 JHV

[nicolas.holst]

Hi Justin,

It should work fine as long as you don't have the option 'distributed maps' ticked. With that option checked every machine will try to access the maps directly, with it not checked the master machine will pass the textures on to the other machines.

Nicolas

______________________________________________________________

If my post answers your question, please click the "Accept as Solution" button. This helps everyone find answers more quickly!

[Anonymous]

I am using Vray to render so that option isn't available

[Anonymous]

I have re-mapped the TEMP folder to a shared network folder as it is working now

[hamilton3d]

Do you mean you put all the maps somewhere on the network so that all machines can see when DBR'ing?

I am running into the same issue and I don't want to tick "include maps" to add to the file size when submitting a scene to the farm to DBR.

Any and all thoughts are welcomed.....

-Greg

[jneilon]

We have the same issue. You can temporarily fix this like hoppergrass mentioned but you will need to do this each and everytime you create a new Populate setup since each user generates new unique maps. Submitting including maps is not a solution so it is currently unusable.

[hamilton3d]

JNeilon

I am not sure what you mean that including maps is not an option. I am currently running a simulation with the "include maps" ticked when network rendering and it is picking up the maps for the populate people splendidly.
However I do not feel this is a valid solution since most of our scenes are quite large with many maps and submitiing with maps included for those jobs would really bog down the network and the job completion speed.

Have you not had luck with using the include maps tickbox?

[jneilon]

hamilton3d

It is a solution but not ideal. All the jobs I work on are too big to include maps while submitting jobs. The only temporary solution when working with large files is to copy the maps to a shared drive each time you create a new instance of populate.
Populate needs to be rewritten to use the same maps each time you generate people and have them in the max directory not the user directory.

[Pixelschmiede]

I am working with vray too and thet map issue is a big problem... populate is nice and very easy to setup, but autodesk has to accept there are other rendersystems than iray and mentalray.

please fix this for the next SP. thanks.

best regards

themaxxer

[Anonymous]

sorry to revive an old thread, but its hard to get any dedicated forum about this. The problem we have is that the people themselves, not just the bitmaps,  are not showing up from the buckets done by the render slaves. Our IT has all machines setup fairly similar. All are using 3ds max 2014 and vray 3.0

Any help appreciated.

Thanks!