jgf

But you still need the correct values to enter. I have Aired, AAM, and Airwrench, all of which easily edit these parameters; but there is so much interaction between them and also with the fuselage angle, and editing any one usually entails editing at least one other that it often seems like trial-and-error in hopes of getting something "close enough for government work", much less finding the truly correct values. Airwrench implies it can recompute the gear data, but either that is an optimistic claim or I'm not using it correctly.

Plenty of time. We'll all wait for you.

Thanks, I'll give that a shot. I have an old Fs2002 airplane that I'm trying to tweak for FS2004, abandoned the project a couple of times, eventually ran it through Airwrench, which helped ...but i still cannot get the gear adjusted properly (which is how I found the above pdf). It either: bounces all the time it's on the ground, or bounces all the time it's taxiing, or bounces whenever above 40kts, or doesn't bounce but the nose gear buries in the runway as soon as you touch the brakes, or all works well but the main gear are a foot off the ground. Not sure which is the current state, haven't cursed it since last summer.

... the next flight

I didn't even wait, just removed the race placards from the fuselage and continued ....all the way around to Jandakot.

Call ahead for an aircraft carrier to be halfway along that leg.

Lol, it has been eight years since I flew the XB-70 and had forgotten how powerful it is. Trying to fly by regs - keep it below 250kt til over 10k ft (does that rule hold in Australia?) - I got a jolt when I saw 500kt before she'd even reached 2k ft. No doubt residents were burning up the phone lines with complaints. (Mental note - use autothrottle once you've cleared the runway.)

Lol, my routes don't cross themselves.

I wouldn't be surprised. In reading about my Beech I found that several owners, frequently needing longer range, would remove the rear seats and mount a fifty gallon tank back there. This gave the plane about 1600 mile range ... eight to nine flight hours.

Here is some more data from ages ago; I understand it but cannot figure out how to derive the data it wants to compute the landing gear parameters.contact_points.pdf

Create it as a popup, that's what i did on the Beech (and my P-38).

Lol, I'm reminded of the old Sims 3 game, it had such excruciatingly long loading times that the devs actually built a hidden object game into the loading screens for you to play while waiting (find the mailbox, find the red bird, etc.).

Generically for all older games in Vista or newer, DO NOT install to any "Program Files" folder, run all exe files as admin, you may have to temporarily disable DEP, you may have to whitelist the exe files in your anti-malware, and make sure your account has full access to all pertinent folders. All this is due to increasing file security in each new windows version, which is even more strict in the "Program Files" folders; any software not written with that in mind may have issues with file access.

Got a wild hair, took her out of mothballs, and flew from Sydney to Haneda; here we're climbing through 41k ft on the way to 60k

Were I condemned to live til completion of my version of that I'd be damn near immortal.

https://theaviationist.com/2020/08/10/take-a-look-at-these-incredible-shots-of-the-russias-sole-completed-lun-class-ekranoplan/ https://en.wikipedia.org/wiki/Lun-class_ekranoplan There is a model for FS2004 from Alphasim/Virtavia, now freeware.

Take your pick

Maybe this will help- //0 Class <0=none,1=wheel, 2=scrape, 3=float/skid> //1 Longitudinal Position (feet) //2 Lateral Position (feet) //3 Vertical Position (feet) -4.70, -4.99 //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) 0.9100 //11 Extension Time (seconds) //12 Retraction Time (seconds) //13 Sound Type point.0=1, -17.40, 0.00, -4.60, 1181.1, 0, 0.6349, 60.0, 0.4000, 1.5, 0.5100, 4.0, 4.0, 0, 0.0, 0.0 so “point.0” is just the sequential number of each individual contact point “=1” is the class or type of contact point it is, meaning 0=none,1=wheel, 2=scrape, 3=float The next three are just the position location format you are now familiar with. The fourth tells us how hard a landing this gear will survive, in this case 1181, whatever that actually means (PSI of pressure impact? Dunno). The fifth one is the brake map, and I recommend that the nosegear is listed as “0” for none (just like this one is), or it will interfere with the differential braking ability, while the others will need to be listed as either left or right (1 or 2). You will know which one is the left wheel by seeing it has a minus – sign on the lateral position value. The sixth 0.6349 is the diameter of the wheel, if you have wheels. The seventh value will only likely apply to the nosegear, as this determines the degree of freedom the nosewheel will turn for taxiing, here it’s 60 degrees. Eighth is Static Compression, meaning how much will the gear compress 0.40 when the aircraft is parked on the ground. 9th, Max/Static Compression Ratio tells us how much difference there is between the static compression position, Vs the maximum compression position (like during a very hard landing that fully compresses the shock absorbers) here 1.5 (feet? Not sure if just a ratio though). Tenth is the Damping Ratio meaning how hard are the shocks (0=Undamped, 1=Critically Damped) here it’s about half ways at 0.51. The last three only edit the speed at which they extend/retract, and whether a sound should be associated with the event. Static Compression and CompressionRatio, items 8 and 9, are what you need to tweak. But it's a royal PITA as there is some interaction between these settings and the fuselage angle and the damping ratio and.... Good luck

The one negotiating the crazy taxi line? That is a C-5 Galaxy with a custom paint job. But I do enjoy the Be200 And the Be-12

No, FS9 gives you this

All I can think of is layering or incompatibility with some other scenery (usually due to overlapping nav aids). I had a "German landmarks" scenery that would cause an instant CTD when I took off from any airport, any runway, any aircraft, in southern Germany or SE France and climbed to 1500ft. No problem if I stayed below 1500ft, but the locals might complain of aircraft tooling along 1200ft above their homes. I never found the exact cause of the CTD, but disabling that scenery eliminated it. (Had too much other scenery in the area to deal with a "process of elimination" ordeal to find the problem.)