regular "fail"-frames in particles-animation

[mesut]

hi,

the setup is: cached realflow-particles (prt-format), brought into the scene via xpcache object.

the problem is: every 20 frames (exactly regular!) there is a "fail"-frame being rendered. this already shows in octane standalone after the export from c4d.
in the live viewer this does not happen. also, during the export-process there is no such behaviour visible in the editor.
motionblur is disabled on the particles via object-tag. but even if all kind of mblur is disabled generally via render settings, this happens.
what could be the problem?

EDIT:
sorry, forgot a massively important info: i don't experience this, when i render in the picture viewer.
this happens when i use "export to animated package" and render out of standalone.
unfortunately, rendering in the picture viewer is no option, in this case.

EDIT2:
here's the orbx file:
http://www.mesutcapkin.com/temp/Skiptest_solo.zip

EDIT3 (sorry):
maybe another interesting information would be: the same simulation had been done with 100 times more particles. in that case the "fail"-frame was not exactly every 20 frames, but exactly every 10 frames.

left hand shows the octane version, the right hand shows the standard renderer.

[bepeg4d]

Hi,
which exact version of plugin are you using?
Have you tried to export to Standalone with a different version of plugin?
ciao Beppe

[mesut]

thx for the quick response. that's helpful since i'm in production and this seems to be a showstopper.

if you refer to the octane-plugin version: it's the stable one. the standalone is the stable version, too.
haven't tried it with another version. which one would you recommend trying, there are so many of them...

Hi,
which exact version of plugin are you using?
Have you tried to export to Standalone with a different version of plugin?
ciao Beppe

[bepeg4d]

Hi,
if you are working with 3.08, please, try with 3.07-R2, and report back, thanks.
ciao Beppe

[mesut]

ok, will do.
so, i guess, i'd also need to link the 3.07 R2 plugin to its corresponding standalone version, right?

Hi,
if you are working with 3.08, please, try with 3.07-R2, and report back, thanks.
ciao Beppe

[mesut]

so,
plugin version 3.07 R2,connected and exported to 3.08 standalone: no difference to prior situation.
now trying exporting to an older standalone.

ok, will do.
so, i guess, i'd also need to link the 3.07 R2 plugin to its corresponding standalone version, right?

Hi,
if you are working with 3.08, please, try with 3.07-R2, and report back, thanks.
ciao Beppe

[mesut]

ok, tried it now with 3.07 R2 and 3.07 standalone: no difference.
what now?

so,
plugin version 3.07 R2,connected and exported to 3.08 standalone: no difference to prior situation.
now trying exporting to an older standalone.

ok, will do.
so, i guess, i'd also need to link the 3.07 R2 plugin to its corresponding standalone version, right?

Hi,
if you are working with 3.08, please, try with 3.07-R2, and report back, thanks.
ciao Beppe

[bepeg4d]

Hi,
another option is to export the particles with c4d internal Alembic export, then import back the .abc file in c4d, or directly in Standalone (you need to change the scale of the .abc node after importing).
ciao Beppe

[mesut]

how would i do that properly?
when it try and export it, i only receive a small-sized file (7kb) which only contains the sphere that originally is being used as the particleabject within the octanetag.

Hi,
another option is to export the particles with c4d internal Alembic export, then import back the .abc file in c4d, or directly in Standalone (you need to change the scale of the .abc node after importing).
ciao Beppe

[mesut]

now this seems interesting - went back to 3.08 on all ends.

went back into realflow and exported the particle-sim as abc-format and stitched the abc-particle-files to 1 single abc-file (or else it won't import poperly into c4d).
while using the octane-scatter to propagate an object onto the vertex of the abc-file results in the same fail-frame situtation as before, a different thing happens when importing that stitched abc-file directly into standalone.

here's the orbx that contains the original geometry.abc with its flaw, and additionally there is the "stitched.abc" imported and connected.
http://www.mesutcapkin.com/temp/failfra ... itched.zip

most interestingly the flaw seems to be gone with that one connected.

to be honest, this is quite a troublesome workaround (with the "real" simulation-data, that is. right now, this is only a few test-particles...).
would love it to have it work "properly".

sooo...
if there's a bug... where is it? in c4d, in octane-c4d-plugin, in standalone... or in the abc file-format?

how would i do that properly?
when it try and export it, i only receive a small-sized file (7kb) which only contains the sphere that originally is being used as the particleabject within the octanetag.

Hi,
another option is to export the particles with c4d internal Alembic export, then import back the .abc file in c4d, or directly in Standalone (you need to change the scale of the .abc node after importing).
ciao Beppe