itoo forest motion blur bugs again Tweet

[coilbook]

Hi Paride,
we use itoo forest for scattering moving cars. And again there is no motion blur. If we select itoo forest and enable movable proxy and mb 3ds max would crash, or some itoo objects start flying fast.

HEre are my previous topics about it. Can they finally fix mb for moving itoo? We sue 2019 8.23 ver
viewtopic.php?f=81&t=72662&p=369058&hilit=itoo+motion+blur#p369058
viewtopic.php?f=81&t=71914&p=364537&hilit=itoo+motion+blur#p364537

Thanks

[coilbook]

As you can see some itoo forest have mb but some do not

UPDATE: MB steps play a big role. When you set mb steps for wheels to 32 they jsut disappear.
It seems that moving itoo forest objects must have motion blur set at 2. Even at 3 it starts disappearing. Why?

And eval times between each frame is too high even though forest pack is set as movable proxy

[paride4331]

HI coilbook,
I sent a pm yesterday, could you share that file please?
Regards
Paride

[coilbook]

HI coilbook,
I sent a pm yesterday, could you share that file please?
Regards
Paride

HI Paride,
yes. I just sent you the scene. Thank you

[paride4331]

Hi coilbook,
thanks.
Regards
Paride

[paride4331]

Hi coilbook,
the pluign developers are working on.
Regards
paride

[coilbook]

Hi coilbook,
the pluign developers are working on.
Regards
paride

Thank you. Hopefully they can add the fix to 2019 version too

[neonZorglub]

Hi coilbook,
the pluign developers are working on.
Regards
paride

Thank you. Hopefully they can add the fix to 2019 version too

Hi coilbook,
I had a look at your sample; I think I understand the problem:
The wheels turn at different rate (I guess small wheels for small cars have to turn faster..)
The 'disappearing' wheel has the worst conditions for this issue and the motion blur duration:
between 2 frames, the wheel move a big distance (~ bigger that the wheel itself), and it rotate of ~ 180 degree..
The result of the blend make it change shape and size (almost scale 0), and 'spread' on the big distance .. so it seems to disappear ..
(The big wheels rotate less, so the blending has much less issue)

Some work around to minimize the effect would be to reduce the wheel rotation, or reduce the motion blur duration.
Maybe a small motion blur duration (~0.1) and a big Shutter Time (~400 %) can approach the effect ..

The good way to fix this is to add extra motion blur 'steps', but it doesn't work yet with Forest pack instances.. I'll try to add this soon..
Regards

[coilbook]

Hi coilbook,
the pluign developers are working on.
Regards
paride

Thank you. Hopefully they can add the fix to 2019 version too

Hi coilbook,
I had a look at your sample; I think I understand the problem:
The wheels turn at different rate (I guess small wheels for small cars have to turn faster..)
The 'disappearing' wheel has the worst conditions for this issue and the motion blur duration:
between 2 frames, the wheel move a big distance (~ bigger that the wheel itself), and it rotate of ~ 180 degree..
The result of the blend make it change shape and size (almost scale 0), and 'spread' on the big distance .. so it seems to disappear ..
(The big wheels rotate less, so the blending has much less issue)

Some work around to minimize the effect would be to reduce the wheel rotation, or reduce the motion blur duration.
Maybe a small motion blur duration (~0.1) and a big Shutter Time (~400 %) can approach the effect ..

The good way to fix this is to add extra motion blur 'steps', but it doesn't work yet with Forest pack instances.. I'll try to add this soon..
Regards

Thank you for explaining. One question off topic. Are you guys still planning to support phoenix wetmap particle texture as black and white texture. Right now octane renders them as mesh. Thanks

[neonZorglub]

Thank you for explaining. One question off topic. Are you guys still planning to support phoenix wetmap particle texture as black and white texture. Right now octane renders them as mesh. Thanks

Hi coilbook,
The latest versions now have support of MB steps for Forest pack objects. For the case of your wheel, 8 to 16 steps seems good; you can try different values of motion blur duration and Shutter Time.. and be aware that adding more steps will use more memory and take more time..
For the Phoenix wetmap support, there is a limitation with current vdb system; I'll get back to it while checking the new features of 2020.2 that could help..
Thanks