posted 01-21- 09:38 AM               

Whats it got? Well it includes:

* Automatic parts positioning/rotation based on MAX rotations/positioning

* Some DOF alignment tools

* A reset XForm tool

posted 01-21- 12:33 PM               

after typing 'old_mat = $.transform' I get this: --Syntax error: at end of pathname, expected level name

When I run the export script this message appears: --Type error: Call needs function or class, got: StringStream
(in line matrix_filename = stringStream "")

I tried this with Max 2.? (2.0?)

I didnt know anything about scripting in Max - did I made a mistake ?

posted 01-21- 01:51 PM               

Right now OPStudio erases/cuts or otherwise deletes any DOf entry for cockpits ...

This forced me to do my FM editing by text with the latest batch of planes sent to me by Mposis and Yardstick ... (they all have opening cockpits) ...

Can you look into this?

posted 01-21- 04:29 PM               

export_filename = stringStream ""
matrix_filename = stringStream ""

to

export_filename = "d:\sdoe\hurricane.obj"
matrix_filename = "d:\sdoe\hurricane.mat"

and deleteing

format "%.obj" base_filename to:export_filename
format "%.mat" base_filename to:matrix_filename

I think that you will run into other problems since the listner window command didn't work, and these commands are fundamental to the script.

Zur: I know what this is, basically the DOFs are one one side of a file reference and the canopys are on another. I didn't fix it in this one but I don't expect it to be too hard.

Tailslide: I didn't know that was a problem, but I just tried it (on the typh) and it worked OK, both cut/paste and copy/paste. I did the action on the file reference. One little thing I noticed while doing it was that deleteing the group items causes some problems.

posted 01-21- 07:17 PM               

'old_mat = $.transform' also dont work with max 2.0 - it looks like I had to find another way to tell max to modify the selected objects, cause $LWTip.transform works... or I do this per hand for all objects - BUT I realize that after '$name.transform = matrix3' I had not to rescale or rotate anything (I think this is because I reset transform and rotation and scale some days ago) - the object moves just to the world origin and after '$<name>.transform =old_mat' all is fine again - so should I do this anyway (does the script this or not ? I´m a bit confused again - maybe I didnt understand the readme file)

after this I use the changed script (THANKS FOR THE FAST HELP!) and all looks good - I get 3 files and the matrix file looks quite good for me:

3
leftAileron : #Matrix([1,0,0], [0,1,0], [0,0,1], [-9,1256,-2,57559,-0,0919419])
leftWing : #Matrix([1,0,0], [0,1,0], [0,0,1], [-3,03863,-2,05148,-0,00762759])
LWTip : #Matrix([1,0,0], [0,1,0], [0,0,1], [-9,94278,-0,0918095,-0,0372034])

this is my "test" wing - in OPS I copied the leftWing (and children)of the P51D and removed all unused LODs so that only 3 LODs remain. But I still got the message ..."LWTip´s" parent, "left Wing" has no imorted matrix..."leftWing" has no imported matrix...and so the objects/LODs are not positioned correctly but better than before (spaces between them gettin smaller and alignment on the axes looks god )

I´m sorry to bother you again with that but I really hope you could help me once more.

posted 01-22- 06:31 PM               

'$name.transform = matrix3 1'

posted 01-22- 06:42 PM               

Bryan - when I finished the texture mapping for all objects, ah - I got something in my mind, ahm - could I send you the model (with the correct names for the objects) and you just export it (PLEASE) to OPS and send me back the sm file (with correct positioning)? ? ?

thanks so far - LK

posted 01-22- 07:35 PM               

Will there be editing of ObBodyPts anytime soon in OPS? It's great seeing them but it's still very tricky to edit them.

posted 01-24- 12:58 PM               

Maybe I just screwed something up, and I haven't had a chance to try and replicate this yet. Anybody else have a compatibility problem between 1.0 and 1.2?