Ok thanks, I think I'm going to have to spen some time playing with this although as of yet I haven't been able to fix it without completely destroying it. Yet again I have encountered another problem although this is with a different component. The error log reads:

Running model

Start! (C:\Documents and Settings\Luke Dalby\My Documents\3D Max Files\X testing\landing pod.X)
Loading X C:\Documents and Settings\Luke Dalby\My Documents\3D Max Files\X testing\landing pod.X...
Processing...
ERROR: Scaling null has a translation, ignoring it
Model units are 1024.00 units/meter
Sorting by Material...
Optimize Parts...
Welding...
Generate BGL...
Done!
WARNING: radius is too big for crash data
Generate crash tree 1 (1040 bytes)
Assembling: C:\Documents and Settings\Luke Dalby\My Documents\3D Max Files\X testing\landing pod.azm
C:\Documents and Settings\Luke Dalby\My Documents\3D Max Files\X testing\landing pod_0.asm(29) : error A2008: syntax error : pod_top
C:\Documents and Settings\Luke Dalby\My Documents\3D Max Files\X testing\landing pod_0.asm(8426) : error A2008: syntax error : pod_NonAlpha
C:\Documents and Settings\Luke Dalby\My Documents\3D Max Files\X testing\landing pod_0.asm(8430) : error A2008: syntax error : pod_skip_1
C:\Documents and Settings\Luke Dalby\My Documents\3D Max Files\X testing\landing pod_0.asm(8435) : error A2008: syntax error : pod_Cylinder05_1
C:\Documents and Settings\Luke Dalby\My Documents\3D Max Files\X testing\landing pod_0.asm(8428) : error A2206: missing operator in expression
IFMSK(4): Macro Called From
 C:\Documents and Settings\Luke Dalby\My Documents\3D Max Files\X testing\landing pod_0.asm(8428): Include File
C:\Documents and Settings\Luke Dalby\My Documents\3D Max Files\X testing\landing pod_0.asm(8428) : error A2206: missing operator in expression
ERRS16(1): Macro Called From
 IFMSK(7): Macro Called From
  C:\Documents and Settings\Luke Dalby\My Documents\3D Max Files\X testing\landing pod_0.asm(8428): Include File
C:\Documents and Settings\Luke Dalby\My Documents\3D Max Files\X testing\landing pod_0.asm(8429) : error A2206: missing operator in expression
BGL_CALL_32(4): Macro Called From
 C:\Documents and Settings\Luke Dalby\My Documents\3D Max Files\X testing\landing pod_0.asm(8429): Include File
Error!

(landing pod is what I called the exported file for the time being and sorry about the length).ps no prizes for guessing my name!

Ok, I think i have pretty much fixed these vertecies now using the optimizer modifier, without loosing too much quality. I may spend a little bit more time tweaking the values to get the best effects but now it is down to the problem I have posted above. I have tried to remake this component but it gives the same error unlike a different problematic section. I hope that if you can help with this then I will be sorted. Thanks again.

Hey Abyss,

The problems were due to the way you used the name (landing pod). MakeMDL doesn’t care much for spaces in the names of models it's tying to export.
If you had used this (landing_pod) everything would have been ok. Sorry I didn't catch it when you posted. I was too tired to see the forest for the trees

You should down load the Make Model SDK its always handy to have.

Also, I have written a MAXScript called TagTool. It will help you to name parts correctly on the aircraft. It's compatible with Max4 though 6 and very easy to use. Use the link to FSAlpha.com in my signature to get it.

Good luck on the project. 

FSEdge

Ok, slightly embarrasing. The reason it couldn't find them is because (remeber i told you I had 3ds max installed twice in two different locations) I was looking in the wrong place. Very nice script thank you.

Quote:


Can you post a screen shoot so I can see it? That would help.

Quote:


The rudder problem is due to the pivot point being oriented wrong. From the description it sounds like they rotate around the Y-axis. Rudders should rotate on the Z-axis. The alignment should be done while in Local system coordinate. Rotate the Z axis is it's pointing up and the X-axis is pointing out to the right.

Since the rudders actually move in FS tells me that you have used the correct naming convention.

FSEdge

Quote:


While in the Hierarchy tab you need to select "Affect Pivot Only". From there you can move and rotate the pivot without affecting the position of the rudder. While you’re doing this just make sure you have selected "Local" in the Reference Coordinate System and this is very important.

I received your email. The misplaced engine pod and the elevator look to be some sort of scaling issues perhaps. I can't say for sure without looking at the model for myself. Do you have the Max System Units set to Meters? If not you need change that.

Good luck

FSEdge

Right, well I found the reference coordinate system and it does slove the odd rudder rotation in fs, however it rotates the rudder model also. I do have local selected and affect pivot only.