Randomize texture using vray

[wesley]

Hi, I tried but failed to randomize the textures when using vray's vrmesh for rendering. All geometries are using the same shader plugged into the vraymeshmtl nodes. Of course I can write a script to do some connections to randomize the texture, but I wonder if there's a more convenient way provided by Miarmy.

Also, the process of outputting the vrmeshes is really long, it is done agent by agent, each one has to go through the whole animation once. Hope that there is a way to improve this in the future.

[Yeah YANG]

Aug 27, 2012 22:51:10 GMT -5 wesley said:

Hi, I tried but failed to randomize the textures when using vray's vrmesh for rendering. All geometries are using the same shader plugged into the vraymeshmtl nodes. Of course I can write a script to do some connections to randomize the texture, but I wonder if there's a more convenient way provided by Miarmy.

Also, the process of outputting the vrmeshes is really long, it is done agent by agent, each one has to go through the whole animation once. Hope that there is a way to improve this in the future.

Thank you for your question wesley,

I'm sorry for the late reply,

we suggestion you can use mesh drive 2.0 to export to vrmesh and it can automatically randomize the shader.

and it will export one time for all agents.

hope this can help

mesh drive 2.0 will not use any of hard disk space

Thank you for your testing!!

[wesley]

I tested the mesh drive 2.0, it's quite fast and less ram-demanding than I thought. The downside is I'll need a Miarmy license for each of the machines that will do the rendering, (I have a pro license on my working machine already) . If I use vray proxies or 3delight, there will be no such limitation after all agents have been exported. I see that all agents have their cache exported but can only duplicate 100 of them. It will be great if the limtation is imposed on the export cache process rather than the duplicate meshes process.

[yeahy2]

Sept 4, 2012 5:00:29 GMT -5 wesley said:

I tested the mesh drive 2.0, it's quite fast and less ram-demanding than I thought. The downside is I'll need a Miarmy license for each of the machines that will do the rendering, (I have a pro license on my working machine already) . If I use vray proxies or 3delight, there will be no such limitation after all agents have been exported. I see that all agents have their cache exported but can only duplicate 100 of them. It will be great if the limtation is imposed on the export cache process rather than the duplicate meshes process.

if you have a license, you can export vray proxy and 3delight proxy from the duplicated meshes~~ you just need select all the mesh and use maya exporting.

Yes mesh drive is 4 times faster than Alembic Mesh for Miarmy Agents but no need export any geo cache~:')