Various issues in the ORBX exporter

Forums: Various issues in the ORBX exporter
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)

Various issues in the ORBX exporter

Postby calus » Wed Apr 05, 2017 7:12 am

calus Wed Apr 05, 2017 7:12 am
Tested exporting scene as "animated OctaneRender scene" with alembic option enabled, and compared to exporting with Maya builtin Alembic.

Issue 1:
Exported ORBX loose Maya scene framerate.
framerate is always 24 FPS

Issue 2:
Exported ORBX loose Maya scene frame numbers.
frame numbers always start at 0.

Issue 3:
Maya "none" option for motion-blur is not respected in the ORBX.
This option doesn't exist in standalone, motion-blur is always enabled as soon as cam shutter >0.
Pascal ANDRE
calus
Licensed Customer
Licensed Customer
 
Posts: 1308
Joined: Sat May 22, 2010 9:31 am
Location: Paris

Return to Bug Reports


Who is online

Users browsing this forum: No registered users and 2 guests

Wed Apr 24, 2024 3:17 pm [ UTC ]