I'm rendering some fast spinning tires on a Formula 1 car and I needed to crank the Motion Blur Samples per frame from 1 up to 12. This achieved good results but I was surprised to find that my 300 frame render stopped rendering motion blur after 256 frames (the render finished… the motion blur just stopped at F 256). I checked for keyframe anomalies and even cached all expressions to keyframes but I got the same results.
Ultimately I decided to reduce the scene to a simple cube spinning for 300 frames with the same render settings to see if I could get the same results... and I DID! My spinning cube's motion blur changed at frame 256. I decided to double the samples to 24 and the motion blur changed at frame 128. It looks like it went from doing a bi-directional blur to a uni-directional blur… so there’s something unfavorable but predictable happening here.
Screenshot
Movie
File
Thoughts?
Motion Blur stops rendering properly with high Samples
Moderators: ChrisHekman, aoktar
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)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
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)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
-
the_monkey
- Posts: 12
- Joined: Sat Apr 18, 2015 8:09 pm
Derp... forgot to mention.
Mac Pro 2 x 3.46 6-Core Intel Xeon / OSX El Capitan / 128GB RAM / GTX980 / Octane 3.0.3.3 for C4D with R17 (but also tested on Octane 3.0.5.3) / NVIDIA Web Driver 346.03.15f05
Mac Pro 2 x 3.46 6-Core Intel Xeon / OSX El Capitan / 128GB RAM / GTX980 / Octane 3.0.3.3 for C4D with R17 (but also tested on Octane 3.0.5.3) / NVIDIA Web Driver 346.03.15f05
I'm testing and found that's really a bug. There is an math error while finding motion data for related frames. I've fixed that.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
