hey,
points with frame to frame variant ptnum, but existing velocity attribute, crash, wont or render long streaks. (reaching from point position to worldspace orgin)
I am trying to render instances with popdop points as sources.
It seems that octane tries to render "exact motion blur" by interpolating between this and last frame. which in that case wont work cause of the variant ptnum.
I have consistent id attributes, but am afraid that octane just taking ptnum in consideration.
thanks
sebastian
variant ptnum motionblur problems
Moderator: juanjgon
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)
here we go https://drive.google.com/file/d/0B5cLxJ ... sp=sharing
that cache is straight out of pop dops. you can clearly see that ptnum is changing every frame, due the way the pops were set up.
thanks for looking into it.
sebastian
that cache is straight out of pop dops. you can clearly see that ptnum is changing every frame, due the way the pops were set up.
thanks for looking into it.
sebastian
Yes, you are right. Currently the instancing motion evaluation functions don't support particle systems with variant ptnum OBJ sequences. I am going to add a new function to support instancing motion blur computing the motion from the base frame particle matrix transformation and the "v" parameter information, in only one pass.
I hope to have this function ready for the next beta build.
Thanks for reporting this problem.
-Juanjo
I hope to have this function ready for the next beta build.
Thanks for reporting this problem.
-Juanjo
Done, available in the next build 
New parameter "Instancing MB computed from velocity attribute" in the Octane OBJ custom spare parameters. Can be enabled in the OBJ instance nodes to compute the instances motion blur using the "v" velocity attribute. Useful when instancing over particle system or other OBJ nodes with variable ptnum IDs, or when only the instances translation motion blur is useful in the scene.
-Juanjo
New parameter "Instancing MB computed from velocity attribute" in the Octane OBJ custom spare parameters. Can be enabled in the OBJ instance nodes to compute the instances motion blur using the "v" velocity attribute. Useful when instancing over particle system or other OBJ nodes with variable ptnum IDs, or when only the instances translation motion blur is useful in the scene.
-Juanjo
- Attachments
-