Beta 2.2 RC1: Maya exporter plugin (unofficial)

[bazuka]

ur right i made a crap

fixing it now...

get it should work if not ill kill my self

[gzavye]

well it's OK for me; rendering well

Working on animation; but no motion blur in rendered images
do you have a tip to make it work?
Animation here : http://www.refractivesoftware.com/forum ... f=6&t=1654

[face]

The motion blur we have, was only camera motion blur, atm.
Octane doesn´t support object motion blur.

[gzavye]

Octane doesn´t support object motion blur.

oh
character animation without motion blur is little more flat in 3D

but plugin is working well for now; that's the very good news

[cgbeige]

a lot of people do motion blur in post with compositors like Nuke because the quality is very good and it's a lot faster than doing it in 3D. Try that if you have Toxik/Maya Composite.

[bazuka]

id like to thx face for some tips for maya exporter that im working at the moment and i hope will have some great updates in few days,

no need for camera aim, ull be able to use any camera u want and also light should work

cheers

[gzavye]

Yes I know how to do that with motion vector in MR and composite with After effects
But the goal is to render with Octane, not with OR+MR
MR knows unbiased with Iray; it knows progressive render too.
But just want to use Octane today

@bazuka : great!
Can't wait for new exporter

[SheepFactory]

Still no luck on my end

The "" at the end of the command is gone but I still get:

"There was an error parsing the command-line arguments:

Couldn't find match for argument Argument: C:\Users\Ali\Desktop\test\whatever.ocs
"

when octane launches and it shuts down after clicking the error away.


It is not creating the .ocs file based on the project name I set there. I tried just saving a empty scene in octane with the project name in that folder and when I do that octane launches without the error message I get above but gives me a :

"Automation Error. MeshNode for rendering 'test.obj' is not useable." Error.

Since its working for others I must be doing something wrong. By the way I am on version 1.021 beta 2.1 if it matters.

[SheepFactory]

After reading gzavyes animation thread I followed his steps exactly and I still get the mesh node not usable error. But if I click ok and close the error msg and click on the mesh node on the node view it works. So the script is exporting everything fine. Any ideas why I am getting that msg in octane?


Sorry for all the problems and questions

[face]

A little hint for you to check it self.
The layout of the things that will send to Octane is simple.
Here an example:

First the binary:
octane.exe

Then the first command:
octane.exe -r

First command parameter:
octane.exe -r "C:\Users\face\Desktop\Project\test.obj"

After this, a new command is comming.

Important to know:
Commands begin either with a - or a --
Values can have a - too. That is not a command. It will be follow by a numeric value. eg -12.1254

The layout is also:
execute[space]command[space]parameter[space]nextcommand...
You can check if after each command a space comes. And if filenames are between "".

A typical layout:
octane.exe -m test.obj -r "C:\Users\face\Desktop\Project\test.obj" --cam-up-x -0 --cam-up-y 0.995037 --cam-up-z -0.0995037 --cam-target-x 0 --cam-target-y 0 --cam-target-z 0 --cam-pos-x 0 --cam-pos-y 2 --cam-pos-z 20 --cam-fov 53.638 --cam-aperture 1 --cam-focaldepth 5 "C:\Users\face\Desktop\Project\test.ocs"

In colors:
octane.exe[space]-m[space]test.obj[space]-r[space]"C:\Users\face\Desktop\Project\test.obj"[space]--cam-up-x[space]-0[space]--cam-up-y[space]0.995037[space]...

Hope that helps a little, so you can help to disburde the scripters

face