Hello,
At first, excuse my english, i'm french.
i'm just a very new user for octane ( since 2 days) and i have to congratulate the team for octane : the renderer i've ever dreamed of, with a 'photographic' logic and result and to my mind a very intelligent and creative concept...
I own a MAYA 6.0 licence ( old but still excellent ) and i want to tell you : the MAYA 2009 version of the script works very well with octane ( animation, Dof, good focal camera conversion etc...) but only with the beta 2.44 ( -> with 2.46b, a error message appears after rendering 2 or 3 trames, saying that the 'obj' object of the project is unusualable ). So:
(1) In future, please can you STILL develop a 2009 version of the script ( with the 2011 version, i don't have acces to the disk-path request for choosing output, .exe etc..., ilt makes an error when clicking the boxes) for the future versions ?
(2): i hope the new version of scripts will be able to work with the last version of octane...
Long life and success to Octane and their developpers !!
extra:
with my lightwave10 license: same problem: i have to use the 2.44 because animation doest work and the OBJ exporter ( or the process after clicking the render button ) is VERY slow...
extra2:
i'm waiting a blender 2.57 official plugin because the existing one (non official seems to have some problems with anim)
**RESOLVED bug with 2.46b**& hope for maya2009 continuation
Moderator: JimStar
Hmm, unfortunately I don't really understand, what the problem here is. There have been no changes between beta2.44 and beta2.46b regarding the OBJ import, beside the addition of Unicode support.
So, when you get this error message, can you open the exported OBJ file directly (i.e. by adding a new mesh node and then selecting the exported OBJ file)?
Cheers,
Marcus
So, when you get this error message, can you open the exported OBJ file directly (i.e. by adding a new mesh node and then selecting the exported OBJ file)?
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Sorry
i did a mistake, it's not about the 'obj' but the ocs file ( look at the lower picture attached to this post ).
So when it happens ( always after the 2nd or generally 3th frame of rendering, with the 2.45 or 2.46b versions of octane, but no problem with 2.44 version ), the animation rendering process stops ( of course
) and if i launch a manual rendering with the same session ( just after the error message): it works !..
Another thing i can't understand is ( i hope you will understand):
when i want to generate a new ocs file from octane( same scene but with a new name, for new texturing or rendering settings ), and when i choose, with maya exporter, this new setting file ( ie 'maison2_.ocs' like the picture attached ), it doesnt work ( look at the upperpicture attached to this post error message with 'maison2_.ocs' -> meshnode not useable ): but if i launch a manual rendering process of 'maison2_.ocs' directly after this error message, it works ( with the new settings ):
can you explain me why ? ( (i tried with many different files, always this problem even with the 2.44 version ( and 2.45 & 246b too) )
perhaps have i miss something...
Thanks per advance
Vincent
i did a mistake, it's not about the 'obj' but the ocs file ( look at the lower picture attached to this post ).
So when it happens ( always after the 2nd or generally 3th frame of rendering, with the 2.45 or 2.46b versions of octane, but no problem with 2.44 version ), the animation rendering process stops ( of course
) and if i launch a manual rendering with the same session ( just after the error message): it works !..Another thing i can't understand is ( i hope you will understand):
when i want to generate a new ocs file from octane( same scene but with a new name, for new texturing or rendering settings ), and when i choose, with maya exporter, this new setting file ( ie 'maison2_.ocs' like the picture attached ), it doesnt work ( look at the upperpicture attached to this post error message with 'maison2_.ocs' -> meshnode not useable ): but if i launch a manual rendering process of 'maison2_.ocs' directly after this error message, it works ( with the new settings ):
can you explain me why ? ( (i tried with many different files, always this problem even with the 2.44 version ( and 2.45 & 246b too) )
perhaps have i miss something...
Thanks per advance
Vincent
- Attachments
-
-
Just for your information: You get the automation error, if the exporter tries to select a mesh node that doesn't exist. In your case it tries to select a mesh node maison2_.obj. I guess, you originally exported the scene with the project name maison2.ocs and then renamed the OCS file to maison2_.ocs, while the mesh node is still called maison2.obj.
Cheers,
Marcus
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra