Hi J_o_J. I used to specialise in this but it's some time since I've done it. You need to tweak the tailwheel entry in Aircraft.cfg. Open it in Notepad & find the [contact_points] header. The tailwheel entry is usually point.0. I've copied this from the default Wildcat.

point.0=1, -16.80,  0.00, , 3200, 0, 0.40,180.0, 0.30, 2.5, 0.90, 3.0, 3.0, 0, 0, 235

The entry in red is the vertical height (in feet) of the tailwheel relative to the datum point or virtual C of G of the aircraft. The negative value means it's below the datum. To lower the tailwheel decrease the actual value. Do this gradually & check it out each time until you get it right.

The static_pitch angle might also need tweaking. To check this hit the Y key to display it in Slew mode. Hope this is some help. If not tell me the page the aircraft is posted on & I'll have a go myself.

OK. I'll check it out.

Quote:

You misunderstood me. That would raise it even more. When I said reduce it I meant reduce the actual number. I would start off with something like -3.00 & take it from there.

I always exit CFS2 before tweaking anything & restart it again each time I want to check it out. This way you're certain you're seeing the changes.

PS. The static height & static pitch are often set wrong on 3rd party aircraft. If this is too far out it would cause the aircraft to drop noticeably when it first loads in CFS2. On some aircraft it's enough to make it blow up before you get the chance to start the engine.

Thanks for the tip on this one. I've been busy fixing my fleet and getting all wheels on the ground. I think in some cases a floating tail wheel results in a low take off angle of attack on the runway, then take off can be long and difficult.

As for restarting csf2 each time for testing, I found that was not needed for this contact point change. I would test in free flight and before making changes would switch to another aircraft in the program, then switch to the desktop and use notepad to change the .cfg file. Then back to csf2 which is still running and then back to my topic aircraft for a test fly. Back and forth this way usually works very quickly without ever exiting csf2 for testing. If you don't choose a different aircraft before making the changes, csf2 won't upload the changes immediately.

Jimski

I can exit csf2 fast enough, but when I restart it I think it takes a few minutes before it is ready even if I skip the opening movie. How are you getting it up and running from scratch so quickly?

Jimski

Tried your method and yes it works well. My PC is about five years old and csf2 takes over a minute to load on the first go but after that I can exit, edit a model, and the return to csf2 free flight is less than 15 seconds.

On the same subject, can one speed up the "mission builder" startup? Acutally I have never found a mission builder execute file anywhere. Must be under a very different name.

Jimski

Thanks Hagar, you're a star. Works perfectly - patiently explained.

J_o_J