RedShift Proxy Support

[phizikl]

Hi,

is it possible to get RedShift Proxy/instance support soon?

Ive wondered about this since vray instance came out.

Pflow already supports that. all geometry (shape instances) that gets sent out to the renderer are only loaded once.

so i can currently scatter millions of geo with pflow, and send out to redshift, without a problem.

frost however makes one big mesh, far too huge for redshift or other renderers to handle…
can frost work the same way pflow does? or can we add redshift proxy support?

it would be super helpful
thanks so much

[Bobo]

I assume the RedShift developers added the improved support for PFlow? We will have to discuss this with them. We would need a public API or SDK to achieve this in our code. If it is their own internal code and not exposed to 3rd parties, then we would have to wait for them to expose it.

[phizikl]

okay. I wonder that too. I think Pflow just instances at render time no? I doubt they have pflow specific code. But of course need to chek. I will write Redshift now and ask.
This works with v-ray or any renderer I think (but need to double check), pflow its not building one big geo, but just making copies of the one loaded in memory

[phizikl]

ok I just made comparison

PFLOW - Shapeinstancing VRAY compiling geometry takes 30 seconds, renter time was 1min 21

PFLOW, using FROST, without VRAY INSTANCER 3min3 seconds
PFLOW using FROST with vray instancer - INSTANTLY loads

so i think, PFLOW loads the geometry to the renderer differently than FROST does it
it treats the shape instances as instances, and does not send out one big data of geo

[Bobo]

My understanding is that PFlow always makes large concatenated meshes - either a single one (default method in the Render operator), multiple meshes, or one mesh per particle. It is possible that some renderers manipulate those settings internally, but I would be surprised.

help.autodesk.com/view/3DSMAX/20 … 2D10DDAB16

Render Result group

These settings determine how the system converts particles to mesh format for rendering. By default, 3ds Max renders all particles as a single mesh per event, which provides for the most efficient operation under most conditions. However, in some situations each particle should be converted to an individual mesh object by turning on Mesh Per Particle. For example, with particles each of whose face count exceeds 10,000, it’s most efficient to render a mesh per particle. Alternatively, you can opt to combine particles into multiple meshes by specifying a face count and number of particles per mesh.
Certain renderers might require a non-default setting for Render Result. Consult the renderer documentation for further information.
Note: The number of particles Particle Flow can handle per frame is limited only by system resources, but each single mesh is allowed a maximum of 5,000,000 faces or vertices. If the total number of faces or vertices in a mesh exceeds 5,000,000, Particle Flow ignores particles beyond this limit.

• Single Mesh Sends the renderer one mesh object comprising all particles in the system.
• Multiple Meshes Sends the renderer the specified number of mesh objects, each containing the specified number of particles. If the result of dividing the total number of particles by the Particles p/Mesh value is less than the specified Mesh Count value, some of the meshes might contain few or no faces.
  This is a compromise method of operation, and can be used with renderers that cannot handle all particles in a single mesh, but can deal with groups of particles of a certain size.
  [list][*]Mesh Count The maximum number of mesh objects that Particle Flow will send to the renderer.
• Particles p/Mesh The number of particles that each mesh object will comprise.
  [/:m]
  [*]Mesh Per Particle Sends the renderer a separate mesh for each particle.
  This is the least efficient method of operation, but might be required by certain renderers.[/:m][/list:u]
  Note: With the default scanline and mental ray renderers, this method does not support rendering of particles born after the start of the rendered frame sequence. In general, use Mesh Per Particle only with renderers that require it.