missing particles on renders. im just using the native c4d emitter. below are the pics from 3 frames. frame 504, 505 and 506.
happens a few times already on other scenes. no problems on viewport.
c4d version : 2023.1.2
cuda driver version 12.0
OctaneRender Studio+ 2022.1 (12000020)
Particles Sometimes missing from render
Moderators: ChrisHekman, aoktar
Try baking the c4d particle system. I vaguely remember there can be problems because c4d's particles get recycled when the particle dies.
Otherwise you could try replicating what the particles are doing by using a cloner/matrix in mograph. Or maybe use a mograph cloner to clone onto the particles and just render the cloner geometry so octane never has to see the particle data.
Otherwise you could try replicating what the particles are doing by using a cloner/matrix in mograph. Or maybe use a mograph cloner to clone onto the particles and just render the cloner geometry so octane never has to see the particle data.
here is a simple test
https://we.tl/t-DYj0ccknlb
here is the test scene project
Last edited by wetfusion on Wed Feb 01, 2023 10:15 am, edited 1 time in total.
intel 17 4770k (MSI MPOWER MAX)
32GB 1866ghz corsair dominator platinum
2x MSI 780 lightning
Plextor M5 256GB
32GB 1866ghz corsair dominator platinum
2x MSI 780 lightning
Plextor M5 256GB
thanks bro. i will try it nowboxfx wrote:Try baking the c4d particle system. I vaguely remember there can be problems because c4d's particles get recycled when the particle dies.
Otherwise you could try replicating what the particles are doing by using a cloner/matrix in mograph. Or maybe use a mograph cloner to clone onto the particles and just render the cloner geometry so octane never has to see the particle data.

intel 17 4770k (MSI MPOWER MAX)
32GB 1866ghz corsair dominator platinum
2x MSI 780 lightning
Plextor M5 256GB
32GB 1866ghz corsair dominator platinum
2x MSI 780 lightning
Plextor M5 256GB
i tried as @boxfx suggest.
baking the particle didnt solve the problem.
but putting the emitter as cloner object solve the problem. so its related to how octane reading the emitter particle data?
hope @aoktar can have a look at it and maybe fix it.
baking the particle didnt solve the problem.
but putting the emitter as cloner object solve the problem. so its related to how octane reading the emitter particle data?
hope @aoktar can have a look at it and maybe fix it.

intel 17 4770k (MSI MPOWER MAX)
32GB 1866ghz corsair dominator platinum
2x MSI 780 lightning
Plextor M5 256GB
32GB 1866ghz corsair dominator platinum
2x MSI 780 lightning
Plextor M5 256GB
Please always use the C4D Particles Emitter as source for a MoGraph Cloner in Render Instance mode.
In this way, also motion blur is supported: ciao,
Beppe
In this way, also motion blur is supported: ciao,
Beppe
Yes as Beppeg say you should use Cloner or particles tab from object tag. Otherwise no stable IDs to track the particles in motion engine.bepeg4d wrote:Please always use the C4D Particles Emitter as source for a MoGraph Cloner in Render Instance mode.
In this way, also motion blur is supported: ciao,
Beppe
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw