OctaneRender for Maya 2021.1.1-20.10 [OBSOLETE] Tweet

[BK]

Batch render not working - Info Channel Ambient occlusion
Writes:
// Rendering with Octane... //
// Percentage of rendering done: 0 (starting) //

And nothing happens.

It's not clear how to render Ambient occlusion.
Missing Passes settings.

Hi Fil3d,

Thank you for the post.

If the batch render gives the same error in another scene then it may be related to Maya Batch render(sometimes gets fixed after reinstalling Maya). Please also see this post viewtopic.php?f=28&t=78504&p=406912&hilit=batch+render+maya#p406912

If it still does not render then please PM the scene for us to look at?

cheers
Cheers

[psultan]

This version is not working on our Linux Machines.
After the CUDA driver downloads and we enter our license information the plugin does not finish loading or crashes.

With bifrost off...error in script editor...

// Error: file: /usr/autodesk/maya2022/scripts/others/pluginWin.mel line 316: Unable to dynamically load : /usr/otoy/ofm_vre/2022/plug-ins/OctanePlugin.so
/usr/otoy/ofm_vre/2022/plug-ins/OctanePlugin.so: undefined symbol: _ZN7Bifrost3API11StateServerC1Ev //
// Error: file: /usr/autodesk/maya2022/scripts/others/pluginWin.mel line 316: /usr/otoy/ofm_vre/2022/plug-ins/OctanePlugin.so: undefined symbol: _ZN7Bifrost3API11StateServerC1Ev (OctanePlugin) //



With bifrost on there is a fatal crash after a few seconds...

output from script editor:

// //
// OctaneRendertm v. 2021.1 - 20.8, network rendering supported //
// Octane: plugin is activated. //
evalDeferred 'shaderBa11RendererMenuUpdate';
updateRenderOverride;
file -type mayaAscii;
// Result: untitled.ma //


output from shell:

Stack trace:
Octane::ApiOcioConfig::destroy()
/Bluearc/GFX/HOME/CHRLX/psultan/dev/3D/maya/maya2022/modules/linux/octane_20.8_2021.1/octane/lib/liboctane.so(+0x3dc6d8e) [0x7f6ec8cf9d8e]
initializePlugin(Autodesk::Maya::OpenMaya20220000::MObject)
Tplugin::primaryLoad(Tstring const&, Tstring*)
/usr/autodesk/maya2022/lib2/libOpenMaya.so(+0x34abed) [0x7f709360abed]
/usr/autodesk/maya2022/lib2/libOpenMaya.so(+0x349ce2) [0x7f7093609ce2]
/usr/autodesk/maya2022/lib2/libOpenMaya.so(+0x3495c2) [0x7f70936095c2]
/usr/autodesk/maya2022/lib2/libCommandEngine.so(+0x98124) [0x7f708baf1124]
/usr/autodesk/maya2022/lib2/libCommandEngine.so(+0xc22ab) [0x7f708bb1b2ab]
/usr/autodesk/maya2022/lib2/libCommandEngine.so(+0xe387f) [0x7f708bb3c87f]
/usr/autodesk/maya2022/lib2/libCommandEngine.so(+0xc22ab) [0x7f708bb1b2ab]
/usr/autodesk/maya2022/lib2/libCommandEngine.so(+0xe2ebb) [0x7f708bb3bebb]
/usr/autodesk/maya2022/lib2/libCommandEngine.so(+0xc22ab) [0x7f708bb1b2ab]
/usr/autodesk/maya2022/lib2/libCommandEngine.so(+0xe4cad) [0x7f708bb3dcad]
/usr/autodesk/maya2022/lib2/libCommandEngine.so(+0xc22ab) [0x7f708bb1b2ab]
/usr/autodesk/maya2022/lib2/libCommandEngine.so(+0xc23e1) [0x7f708bb1b3e1]
SophiaExecutable::evaluate(void*)
TcommandEngine::executeCommand(Tstring const&, bool, bool, TmelCmdResult*, unsigned int)
TscriptActionMixin::execute(Tevent const&, std::unique_ptr<TinterpreterResult, std::default_delete<TinterpreterResult> >*)
TcontrolScriptAction::doIt(Tevent const&)
Taction::performAction(Tevent const&, char const*)
Taction::doIt()
/usr/autodesk/maya2022/lib/libQt5Core.so.5(+0x2dd3b5) [0x7f7088eb13b5]
QmayaCheckBox::onOffChanged()
/usr/autodesk/maya2022/lib2/libExtensionLayer.so(+0x30fa73) [0x7f708c011a73]
/usr/autodesk/maya2022/lib/libQt5Core.so.5(+0x2dd3b5) [0x7f7088eb13b5]
QCheckBox::stateChanged(int)
/usr/autodesk/maya2022/lib/libQt5Widgets.so.5(+0x25aabc) [0x7f708ad24abc]
QAbstractButton::mouseReleaseEvent(QMouseEvent*)
QWidget::event(QEvent*)
QApplicationPrivate::notify_helper(QObject*, QEvent*)
QApplication::notify(QObject*, QEvent*)
/usr/autodesk/maya2022/lib2/libExtensionLayer.so(+0x32f9d6) [0x7f708c0319d6]
QCoreApplication::notifyInternal2(QObject*, QEvent*)
QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool)
/usr/autodesk/maya2022/lib/libQt5Widgets.so.5(+0x1c347c) [0x7f708ac8d47c]
/usr/autodesk/maya2022/lib/libQt5Widgets.so.5(+0x1c658c) [0x7f708ac9058c]
QApplicationPrivate::notify_helper(QObject*, QEvent*)
QApplication::notify(QObject*, QEvent*)
/usr/autodesk/maya2022/lib2/libExtensionLayer.so(+0x32f9d6) [0x7f708c0319d6]

[JimStar]

psultan
This is the engine bug in Octane SDK. The engine team is aware of it, and they told us it is going to be fixed in 2021.1.2 SDK.

A quick workaround you could try - would be to set the OCIO environment variable in Linux to a path to existing OCIO config file, before running Maya. But there is no guarantee that this workaround would work... in which case you'd still need to wait for a fixed 2021.1.2 engine release...

[johan_D]

Hi,
I'm not able to Install this version on Maya 2019
And on Maya 2020 I tryed a simple SunSky with a daylight environment, the sun make a strange red color
I tryed sun direction or daylight system with many diferent setings or hours, it's the same
anybody els saw that?

[p3taotoy]

Strange One here...

If I create a brand new scene and use a 1x1 poly plane as a texture (rgb) emitter... works great

I have a default Maya scene I use for OR and my emmitter planes are not working... even if i copy and paste the one that did into the scene.

In the Hypershade ... the preview shows the light strength etc.

Render ID is set ok... I must have set something but they do not emmit light.

Daylight and HDR envorons all responding OK.

I am sure its something I set... but for the life of me I can not find it...

Any guesses? :>))

Thanks

[BK]

Hi,
I'm not able to Install this version on Maya 2019
And on Maya 2020 I tryed a simple SunSky with a daylight environment, the sun make a strange red color
I tryed sun direction or daylight system with many diferent setings or hours, it's the same
anybody els saw that?

Hi Johan,

Thank you for the post!
Would you please share a screenshot of the error message with Maya 2019?
And, is it possible to share a video and the scene?
Please make sure you have selected the correct Environment node if your scene has more than one Environment node.

Also, check if you have attached any Environment node under Camera>Octane>Render Settings Overrides.

Cheers

[johan_D]

A simple render with octane2020.2.5, and the same with 2021.1.1.1

you can see the error message when I load it in Maya 2019, it's mean "the specified module could not be found"
if it's on auto load before I instaled the version maya 2019.1 crash on start

[BK]

A simple render with octane2020.2.5, and the same with 2021.1.1.1

trouble_octane_2021.jpg

you can see the error message when I load it in Maya 2019, it's mean "the specified module could not be found"
if it's on auto load before I instaled the version maya 2019.1 crash on start

Hi Johan,

Thank you for the screenshot.
Please let us know if you are using OCIO or share the scene for us to investigate?

cheers

[BK]

A simple render with octane2020.2.5, and the same with 2021.1.1.1

trouble_octane_2021.jpg

you can see the error message when I load it in Maya 2019, it's mean "the specified module could not be found"
if it's on auto load before I instaled the version maya 2019.1 crash on start

Hi Johan,

We introduced an option White light spectrum from v2021.1.1 Kernel and the render result is expected.
Please change it to legacy/flat to match 2020.2.5.
Here are more tips from our core dev
viewtopic.php?p=404493#p404493

cheers

[johan_D]

Hi BK,

Thank you for your answer, I had missed this change,
that works.