OctaneRender® for Maya® 3.08rc1 - 12.9-beta [ OBSOLETE ]

[BK]

Is it okay to post on our Feature Request page? [ https://render.otoy.com/requests/ ].

There's a misunderstanding here, I think the new image plane implementation is fine (only needs a way to enable/disable render), so not asking for other features because :

- In case someone wants to have the same behavior as in previous plugin, he can just use a real polygon plane parented to the camera !

- If someone needs a background affected by DOF and only visible by camera and/or in reflection and/or in refraction, he must use the "visible environment" feature, which is now well integrated in Maya.

Thank you, Calus, for all your detailed explanation.

Cheers

[intelligentlight]

Hi!

When I open Render Globals the Common-tab menu is blank and this message is displayed:

// Error: file: D:/Program Files/Autodesk/Maya2017/scripts/others/createMayaSoftwareCommonGlobalsTab.mel line 36: setParent: Object 'commonTabColumn' not found. //
# Error: line 1: MelError: file D:\Program Files\Autodesk\Maya2017\Python\lib\site-packages\pymel\core\language.py line 992: Error during execution of MEL script: file: D:/Program Files/Autodesk/Maya2017/scripts/others/createMayaSoftwareCommonGlobalsTab.mel line 36: setParent: Object 'commonTabColumn' not found.
Calling Procedure: updateMayaSoftwareImageFormatControl, in file "D:\Program Files\Autodesk\Maya2017\D"
updateMayaSoftwareImageFormatControl() #

But just switching back and forth between tabs gets it loaded OK.

Maya 2017 Update 5 x64, Windows 10 x64
(I didn't test it in 2018.2 yet, because I use that for production)

[Rikk The Gaijin]

Unusable. I made a simple scene and at some point Maya crashed. Reloaded the last save and now it only renders in wireframe no matter what kernel/pass I try.
Garbage plugin.

[BK]

Unusable. I made a simple scene and at some point Maya crashed. Reloaded the last save and now it only renders in wireframe no matter what kernel/pass I try.
Garbage plugin.

Hi Rikk,

Thank you so much for the crash report.
As mentioned in the release note above, the plugin is a BETA release so some crashes are expected. And we hope to make this stable in few weeks time.

While we try to reproduce the issue, would you be able to share the last save Maya file for debugging?

We have gone through extensive RnDs to introduce and integrate our Octane Standalone node workflow inside Maya. viewtopic.php?p=322553#p322553

Please see the Orbx material and Orbx proxy. If you have any feedback/request to the workflow, please feel free to let us know.

[BK]

Hi!

When I open Render Globals the Common-tab menu is blank and this message is displayed:

// Error: file: D:/Program Files/Autodesk/Maya2017/scripts/others/createMayaSoftwareCommonGlobalsTab.mel line 36: setParent: Object 'commonTabColumn' not found. //
# Error: line 1: MelError: file D:\Program Files\Autodesk\Maya2017\Python\lib\site-packages\pymel\core\language.py line 992: Error during execution of MEL script: file: D:/Program Files/Autodesk/Maya2017/scripts/others/createMayaSoftwareCommonGlobalsTab.mel line 36: setParent: Object 'commonTabColumn' not found.
Calling Procedure: updateMayaSoftwareImageFormatControl, in file "D:\Program Files\Autodesk\Maya2017\D"
updateMayaSoftwareImageFormatControl() #

But just switching back and forth between tabs gets it loaded OK.

Maya 2017 Update 5 x64, Windows 10 x64
(I didn't test it in 2018.2 yet, because I use that for production)

Hi Intelligentlight,

Thank you for the bug report
We already have a ticket on this issue and it has been identified as Maya bug after our investigation. We would try to resolve as soon as possible.
If you come across with any hiccups during the test drive, please let us know

[Rikk The Gaijin]

Hi Rikk,

Thank you so much for the crash report.
As mentioned in the release note above, the plugin is a BETA release so some crashes are expected. And we hope to make this stable in few weeks time.

While we try to reproduce the issue, would you be able to share the last save Maya file for debugging?

We have gone through extensive RnDs to introduce and integrate our Octane Standalone node workflow inside Maya. viewtopic.php?p=322553#p322553

Please see the Orbx material and Orbx proxy. If you have any feedback/request to the workflow, please feel free to let us know.

Hi BK.
The crash was unrelated to Octane, Maya crashed while trying to use Transfer Attributes between two meshes. Octane viewport was not active, although Octane nodes were present in the scene.
The last save was before that operation, but the problem is that no matter what I do, now it only renders in wireframe. I cannot get Octane to render normally in that scene anymore.
If I make a completely new scene, it renders fine.
I have attached the scene with the problem. It was saved in Maya 2017.

Also, is there a reason why you changed the gamma response when using Linear/Off in the Imager? In the standalone you need to set the gamma to 2.2 when using Linear, and it was the same in the old plugin, but now you need to set it 1.0 to look correct.
It's confusing. Standalone and Plugin need to have the same parameters.

[calus]

Hey Rikk,

Unusable.

Yes, this beta release is not usable yet, still a work-in-progress.
However it's possible to test the new features as long as you identify current issues/limitations.

Garbage plugin.

Not this time, on the contrary I found that most of the change/new features have well-thought-out implementation and are very promising,
but for the moment most of them have some bugs preventing correct usage.

Reloaded the last save and now it only renders in wireframe no matter what kernel/pass I try.

The major issue I identified with the new render-setting section is:
- when a scene is reloaded or when using batch-render / cmd-render, the scene always looses all its connections to the renderSettings nodes, then render use default wireframe kernel as in standalone when no kernel are connected to renderTarget.
- workaround for IPR (for testing) is to re-link the renderSetting nodes(kernel,imager,env,..) each time the scene is reloaded .
- no workaround for batch/cmd render, can only render wireframe kernel. Also doesn't render anything if render output path uses directory hierarchy.

[Rikk The Gaijin]

The major issue I identified with the new render-setting section is:
- when a scene is reloaded or when using batch-render / cmd-render, the scene always looses all its connections to the renderSettings nodes, then render use default wireframe kernel as in standalone when no kernel are connected to renderTarget.
- workaround for IPR (for testing) is to re-link the renderSetting nodes(kernel,imager,env,..) each time the scene is reloaded .
- no workaround for batch/cmd render, can only render wireframe kernel. Also doesn't render anything if render output path uses directory hierarchy.

So they knew the plugin cannot even handle to reload a scene, and they released it anyway?
I m sorry but IT IS GARBAGE.
I don't get paid to beta test this stuff, I purchased a plugin two years ago and still cannot use for production. Explain that.

[calus]

So they knew the plugin cannot even handle to reload a scene, and they released it anyway?
I m sorry but IT IS GARBAGE.
I don't get paid to beta test this stuff, I purchased a plugin two years ago and still cannot use for production. Explain that.

Indeed Bikram wanted initially to do private beta testing before public release,
but finally it was decided to release most of the 3.08 plugins around the 3.08 RC1 SA release date (and also because refactoring took so much time I guess).
So I think the beta Maya plugin was released as is without any serious testing, I don't think the reload scene bug was a known issue.

[calus]

Also, is there a reason why you changed the gamma response when using Linear/Off in the Imager? In the standalone you need to set the gamma to 2.2 when using Linear, and it was the same in the old plugin, but now you need to set it 1.0 to look correct.
It's confusing. Standalone and Plugin need to have the same parameters.

I might be wrong but I found that the plugin now have the exact same behavior as in Standalone.
What you noticed might be relative to the bug described previously (imager node needs to be relinked)
or is it about saving images files from Maya render View ?
Indeed I think it's not possible to get an HDR linear buffer in render view and Octane viewport. They always use a LDR tonemapped clamped buffer for the moment. I think the implementation is just not finished and doesn't adjust as expected the image buffer bit depth based on the chosen File Output format. So when you save EXR from the render view, you get a wrong LDR result even if EXR format is selected in File Output setting.