
OctaneRender® for Maya® 1.55 - 3.1 Win [OBSOLETE]
Moderator: JimStar
JimStar thank you very much for the Maya plugin update, I found a little bug that is not present in the 1.20a version, when you work with the IPR the render time keeps going and going and never stops even if the render finished, so If I left my render and leave for a second, is imposible to know what was the render time of the frame, please have a look at it, thanks. 

Thanks Jimstar for this update. I can't fait to finish the ongoing production to test this new version!
One question. Do you know if there another shading and node rearrangement planned soon? ( next year or later)
I'm still running the 1.20a and Iknow that I will have to redo all my shaders.Will this long and painfull task will last? Is there any plan to change the shading procède again? For the 2.0 or later?
It is for my information, to know how I manage my studio's pipeline for the next 1-2 years.
thanks
One question. Do you know if there another shading and node rearrangement planned soon? ( next year or later)
I'm still running the 1.20a and Iknow that I will have to redo all my shaders.Will this long and painfull task will last? Is there any plan to change the shading procède again? For the 2.0 or later?
It is for my information, to know how I manage my studio's pipeline for the next 1-2 years.
thanks
Laptop HP 8760w, I7, 16Go ram, Quadro fx3000m, Maya 2014, Octane 1.20a. Vimeo: http://vimeo.com/ciboulot/albums
Well, you are right, it's working! I was checking wrong file path. My bad, sorry.Did you check it on this version?
By the way, is there any way to check which version of plugin is currently installed? If not, will be very difficult for You to include this information somewhere, maybe in OctaneLive Account tab in render settings?
Ok, I understand.This is intended behaviour. GPU is working on your IPR, so all the swatches wait for the resources to refresh.
I've never stumbled on this information. Now I know it's not so easy.I already wrote about it long time ago. Maya's issue, not plugin's. Moreover, this issue is still present during all the versions: Maya's plugin API easily allows to save any chosen 8-bit image type, but if the parameter "save to 16-32 bit" is given to the same function - it does nothing. So, I was forced to place some "stub" into this place which writes always 32-bit exr file by plugin's stub if any HDR format is chosen from Maya's formats list. I can't change this list adding e.g. "EXR 16" and "EXR 32" by standard Maya's API (it does not have standard means for it) - only by some ugly hacks. So, either you always have 32-bit if these HDR formats are chosen, or always 16-bit. There will be a lot of complaints if I change it to 16-bit only, so taking into account cheap disk memory - there is 32-bit chosen, awaiting for Maya's developers finally fix this bug...
Thank you for support Jim

i7, 4x GTX 780, Maya.
- Digitaline
- Posts: 32
- Joined: Thu Feb 25, 2010 12:15 pm
Nice work Jim, even if it's not a stable version it's a pleasure to work with this new version.
- There is a bug in the animation batch render with exr ouput (maybe with 8 bit too), all the frames are flipped.
- There is a bug in the animation batch render with exr ouput (maybe with 8 bit too), all the frames are flipped.
Hi JimStar,
Nice to have you back
This version seems fairly stable for me. All of the bugs I'd found in v1.33 - 2.3 seem to be fixed apart from the legacy octaneDiffuse shaders not being recognized, it would be great if that can be fixed as it makes it a bit of a pain to pull older files up to the new version but it's not an issue going forward.
I have found one new bug: Multiframe Motion Blur doesn't seem to be working, it appears to be rendering the subframes alright but something is wrong with the averaging back into the final frame.
The visibility controls all seem to be working well.
T.
Nice to have you back

This version seems fairly stable for me. All of the bugs I'd found in v1.33 - 2.3 seem to be fixed apart from the legacy octaneDiffuse shaders not being recognized, it would be great if that can be fixed as it makes it a bit of a pain to pull older files up to the new version but it's not an issue going forward.
I have found one new bug: Multiframe Motion Blur doesn't seem to be working, it appears to be rendering the subframes alright but something is wrong with the averaging back into the final frame.
The visibility controls all seem to be working well.
T.
Win10 x64|i7-9750H 2.6 GHz|32 GB RAM | RTX2080 max Q 8GB
Hi Jim,JimStar wrote:What you mean by "noise issue", can you please explain? Or just point me to the post if it was explained somewhere…prodviz wrote:The noise issue is still present in the PMC kernel.
here's the original thread with a link showing the issue:
http://render.otoy.com/forum/viewtopic.php?f=28&t=39842
and this is the post by Oliveij which looks like the same thing:
http://render.otoy.com/forum/viewtopic.php?f=28&t=40311
cheers,
Steve
Hi JimStar, is this for real? I just saw a pop on the OTOY website that 2.0 is now available ~ see the attachment
Solomon W. Jagwe
3D Artist/Animator/Modeler | Independent Film Director
http://www.sowl.com | http://www.galiwango.com | http://www.nkozaandnankya.com
3D Artist/Animator/Modeler | Independent Film Director
http://www.sowl.com | http://www.galiwango.com | http://www.nkozaandnankya.com