OTOY Forums

Is there a problem going from a Maya scene that is in centimeters to Octane? The camera is in worldspace in Maya, and its not transferring over correctly.

What is the camera lens aperture radius?

In what of unit need work in maya, and what unit need in octane? meter to meter?


Because I have this problem - http://www.refractivesoftware.com/forum ... f=9&t=7469

Thx.

HI,
Great work with the plug-in. It was working very well for me until I started receiving this message when I was trying to update my Octane scene with my new Maya scene.

----- meshnode for rendering "test.obj " not useable ----



!!!!!!!!!!!UPDATE!!!!!!!!!!!UPDATE!!!!!!!!!!!UPDATE!!!!!!!!!!!UPDATE!!!!!!!!!!!

So I think I figured out the problem. The issue seems to arise when I save out a new version on the Octane scene while still in Octane.

Let's say I used the export plug-in to move a Maya Scene into Octane. This is now OctaneScene_v1. I do some work, save it out, work in Maya then bring it back to Octane using the plug-in and the same file OctaneScene_v1. I do some more work but this time I want to save the scene as OctaneScene_v2. I do this in Octane, then go back to Maya. I do some more work in Maya, now, I want to bring the scene back into Octane and this time use OctaneScene_v2 as my file. This is when the problem occurs and I get the error stating that the meshnode is unusable.

If I try to load the new Maya scene using OctaneScene_v1, there is no problem, and the mesh will update. But if I try to open my updated mesh using the new scene file I saved while in Octane, OctaneScene_v2. The problem occurs, yet I can manually update the mesh by re-importing it through the add-mesh node.

So there is no problem with the mesh, the error occurs with incremental scene versions saved out of Octane and used to load the plug-in.

Hope this helps.

Hello there. Is there any chance of porting this script to Linux (ubuntu to be more specific)? it would be wonderful.

Upon use of the script in Ubuntu i receive this message:

There was an error parsing the command-line arguments:

Couldn't find match for argument Argument: Render/002.obj

the rest is an explanation of the use of the render call it receives I suppose.
------------

After blundering around in the script I'm noticing....

------------
I needed to take the space out of the Folder name. It starts. The camera position doesn't stick through the export though. only the rotation. (This may not be the true case, I notice that when I create a new camera that it is tiny! Probably a Maya issue.)
------------
now if I could only figure out the unit conversion...oh wait! i just set octane to change it. Just so you know:meters to Meters still doesn't work in octane.

Well, after messing around with some settings it seems that the camera position upon export isn't (scaled) taken into account...not really. I'm not sure how to put it, but I'm sure this is a maya thing. When I have maya set to centimetres, and octane set to meters it exports fine, so it seems. I bet the the camera is still off, but just not as much. Also with these settings I have almost no control of AO in octane. i would really like to get to the bottom of this.

-------------------

i decided (rename) to delete my userprefs.mel and somehow everything works fine with no further adjusting in maya! The units are set to CM, but it/everything exports just fine. With Octane using meters to meters, it works just like the video. YAAAAY! Now, if i could only learn how to model.

I am having an issue with the Maya FOV importing into the Octane (2.52) release. I am using Maya 2010 and it is not getting along with the new verison of Octane. My camera is all over the place. Im not sure if this is a new bug that happened in the latest release or if it has been a known issue. I do a lot of animation and moving cameras so this is an issue. I am hoping to post some of my work done in octane soon... if I can get this camera issue figured out.

Thanks.

Is it possible to have animated textures with the maya exporter?

Didn't check the latest script version but I guess it's not possible.
I think the best option for now is to modify the texture path in the ocs file before rendering each frame...
This could be automated by the script.

Thank you tchoa,
I will think about a work around until the script will be updated.