-In fact, there is another way to display the terrain mesh:HHbomb wrote: Thu Jan 29, 2026 10:44 am @NZ : yes I have Particle interface disabled.
I enable just when I have a lot of particles.
Can you tell us when Particle interface must to be activated ?
With Particle interface enabled, you need to enable 'Use particle node's mesh'
- in Render settings / Support / TyFlow (that's for all tyFlow objects)
- or if there is an Octane Geometry modifier for a particular tyFlow object, in the 'TyFlow object' panel.
In current version, when Particle interface is disabled, the tyFlow object is processed as a standard object, and we get a single big mesh with all sub items together (all particles, terrain, other meshes...)
When Particle interface is enabled, Octane will use the instances generated by tyFlow for the particles.
That should be better for performance and use less memory, and work in most cases.
In some cases, there could be some incorrectly supported effects, so Particle interface can be disabled to get a single mesh.
Also, for some types of simulation, each particle is in fact different (a different mesh), so there is not much benefit to use instances. it might even be slower to handle all those different particles than using a single mesh..
For example, the sample tyFlow_deformingFracture_001.max has such many different particles.
It also has an internal mesh (like the terrain case), for the unbroken part of the tube, and several particles for the broken pieces of the tube.
Using a tyMesher can also help to make sure we handle just a single mesh for those kind of cases, but make sure that doesn't result in double rendering (hide the tyFlow object, or disable the particle interface)
