I have encountered this bug multiple times now.
"Render frame range" is buggy.
Octane will not read in the geometry data if the data only start appear in the middle of the sequence.
For example, I have a geo object named "A" which only has polygon from Frame10 onward.
If I "save render as frame range " from Frame1 to Frame20, because "A" has nothing on the starting frame, Octane will be bugged and render the whole sequence without A.
But if I "save render as frame range " from Frame10 to Frame20, because "A" has geometry data on the starting frame, A will be rendered correctly and apear throughout the whole sequence.
Geometry missing from render
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)
Yep, this is a known limitation. If an OBJ node doesn't have any valid geometry in the first frame, it is not even extracted, so later it can't be updated.
The workaround for this kind of scene is to render them in full scene reload mode. If you configure the Octane ROP node to render in full scene reload mode, the whole sequence should be rendered fine.
Thanks,
-Juanjo
The workaround for this kind of scene is to render them in full scene reload mode. If you configure the Octane ROP node to render in full scene reload mode, the whole sequence should be rendered fine.
Thanks,
-Juanjo
-
mirocreative
- Posts: 46
- Joined: Fri Jan 17, 2014 2:26 pm
- Location: New York
- Contact:
I had this issue when working with particles not being present on the first frame. I placed a few particles behind the camera (at a blind spot) and managed to render/export without the frame range madness. Might work for you as well.
how is this a thing with the octane plugin but works fine with the redshift houdini plugin? you worked on both right so im curious why they differ when it comes to this feature/issue?juanjgon wrote:Yep, this is a known limitation. If an OBJ node doesn't have any valid geometry in the first frame, it is not even extracted, so later it can't be updated.
The workaround for this kind of scene is to render them in full scene reload mode. If you configure the Octane ROP node to render in full scene reload mode, the whole sequence should be rendered fine.
Thanks,
-Juanjo