Page 3 of 4
Re: OctaneRender® for Maya® v1.11a beta [CURRENT]
Posted: Sun Mar 24, 2013 8:02 am
by renmaxhb
TBFX,
thanks for these answers for me.
My scences rendering cost 6 min per frame on 3X gtx580 3GB, octane can blur the rays to reduce noise like mentalray ,renderman?
Re: OctaneRender® for Maya® v1.11a beta [CURRENT]
Posted: Sun Mar 24, 2013 8:44 am
by TBFX
renmaxhb wrote: octane can blur the rays to reduce noise like mentalray ,renderman?
No, those renderers are using biased methods. Any "bluring of the rays" would introduce bias. The beauty of an unbiased engine like Octane is you never have to fight render settings to eliminate blotchiness or GI flicker but you do have to let the render "cook" long enough to get the noise down to an acceptable level. There are a couple of features that can help in some scenes. setting caustic blur in the render globals will help caustics to converge faster at the cost of some fine details and on HDRI environment maps that have a strong point light source like the sun you can turn on importance sampling which will greatly increase the speed of convergence.(not availible in the Maya plugin just yet but should be soon)
How quickly a render will converge to an acceptable result varies greatly depending on many factors. Search these forums, there have been many great posts from the community with advice on lighting and scene setups to get the most efficient render times.
T.
Re: OctaneRender® for Maya® v1.11a beta [CURRENT]
Posted: Sun Mar 24, 2013 9:36 am
by renmaxhb
Thaks a lot,I will go on learning this render.
Re: OctaneRender® for Maya® v1.11a beta [CURRENT]
Posted: Mon Mar 25, 2013 3:03 am
by renmaxhb
JimStar,
I found octane load all nodes when IPR refresh,this cost many time,can load new nodes only when IPR refresh?
Re: OctaneRender® for Maya® v1.11a beta [CURRENT]
Posted: Fri Mar 29, 2013 8:01 am
by Reggie
This Unique name bug is still preventing me from rendering a single useful image out of Octane for Maya. Wasn't this bug supposed to be fixed in v1.11a? The unique names script doesn't do anything to solve this problem. I even have my own script that changes all the names of the objects, but I'm still getting this error with virtually every scene I try to use Octane for Maya with.
Can you guys actually fix this bug the correct way, without having some hacky ass script change the name of everything? That is not the way to fix a bug. This has been a problem for 6 months already, it's really annoying at this point.
Attached is an incredibly basic scene with this error, even though the shape names don't look like they're clashing.
Re: OctaneRender® for Maya® v1.11a beta [CURRENT]
Posted: Fri Mar 29, 2013 10:50 am
by JimStar
Reggie
Thank you for the report and for the scene. I will try to explain some details about it.
I already wrote many times in different threads, that it is not the bug. It is even not the plugin problem. It is Maya's problem. As Maya does not have any mechanisms to unique identify any object, Maya even does not support the uniqueness of objects names. But the plugin which implements the real time rendering NEEDS unique IDs of objects to instantly find these objects in loaded scene database for speed purposes - as in this case the plugin does not need to reload all objects when just one was changed.
So, to fix this problem in the right way - Maya should add the mechanism to have some unique IDs in its objects (or just start to track the objects names uniqueness), the same as it is made in other 3D-modelling soft (e.g. I didn't encounter this problem when was coding the plugin for Blender). I'm not the warlock, I can't code the search in the objects database when these objects do not have some unique identifiers to be object's primary-key in this database. It is the reason why this problem still exists...
But the good news - I have some thoughts how to narrow this problem, I'm working on it right now, and it will be released in the next version... I will write in this new version's description in detail what was changed in this regard. There were some changes happen in my life last few months (Maya users will hear about it soon), it was the reason why new releases were out not so often last time... Now I'm working again with the full force...
So, thank you for the scene - it will help to make some workarounds...
Re: OctaneRender® for Maya® v1.11a beta [CURRENT]
Posted: Fri Mar 29, 2013 1:23 pm
by arh-osa
Thank you very much, Jimstar! can't wait to see all new features:)
I found some troubles in camera. Ortho camera doesn't match viewport ortho at all. I can't figure out how to change it.
Changing Camera Aperture and Focal Lenght has no effect.
Re: OctaneRender® for Maya® v1.11a beta [CURRENT]
Posted: Fri Mar 29, 2013 7:53 pm
by p3taoctane
Is there a way to do Camera Only Rendering from Maya Octane Render?
I can't find the check box to tick

Re: OctaneRender® for Maya® v1.11a beta [CURRENT]
Posted: Fri Mar 29, 2013 8:21 pm
by p3taoctane
Oops.. found it.. I'm a dick !!
Re: OctaneRender® for Maya® v1.11a beta [CURRENT]
Posted: Sat Mar 30, 2013 2:42 am
by TBFX
Reggie wrote:Attached is an incredibly basic scene with this error, even though the shape names don't look like they're clashing.
Hi Reggie,
I did an optimize scene size on your scene and now it renders fine. It was strange that it looked like there were no clashing node names but sometimes Maya's been known to leave stuff in the scene it shouldn't and an optimize scene will usually get rid of it.
T.