OTOY Forums

That's not a matter to get or can't get the speed vectors without having this functionality in our plugin.

aoktar wrote:That's not a matter to get or can't get the speed vectors without having this functionality in our plugin.

ok. i thought the speed vector is just an other name for vertex speed...

las thought for today.
should not the c4d-plugin be able to produce the same output than standalone?

here i downloaded the alembic file, that produces perfect motion blur in standalone.
viewtopic.php?f=33&t=44704&p=229784#p229971

momade wrote:las thought for today.
should not the c4d-plugin be able to produce the same output than standalone?

here i downloaded the alembic file, that produces perfect motion blur in standalone.
viewtopic.php?f=33&t=44704&p=229784#p229971

Of course not. I think you're assuming that things are automatically implemented by a single command. Absolutely not. Lot of calculations and preparation is done while converting scenes. That's not possible without generating and registering the speed vectors for generated octane scenes. As i try to explain that was not easy to read vector speeds of geometries. Even C4D sdk had not efficient methods as i can know. So you should wait for a solution in plugin or try to use in standalone.

aoktar wrote:

momade wrote:las thought for today.
should not the c4d-plugin be able to produce the same output than standalone?

here i downloaded the alembic file, that produces perfect motion blur in standalone.
viewtopic.php?f=33&t=44704&p=229784#p229971

Of course not. I think you're assuming that things are automatically implemented by a single command. Absolutely not. Lot of calculations and preparation is done while converting scenes. That's not possible without generating and registering the speed vectors for generated octane scenes. As i try to explain that was not easy to read vector speeds of geometries. Even C4D sdk had not efficient methods as i can know. So you should wait for a solution in plugin or try to use in standalone.

ok. thanks aoktar. i guess we will use the workflow of generating an animated package of the finished c4d file in the end and adding the alembic fluid mesh in stand alone and render there.

Great. I'm investigating how can we read vertex velocity values from vpost data. I'll give you info.

aoktar wrote:Great. I'm investigating how can we read vertex velocity values from vpost data. I'll give you info.

thank you aoktar. i am also ivestigating sub-frame-motion-blur solution with render layer for fluid...

@miknik: I PM'ed you.

Any chance that the information can be written to an image file, and then applied via the existing texture mechanisms? That would then allow the Octane plug in access in that manner, though it would still be up to the plug in to interpret the information properly, and pass it along to the Octane render engine.

aoktar wrote:Great. I'm investigating how can we read vertex velocity values from vpost data. I'll give you info.

that´s good news! usability of other vertex channels (like age, speed etc.) would be interesting too.