flight dynamics

[Oz]

Anyone know of a program that lets you change the .cfg files and has a user-friendly interface. Or maybe a tutorial that explains what all the numbers stand for in notepad. See i got a couple crafts that have high contact points and i wanna change that, along with their flight characteristics.

[Hagar]

Oz. If you have FS2002 Pro you can use FSEdit. I prefer Notepad.

[Brian_Gladden]

FS edit will many times totaly destroy an air file..... I have been using the Shareware Aircraft Container Manager. Some do not like it because it had a Model export feature that may have allowed some model piracy to ocur. I tried this feature and got a file that nothing could open so to mi it's not a big deal. It does however allow you to see the model in 3D with textures (great for repainting) and gives a nice mesh view for editing things like fuel tank locations, contact points and adding in lights.

Brian

[Oz]

Normally i try to use Notepad, but i dont know exactly what each number represents. Unfortunately i dont have FS2002 Pro, so i wont be able to get FSedit

[microlight]

I thought that FSEdit only let you edit the .cfg file? The only time I've used FSEdit recently was to convert the default AI Dash 8 and MD83 to flyable versions. I now edit the .cfg file using Notepad - many of the default aircraft have a text key at the start of each complicated section to let you know what the figures mean, e.g.

[GeneralEngineData]
engine_type=1 //0=Piston, 1=Jet, 2=None, 3=Helo-Turbine, 4=Rocket, 5=Turboprop
Engine.0=4.75, -16.1, -2.5  //(feet) longitudinal, lateral, vertical distance from reference datum
Engine.1=4.75,  16.1, -2.5  //(feet) longitudinal, lateral, vertical distance from reference datum
fuel_flow_scalar=1    //Scalar for fuel flow efficiency

from the default 737 .cfg file.

I use AirEd (easily available by using any search engine) to edit .air files.

Hope this helps.

[Oz]

Thanks for the hint microlight. Unfortunately what i really want to change is the contact point cause the craft i got is just too high. This is what i wanna change:

[contact_points]
point.0=1,  8.48, -9.90, -3.6, 19500, 1, 0.5, 30.0, 0.54, 5.5, 0.5, 0.0, 0.0, 0, 0, 150
point.1=1,  8.48,  9.90, -3.6, 19500, 2, 0.5, 30.0, 0.54, 5.5, 0.5, 0.0, 0.0, 0, 0, 150
point.2=1, -7.02, -9.90, -3.6, 19500, 1, 0.5,  0.0, 0.55, 5.5, 0.5, 0.0, 0.0, 2, 0, 150
point.3=1, -7.02,  9.90, -3.6, 19500, 2, 0.5,  0.0, 0.55, 5.5, 0.5, 0.0, 0.0, 3, 0, 150
point.4=4,  8.48, -9.90, -2, 19500, 0, 0.5, 30.0, 0.34, 5.5, 0.5, 0.0, 0.0, 0, 0, 150
point.5=4,  8.48,  9.90, -2, 19500, 0, 0.5, 30.0, 0.34, 5.5, 0.5, 0.0, 0.0, 0, 0, 150
point.6=4, -7.02, -9.90, -2, 19500, 1, 0.5,  0.0, 0.35, 5.5, 0.5, 0.0, 0.0, 2, 0, 150
point.7=4, -7.02,  9.90, -2, 19500, 2, 0.5,  0.0, 0.35, 5.5, 0.5, 0.0, 0.0, 3, 0, 150

static_pitch=0.000000
static_cg_height=4.20000

Oh, just wondered now, is "static_pitch=0.000000
static_cg_height=4.20000" the only thing that counts when it comes to how high an aircraft is on the ground? or do i have to change the points too?

[microlight]

No problemo, Oz.
Here's the test list from the default 737's contact point section:

//0  Class                        <0=none,1=wheel, 2=scrape, 3=float>
//1  Longitudinal Position        (feet)
//2  Lateral Position             (feet)
//3  Vertical Position            (feet)
//4  Impact Damage Threshold      (Feet Per Minute)
//5  Brake Map                    (0=None, 1=Left, 2=Right)
//6  Wheel Radius                 (feet)
//7  Steer Angle                  (degrees)
//8  Static Compression           (feet)  (0 if rigid)
//9  Max/Static Compression Ratio
//10 Damping Ratio                (0=Undamped, 1=Critically Damped)
//11 Extension Time               (seconds)
//12 Retraction Time              (seconds)
//13 Sound Type
//14 Airspeed limit for retraction     (KIAS)
//15 Airspeed that gear gets damage at (KIAS)

This list gives you what all the figures refer to. Points 0, 1 and 2 are the undercarriage, and the 4th figure along on on each of the lines (3.50 in your example) is the vertical height. If you change this value, the plane will either sink into the tarmac further(!) or rise up out of it. Play with the values until the plane is where you want. The c_of_g figure is linked to the vertical height, and you need to change it when you change the vertical height parameters, otherwise the plane may drop from a few feet up when you load up, or spring out of the ground if it's too low. If the crash parameters are too sensitive, you could 'crash' the plane as soon as you load up, so it's worth watching for.

Good luck!

[microlight]

Oops, I meant '-3.6' in your example!

[Oz]

Many thanks microlight!  :)

[Oz]

Well, got a little issue now: Ive reached the last digit, 0.0 but still the craft is a few feet off the ground. Where else do i go from 0.0? And BTW, heres what im fixing..



It doesnt look too high, but thats caus of the camera anlge.

If i get to fix the problem, ill upload the car  here

[microlight]

Ah - one of those strange 4-wheeled aeroplanes without wings! I haven't done much with cars: I downloaded a Jaguar XK120 from somewhere or other (can't remember now) but haven't used it much. Here's the contact point info from that .cfg file - perhaps it'll give you a lead. I can't see anything else in the contact point info that would affect the height off the ground - unless anybody else out there knows different?

point.0=1,  2.48, -9.50, -4.46, 4500, 1, 0.5, 23.0, 0.34, 5.5, 1.0, 0.0, 0.0, 0
point.1=1,  2.48,  9.50, -4.46, 4500, 2, 0.5, 23.0, 0.34, 5.5, 1.0, 0.0, 0.0, 0
point.2=1, -5.02, -9.50, -4.52, 4500, 1, 0.5,  0.0, 0.35, 5.5, 1.0, 0.0, 0.0, 2
point.3=1, -5.02,  9.50, -4.52, 4500, 2, 0.5,  0.0, 0.35, 5.5, 1.0, 0.0, 0.0, 3
point.4=4,  2.48, -4.50, -4.00, 4500, 0, 0.5, 23.0, 0.34, 5.5, 1.0, 0.0, 0.0, 0
point.5=4,  2.48,  4.50, -4.00, 4500, 0, 0.5, 23.0, 0.34, 5.5, 1.0, 0.0, 0.0, 0
point.6=4, -5.02, -9.50, -4.00, 4500, 1, 0.5,  0.0, 0.35, 5.5, 1.0, 0.0, 0.0, 2
point.7=4, -5.02,  9.50, -4.00, 4500, 2, 0.5,  0.0, 0.35, 5.5, 1.0, 0.0, 0.0, 3

static_pitch=0.000000
static_cg_height=0.000000

Let me know if I can help any further.

[Oz]

All right got it fixed, thanks again microlight