Incorrect frame range exported to Standalone in Octane X

Forums: Incorrect frame range exported to Standalone in Octane X
Sub forum for bug reports

Moderator: JimStar

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)

Incorrect frame range exported to Standalone in Octane X

Postby spectacle » Tue Mar 02, 2021 3:42 pm

spectacle Tue Mar 02, 2021 3:42 pm
In Octane X PR7 the Maya plugin is exporting the frame range incorrectly. For example, setting frames 120-150 in render globals will result in a .orbx with a frame range of 0-150, and the scene data shifted to start at 0 and end at 30.

Maya 2020.3
Octane X PR7
MacOS 11.2.2
5700XT
128GB RAM
spectacle
Licensed Customer
Licensed Customer
 
Posts: 40
Joined: Fri Nov 18, 2016 9:21 pm

Return to Bug Reports


Who is online

Users browsing this forum: No registered users and 1 guest

Sun May 12, 2024 4:59 am [ UTC ]