Page 1 of 1
Bug with octane preview and motion blur
Posted: Wed Jul 05, 2017 6:31 pm
by coilbook
Seems like when mb and movable proxy is on octane viewport gets stuck between 1 and 100 samples and does not render. It does not happen to dummies and helpers it happens to actual mesh. Also slaves fail because of this.
This problem did not exist in earlier versions
Re: Bug with octane preview and motion blur
Posted: Wed Jul 05, 2017 6:43 pm
by coilbook
it seems that if adaptive sampling is on and expected exposure is set to 2.5 instead of 1,2,3,4 or something like this Octane viewport is stuck at 1
otoy knew about this bug since early may and still did not address the fix for it. They released about 3 versions since then.
Re: Bug with octane preview and motion blur
Posted: Thu Jul 06, 2017 7:18 am
by paride4331
Hi coilbook,
did you try with other scenes? Does it always happen?
I can not reproduce your issue, could you kindly share a scene where it happens by activating and deactivating movable proxy?
Regards
Paride
Re: Bug with octane preview and motion blur
Posted: Sat Jul 08, 2017 2:22 am
by coilbook
paride4331 wrote:Hi coilbook,
did you try with other scenes? Does it always happen?
I can not reproduce your issue, could you kindly share a scene where it happens by activating and deactivating movable proxy?
Regards
Paride
Hi Paride,
I will try some part of it. The scene is like 2 Gigs in size
It seems like bigger the scene more little problems happen with octane that do not happens in small test scenes
Thank you
Re: Bug with octane preview and motion blur
Posted: Sat Jul 08, 2017 3:21 pm
by coilbook
looks like there was phoenix sim in the scene that was causing octaneviewport to freeze. Hopefully they will fix it soon
EDIT: it still freezes with exposure set to 1.xx I will try to send soem file soon
Re: Bug with octane preview and motion blur
Posted: Mon Jul 10, 2017 5:21 am
by neonZorglub
Hi Coilbook,
Several issues related to viewport / motion blur with Phoenix and adaptive sample have been fixed in 4.37.
Could you check if your problem still happens with 4.37 ?
Thanks