long export times for vrmesh and alembic and huge file sizes. Use on render farms
#3
(03-05-2022, 01:26 PM)tyFlow Wrote: The reason for that is because the VRay and ABC exporters don't support instancing. So, when exporting as tyCache if you have a million particles that share 1 shape mesh, the export will contain 1 shape mesh and a million transforms (very light). However, when exporting as VRMesh/ABC you'd end up with a million meshes (very heavy).

ABC does technically allow shape collapse, meaning you could get the 1-shape-million-transform result, but there are a lot of caveats that come with it, so I haven't been able to implement it yet.

Any reason in particular your renderfarm can't have tyFlow on it? Then you could export/load with tyCache which will be the quickest method.

If you export as PRT or ABC point cloud it'll be similarly light to tyCache, but you won't have the shape data. Depending on what exactly you're rendering, you might be able to add a shape mesh after. For example, you could use the VRayInstancer plugin to scatter shapes on a particle cloud.

Ah okay that makes sense. thank you.

Its a cloud renderfarm actually, and they just don't support it right now. they have plans to but the options they gave were alembic export for the time being. 

Would the vray instancer keep the mapping data do you know?
  Reply


Messages In This Thread
RE: long export times for vrmesh and alembic and huge file sizes. Use on render farms - by ldotchopz - 03-05-2022, 02:40 PM

Forum Jump: