OTOY Forums

Why is motion blur still not working right with particles (super spray, pflow). After so many frames it does this. It's been since Octane 2. We really try hard and report problems for you, guys, but some get ignored and the problems pile up.
Do you even test animations?




Like this problem I mentioned like 10 times :

"That's from a RC4 thread, regarding the "expected exposure" bug where it has to be 1 or 2, instead of .3 - And the rendering is locked at one sample only.

It is still a problem in 6.11. Wouldn't there be a way to completely bypass having to set this anyway?"
viewtopic.php?f=80&t=69843&start=30

Hi coilbook,
I'm sorry, expected exposure seems works, I have not issues.
About MB, could you share your issued MB?
There might be some possible work around with the Broadcast
notification options (in the kernel, and also in the trouble shooting).
Developers try to check more.
Regards
Paride

paride4331 wrote:Hi coilbook,
I'm sorry, expected exposure seems works, I have not issues.
About MB, could you share your issued MB?
There might be some possible work around with the Broadcast
notification options (in the kernel, and also in the trouble shooting).
Developers try to check more.
Regards
Paride

Thanks I will send you the scene
Also after rendering sometimes I have to uncheck all slaves or I get this error still "the total count of GPUs used locally and over the network exceeds 20. ignoring slave xxxxxxxx-847 (7) with 5 device(s)."

paride4331 wrote:Hi coilbook,
I'm sorry, expected exposure seems works, I have not issues.
About MB, could you share your issued MB?
There might be some possible work around with the Broadcast
notification options (in the kernel, and also in the trouble shooting).
Developers try to check more.
Regards
Paride

Hi Paride,
here is the scene.

There are two bugs:

1. If you start rendering at frame 429 you will see no particles being rendered.

2. Please start rendering at frame 430 and you will see incorrect mb at frame 440.

Thank you

paride4331 wrote:Hi coilbook,
I'm sorry, expected exposure seems works, I have not issues.
About MB, could you share your issued MB?
There might be some possible work around with the Broadcast
notification options (in the kernel, and also in the trouble shooting).
Developers try to check more.
Regards
Paride

Hi Paride,
were you able to reproduce these two problems with particles?

Hi coilbook,
yes, I was.
I made my report, let's see what developers say about this.
Regards
Paride

coilbook wrote:There are two bugs:
1. If you start rendering at frame 429 you will see no particles being rendered.
2. Please start rendering at frame 430 and you will see incorrect mb at frame 440.

Hi coilbook,
Thanks for your scene.
-The first issue will be fixed in next release, 7.01
-For the motion blur, do you mean a blur that should not there there ? I see some blur on the lever at frame 440, but it's not due to motion blur (as it stopped moving at frame 439), I think it's just camera's focus / aperture.. (setting Aperture to 0 makes it clear..)
Thank you

neonZorglub wrote:

coilbook wrote:There are two bugs:
1. If you start rendering at frame 429 you will see no particles being rendered.
2. Please start rendering at frame 430 and you will see incorrect mb at frame 440.

Hi coilbook,
Thanks for your scene.
-The first issue will be fixed in next release, 7.01
-For the motion blur, do you mean a blur that should not there there ? I see some blur on the lever at frame 440, but it's not due to motion blur (as it stopped moving at frame 439), I think it's just camera's focus / aperture.. (setting Aperture to 0 makes it clear..)
Thank you

Hi neonZorglub,
I've reattached the scene. please go to frame 439 and you will see incorrect motion blur of sparks where in 438 it is ok. It has nothing to do with camera or the lever. Thank you.

neonZorglub wrote:

coilbook wrote:There are two bugs:
1. If you start rendering at frame 429 you will see no particles being rendered.
2. Please start rendering at frame 430 and you will see incorrect mb at frame 440.

Hi coilbook,
Thanks for your scene.
-The first issue will be fixed in next release, 7.01
-For the motion blur, do you mean a blur that should not there there ? I see some blur on the lever at frame 440, but it's not due to motion blur (as it stopped moving at frame 439), I think it's just camera's focus / aperture.. (setting Aperture to 0 makes it clear..)
Thank you

Hi neonZorglub,
were you able to reproduce the incorrect mb problem?

coilbook wrote:

neonZorglub wrote:

coilbook wrote:There are two bugs:
1. If you start rendering at frame 429 you will see no particles being rendered.
2. Please start rendering at frame 430 and you will see incorrect mb at frame 440.

Hi coilbook,
Thanks for your scene.
-The first issue will be fixed in next release, 7.01
-For the motion blur, do you mean a blur that should not there there ? I see some blur on the lever at frame 440, but it's not due to motion blur (as it stopped moving at frame 439), I think it's just camera's focus / aperture.. (setting Aperture to 0 makes it clear..)
Thank you

Hi neonZorglub,
were you able to reproduce the incorrect mb problem?

Hi coilbook,
developers is checking that.
Regards
Paride