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
particles and mb
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
-
paride4331
- Posts: 3809
- Joined: Fri Sep 18, 2015 7:19 am
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
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
- Attachments
-
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
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
- Attachments
-
- particles bug.zip
- (783.18 KiB) Downloaded 236 times
Hi 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
were you able to reproduce these two problems with particles?
-
paride4331
- Posts: 3809
- Joined: Fri Sep 18, 2015 7:19 am
Hi coilbook,
yes, I was.
I made my report, let's see what developers say about this.
Regards
Paride
yes, I was.
I made my report, let's see what developers say about this.
Regards
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
-
neonZorglub
- Posts: 1006
- Joined: Sun Jul 31, 2016 10:08 pm
Hi coilbook,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.
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,neonZorglub wrote:Hi coilbook,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.
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
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.
- Attachments
-
-
- particles bug.zip
- (702.17 KiB) Downloaded 238 times
Hi neonZorglub,neonZorglub wrote:Hi coilbook,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.
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
were you able to reproduce the incorrect mb problem?
-
paride4331
- Posts: 3809
- Joined: Fri Sep 18, 2015 7:19 am
coilbook wrote:Hi neonZorglub,neonZorglub wrote:Hi coilbook,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.
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
were you able to reproduce the incorrect mb problem?
Hi coilbook,
developers is checking that.
Regards
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid