VRay Proxy export / Standalone Issue
#2
Hi Robert,

1) I will make sure in the next build that tyCaches support relative path input.

2) In order for the vrmesh exporter to export tyCaches/tyFlow particles, you have to make sure they're not being processed by the GPU instancing system which bypasses regular max mesh methods and sends meshes straight to the GPU. When particles are instanced, they have no max-accessible mesh, so exporters will see tyCaches/tyFlows as being empty. Just disable GPU instancing in any tyCaches, and be sure to give any tyFlow events you want exported Mesh operators set to non-render-only.

3) tyCache export is probably slow because they have 2 phases. The first phase exports particle transforms, the second phase exports particle meshes corresponding to those transforms. If you have a lot of unique particles (ex: a highly detailed voronoi fracture), the transform phase will be very quick, while the mesh phase could be very slow depending on the setup (because it may be writing thousands of meshes to disk or whatever). Although "slow" should only be a few seconds in most cases....15 minutes is definitely odd although I haven't had a chance to dig into your scene yet to find out why.

4) It's perfectly legal to use the beta for commercial purposes, and says so on the download page explicitly, and the EULAs terminology is inclusive of commercial work as well.
  Reply


Messages In This Thread
RE: VRay Proxy export / Standalone Issue - by tyFlow - 07-26-2019, 06:28 AM

Forum Jump: