object visibility not working? and other problems.

[vanlicht]

Hi Bazuka,

I was trying out one shot to render, but there are some problems i encountered:
1. When exporting to octane, all those geometries which were hidden in Maya are all visible now in Octane.
I thought you mentioned a while ago the visibility issue was fixed in the plugin?

2. When I execute the plugin, my rig got all screwed up, the leg is flying up high in the air.
I am not sure why this happen...I though maya2octane should only run something that's not harmful to the scene itself?

My scene file contains the following components:
rigged/ skinned geometry (used as reference files)
nCloth simulation cache (contained in the file itself and being cached out)

Best,
Tomas

[bazuka]

i was on vacation, ill check ur probl asap

i think i know whats the probl...

[bazuka]

i will make a modification for u my friend, i think ill have to remove scale thing coz of the probl some people have...

[vanlicht]

Cool. Will wait for the update then.
Hope you have a good vacation.

[bazuka]

here u go, scale modification is removed, and visibility should work...

let me know if u still have any probl

cheers

[vanlicht]

Hey Bazuka,

I tried the new plugin you attached.
Result:
1. The rig seems behaving fine now. Not jumping around.
2. unit still doesn't work. CM or Meter both have the radiating black marks.
3. visibility still doesn't work. All the blenshapes and things that I hide still shows up in the render.
4. I also tried it with pre-2.3, it doesn't work I think the scale thing is the problem.
Either cm or meter, the scene is always so faaaaar away that I can't reach in with the camera.

Hopefully there will be plgin updates to solve these problem.
Thanks,
Thomas

[bazuka]

i have some probl with scaling units and camera position, trying to find the solution...

hope ill have something soon

cheers

[nick]

will this new plugin have the export only camera animation too ?

[eyearmy]

2. unit still doesn't work. CM or Meter both have the radiating black marks.

That's because your objects are being scaled up by a factor of 10000.

The current state of affairs is this:



All hail the Hundred Meter Box!

(Unnecessary Disclaimer: The box was created in Maya on a centimeter scale, and then exported to OBJ with the latest version of the script. It was then imported into Rhino, because I hate Maya's measurement tools. Rhino was set up to work on a millimeter scale, but it doesn't really matter, because OBJ files are unit-agnostic.)

Bazuka, you should scrap the entire scaling routine as it stands now. The only scaling that we need here is "set the group's scale values to 0.01", and it would get us perfect results every time. Maya thinks in centimeters; Octane expects to be fed with meter-based data; there's nothing more to this.

...but what I really meant to say is: thank you for your work, mate! =)

P. S. Ah, I missed the updated version of the script posted above; unfortunately, removing exportScale achieves nothing, because meshes coming out of Maya are still 100 times bigger than they should be.

[bazuka]

thank u people for reply,

@nick
yes there is only cam export

@eyearmy
to be honest im a bit confused, i know that the mayas thinks in cm by default

try latest ver of exporter and let me know if i manage to fix it, if not then ill will need ur help to solve the probl

so, if i got everything right this hows everything goes

if u make box 1x1x1cm then u need to scale it 100x so u can get 1x1x1meter box, right?

and if u make 1x1x1meter then u dont have to scale anything, before u export, or im still wrong?

cheers