OctaneRender for Maya 2018.1rc1-14.7 [OBSOLETE]

Sub forum for plugin releases

Moderator: JimStar

User avatar
JimStar
OctaneRender Team
Posts: 3816
Joined: Thu Jul 28, 2011 8:19 pm
Location: Auckland, New Zealand

Forum rules:
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.

!!! THIS IS THE BETA VERSION OF OctaneRender PLUGIN, IT IS RELEASED FOR INITIAL BUG HUNTING ONLY !!!
!!! PLEASE DON'T USE IT FOR PRODUCTION & DON'T SAVE THE SCENES FROM THIS BETA VERSION FOR FUTURE USE AS THERE ARE HIGH CHANCES TO LOSING THEM !!!
!!! SCENES SAVED IN THIS BETA VERSION ARE NOT GUARANTEED TO WORK IN SUBSEQUENT VERSIONS !!!
!!! THE RENDER ENGINE IS YET TO BE STABLE, SOME CRASHES & BUGS ARE EXPECTED FOR THIS TEST VERSION OF THE PLUGIN !!!


Otoy® is proud to announce the availability of a new test version of OctaneRender™ for Maya® Version 2018.1
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 2016, 2016.5, 2017 and 2018 64-bit on Windows, Linux and OSX operating systems.


To use this version, you need a GPU of compute model 3.0 or higher. Support for Fermi GPUs (like GTX 4xx and 5xx) has been dropped. Also make sure you use a driver of version 387 or higher and if you are working on Mac OS that have a CUDA driver installed that supports at least CUDA 9.1.


Changelog and the installers for Octane Standalone 2018.1 are here:
OctaneRender Standalone 2018.1 RC1


Changes since version 14.6:
  • Implemented the particular component selection to load into Octane float-vertex-attributes from Maya colorsets. Just add the ".r", ".g", ".b" or ".a" postfix to a colorset name (e.g. "colorSet1.a") in the Octane-specific mesh settings. If no postfix - then alpha component will be loaded by default.
  • Fixed Octane settings issues when injecting references directly into root namespace.

Windows DOWNLOAD
OctaneRender for Maya 2018.1rc1-14.7 BETA

Linux DOWNLOAD
OctaneRender for Maya 2018.1rc1-14.7 BETA


MacOS DOWNLOAD
OctaneRender for Maya 2018.1rc1-14.7 BETA


=================================
Subscription Studio Downloads
=================================

OctaneRender for Maya Studio 2018.1rc1-14.7 BETA [Windows]

OctaneRender for Maya Studio 2018.1rc1-14.7 BETA [Linux]

OctaneRender for Maya Studio 2018.1rc1-14.7 BETA [MacOS]
Last edited by JimStar on Wed Jan 09, 2019 10:42 pm, edited 1 time in total.
calus
Licensed Customer
Posts: 1308
Joined: Sat May 22, 2010 9:31 am
Location: Paris

JimStar wrote:
  • Implemented the particular component selection to load into Octane float-vertex-attributes from Maya colorsets. Just add the ".r", ".g", ".b" or ".a" postfix to a colorset name (e.g. "colorSet1.a") in the Octane-specific mesh settings. If no postfix - then alpha component will be loaded by default.
WO, perfect super fast answer :) thanks.
Pascal ANDRE
Dennyuel
Licensed Customer
Posts: 7
Joined: Tue Nov 27, 2012 8:34 pm

SUPER! SUPER!
Its working! The reference problem solved!
Thank You JimStar!!

But we have a new issue. I shared a picture.
After installing the new version, all camera view will be gray. An error message is displayed when the camera is highlighted.

https://drive.google.com/file/d/1218kj9 ... sp=sharing

Thank You!
User avatar
JimStar
OctaneRender Team
Posts: 3816
Joined: Thu Jul 28, 2011 8:19 pm
Location: Auckland, New Zealand

Dennyuel
This error is not an Octane error: this error happens in Maya's internal scripts. Particularly in the Autodesk's AEcameraTemplateCommon.mel file: the division by zero error happens in its AEcameraFilmAspectReplace UI function because the verticalFilmAperture attribute of your camera is "0" - this function does not check it before doing division.
Just set this attribute to a proper value...

If this happens in some old scene made in pre-refactored plugin versions, and you are absolutely sure that you did not set this attribute to zero - then please PM me the initial scene, I can check if the auto-conversion perhaps somehow zeroed this attribute...
User avatar
Jolbertoquini
Licensed Customer
Posts: 1067
Joined: Sun Aug 31, 2014 7:08 am
Location: London
Contact:

Hi Jim,

Happy new year! Hope everything is fine. I have a problem to make work Ornatrix simple scene with sphere is not load as hairs but as Mesh also is not supporting the render hair option to see on viewport less and on the render more (the all reason of the plug) Please any help maybe I set wrong here a screen shot . I can't save the scene cause of demonstration version, but I'm sure you could build one simple sphere scene.

Cheers,
JO
Attachments
Screen shot
Screen shot
Octane Render for Maya.
https://vimeo.com/jocg/videos
https://www.linkedin.com/in/jocgtd
http://www.hmxmedia.com/
--------------------
Join MAYA OCTANE USERS Skype discussion here :
https://join.skype.com/LXEQaqqfN15w
User avatar
Jolbertoquini
Licensed Customer
Posts: 1067
Joined: Sun Aug 31, 2014 7:08 am
Location: London
Contact:

Hi Jim,

After further test is working but, is a information issue, show "0" hair but after change the "viewport count fraction" while I'm doing the IPR is showing right amount.
The only issue is Render count is ignored and Octane use only the viewport preview count. I think we need make sure is using the Render count not the viewport count fraction preview.

Cheers,
JO
Attachments
Screenshot_2.png
Octane Render for Maya.
https://vimeo.com/jocg/videos
https://www.linkedin.com/in/jocgtd
http://www.hmxmedia.com/
--------------------
Join MAYA OCTANE USERS Skype discussion here :
https://join.skype.com/LXEQaqqfN15w
renmaxhb
Licensed Customer
Posts: 226
Joined: Mon Dec 13, 2010 8:53 am

Maya 2016 crashed in OCrendering when add a Ornatrix fur ball to poly allways.
Attachments
2016.png
User avatar
Jolbertoquini
Licensed Customer
Posts: 1067
Joined: Sun Aug 31, 2014 7:08 am
Location: London
Contact:

Hi Jim,

I'm using vectron on the Maya Plug I manage to make work really well, (apart the scale options is a bit weird with the dummy box which doesn't have the mesh size like a bounding box, old request for all proxy, vdb's and etc.)

I have a problem to replicate the example scenes from Standalone one projection node is missing the XYZ to UVW node.

(I know I could just copy the nodes via orbx proxy and I have on the scene but if want build from scratch I don't know how to)
I included the scene "octaneOslGeometry1" I try to build from scratch and "the proxy" is from standalone. Please help me if I did something wrong.

Here a screen shot:

Cheers,
JO
Attachments
vectron_test_Box.rar
Scene
(13.04 KiB) Downloaded 206 times
Screenshot_1.jpg
Octane Render for Maya.
https://vimeo.com/jocg/videos
https://www.linkedin.com/in/jocgtd
http://www.hmxmedia.com/
--------------------
Join MAYA OCTANE USERS Skype discussion here :
https://join.skype.com/LXEQaqqfN15w
Dennyuel
Licensed Customer
Posts: 7
Joined: Tue Nov 27, 2012 8:34 pm

Hi Jim!

Thank you for your previous fix. It solved the Node errors.

Now we see another kinda serious issue with multi GPU batch render.
The render speed is different compared to IPR. It is much slower, much like as it is only using one of the GPU s and not all.

Also many times the batch render doesn`t start if we turn off the denoiser. (if we turn it back on it runs again.)

And another question.
Are there any settings how we could turn off the save of the Beauty pass? As we only need the denoised. At the moment it saves both the denoised and the beauty pass. Which is slowing down the saving of a frame. Also creates many junk files on our server which we have to delete by hand.

Thanks,
Dennyuel
User avatar
Jolbertoquini
Licensed Customer
Posts: 1067
Joined: Sun Aug 31, 2014 7:08 am
Location: London
Contact:

Hi Jim,

SDF Vdb mesh, is not supported on real size world based on the most common workflow on the industry using Maya units at centimeters, cause Octane is on "meters" we need set scene scale at "0.01" to work right? I guess I need ask Standalone not sure if I can have a object at "50cm" size doesn't work. Is the same issue we had before with displacement (fixed now). When I checked the RC1 version only big object like "50 meters :o " size is rendering correct with SDF, and this on my point of view break all the concept sold by Otoy's physically based render if real size world is not properly supported. (I guess is just this feature due the Beta stage)

Anyway Maya plug as this issues for while. I post some screen shots from Maya Plug, but I think may be a Standalone issue because if I create a SDF at 50 unit 1unit=1 metter is fine but if I create at 0.5 unit = 50 cm doesn't work as well on the standalone.

Please can we have any clarification on this?

Thanks :),
JO
Attachments
Scene scale at 1
Scene scale at 1
Scene scale at 0.01
Scene scale at 0.01
Octane Render for Maya.
https://vimeo.com/jocg/videos
https://www.linkedin.com/in/jocgtd
http://www.hmxmedia.com/
--------------------
Join MAYA OCTANE USERS Skype discussion here :
https://join.skype.com/LXEQaqqfN15w
Locked

Return to “Releases”