OTOY Forums

Otoy® is proud to announce the availability of a new version of OctaneRender™ for Maya®
The world's fastest and most feature-rich unbiased render engine that integrates completely into Autodesk® Maya®.

Maya® Version Requirements

This release will work with Maya® Versions 2015, 2016, 2016.5 and 2017 64-bit on MS Windows operating systems.

COMPATIBILITY AND OCTANERENDER STANDALONE REQUIREMENT

To run OctaneRender™ for Maya®, you need to also have an activated OctaneRender™ Standalone copy activated on the machine you wish to install the plugin onto.
You cannot purchase and use only the Maya plugin and use it without also owning an activated copy of OctaneRender™ Standalone on your machine.

CHANGES SINCE THE PREVIOUS VERSION

• Implemented support of Maya's fluid "Auto resize" feature. For those who uses it - the volume's wrong offset in some cases must be gone now.
• Minor fixes and improvements...

DOWNLOAD

OctaneRender for Maya 3.04.5 - 9.4

OctaneRender for Maya DEMO 3.04.5 - 9.4

For network slave and daemon please download standalone installer here:
viewtopic.php?f=24&t=57660


Yours,
The OctaneRender™ Team.

Thanks for a update, But would be very helpful if the "Convert Maya Materials to Octane" Feature could get fix not working in Maya 3.04.5 9.4. looks to me that the dashes are not being imputed. thanks


Octane Convert ?

Default maya

@JimStar,

I don't think you implemented yet the Octane sphere primitive in the plugin,
if you inted to do so, one case where it's really needed is for Bifrost foam.

So quick

Vrr wrote:would be very helpful if the "Convert Maya Materials to Octane" Feature could get fix

@Vrr, Are you sure it was working before when doing the exact same thing ?
Are you sure your scene is saved and the Project is defined correctly when you try this function ?

I remember I had this exact same problem very long time ago.

Inever really used this feature,
but I just tested it now and for me the texture pathes are correct in Maya 2016, it just works.
Works also if the file texture is outside of the project path.

Did you try replacing the "-" character in the file name ?
Or maybe this is OS relative, we are in the windows version thread, but maybe you use another OS ?

Anyway you should share a sample scene/project where you have this issue, because it's not possible for JimStar to fix something he can't reproduce.

calus wrote:

Vrr wrote:would be very helpful if the "Convert Maya Materials to Octane" Feature could get fix

@Vrr, Are you sure it was working before when doing the exact same thing ?
Are you sure your scene is saved and the Project is defined correctly when you try this function ?

Thanks for reply, And Yes save the scene and i never change the file location? i haven't use Octane in years but i never had this problem with older version of Maya and Octane, or with a model before it always worked Had many others problem though. maybe its just in Maya 2017, but Arnold Redshift and Renderman see the texture location and put the " \ dashes" in correctly in Maya 2017. i will send a Maya file soon

Here's a FBX i just put it on a external hard drive but haven't tried desktop, import the file and Hit the "Convert Maya Materials to Octane" in Maya 2017 and all dashes are left out..

this is my first version of v3 I'm testing out but I had to revert back to v2. Opened a couple scenes that were originally created in v2...one of them worked fine but the other, I could only render once before it quit working. If I rendered, then stopped the render, I could not get it started again until I restarted Maya. Any clue?

itsallgoode9 wrote:this is my first version of v3 I'm testing out but I had to revert back to v2. Opened a couple scenes that were originally created in v2...one of them worked fine but the other, I could only render once before it quit working. If I rendered, then stopped the render, I could not get it started again until I restarted Maya. Any clue?

I guess as usual your scene is very resource hungry,
and the symptoms looks like Octane IPR crashing silently on quitting because of something going out of resource.

Assuming you can't share the scene neither reduce it to a sample with the same problem,
I would export the scene to Standalone V3 to confirm it's a Maya plugin problem first.
Though most of the time the exporter also crash in this case,
this is a good proof of something going wrong in the plugin.

ah, thanks. I'll check my gpu resources and see if that was the problem. thanks