X-particles motion blur still broken

[smessing]

Hey Aoktar

I and others have mentioned significant issues with x-particles integration. Are the motion blur issues going to be fixed in Octane with X-particles? We cannot use octane anymore as a result of this basic integration that Redshift and Cycles simply do not have an issue with.

A simple particle emitter with a vertex speed motion blur tag crashes c4d in many scenarios. I turn off motion blur and it renders fine. There was also the issue of certain scenes multiplying in render time with motion blur turned on at a certain frame threshold - I understand this may have been fixed or improved?

It makes octane very unusable for a ton of people that need basic particle, fluid, liquid water sim, etc

Any incite is much appreciated as I am very close to jumping ship as are people in my department.

Thanks
-Steven

[aoktar]

Hi,
I'm not aware of issues as you said, don't suppose it's something about plugin. It's fine on my example scenes as far as I know. Have you reported your issues with additional data to let me check?

[smessing]

Same issues described here in this thread in January. He posted an example scene. I have mentioned this to Jules. Same issues described multiple times on this board before. Small particles counts show nothing. You need more than a few particles.


viewtopic.php?f=30&t=76688

Also other issues described here: to my knowledge are still broken

viewtopic.php?f=30&t=76145&p=391846#p391846

[smessing]

Attached another scene file here - these issues were sent to you months ago through Jules I believe. This is separate from the crashing issues. Xptrails, generative geometry, etc do not motion blur correctly or at all. They work fine in Redshift and Cycles. I work with large departments in VFX and design. We cannot use Octane as a result of these issues.

[aoktar]

XpTrail is not fully supported for motion blur. Probably because of dynamic point counts