f16jockey_2

Guess what, I found these same textures in the Livery Pack I got when purchasing the DC-2 back in 2012 (from Flight1 indeed). Even the [fltsim.x] entries are identical. As you can see: no problems with them. As said, you need to reinstall the DC-2 with all included model and panel variants. (to enlarge: right-click -> open in new tab) @Downwind: I had to use a magnifying glass as well, your eyes are OK. Wim

Then I suggest you reinstall the aircraft from your original installer. As I mentioned, the textures you've downloaded are made for a variant model. Wim

On the 1st screenies: ... model=int panel=old ... On the 3th screenie: the folders model.int and panel.old aren't present. So change the entries to model= panel= This may work, although the textures seem to be made for a variant model of the aircraft. OTOH the forementioned folders are present on my install. I start to wonder where you got that DC-2... Wim PS. It's UIVER, not Univer PS2. Do something with the resolution of those screenshots !!!

Nevertheless it wouldn't hurt to post the [fltsim.x] part of your fsx.cg. Wim

You mean the aircraft crashing into a scenery object upon loading, or a computer crash? If it’s the first, disable crash detection. If it’s the latter, see the post above. Wim

What's your default flight (aircraft/airport) ? Did you change it recently? Wim

Now you've done this (twice), it's good practice to check your inbox for replies :cool:. Wim

Not helpfull. Wim

Looks like you have a double install? [color=#333333]Looking in registry for FSX install path:[/color] [color=#333333]HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0[/color] [color=#333333]Parameter"SetupPath"[/color] [color=#333333]... >>> OK! FOUND FSX! [color=#333333]SetupPath=[/color][color=#ff0000][b]C:\Program Files (x86)\Steam\steamapps\common\FSX[/b][/color] [color=#333333]Looking in registry for FSX-SE install path:[/color] [color=#333333]HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX[/color] [color=#333333]Parameter"Install_Path"[/color] [color=#333333]... >>> OK! FOUND FSX-SE! [color=#333333]SetupPath=[/color][color=#ff0000][b]F:\Steam\steamapps\common\FSX[/b][/color][color=#333333] [/color] The installer takes one for FSX Boxed, the other for FSX-SE. But both paths say Steam? For me it's confusing, maybe for the installer as well... Wim

Apparently I solved this in 2010 already, as I replied to an earlier post of yours in 2018 (!). https://www.flightsim.com/vbfs/showthread.php?311195-Floating-Control-Tower&p=2047789#post2047789 I still have the fix installed. Send me a PM. Wim

Below are my installation files for the Uiver DC-2. Doesn't come anywhere near yr pic. We're obviously talking different things. Sorry, I'm out. Wim P.S. Your pic is close to unreadable.

Tick the "Show all Variations" checkbox near the bottom of the Aircraft Selection Screen. Wim

If you mean the Uiver DC-2: I have it, it's genuine FSX. The props never needed fixing, so I'm pretty sure the file doesn't exist. Maybe (wild guess, as with all yr questions): are you running the FS9 version on FSX? Wim

Thanks for the ample explanation on how you solved the problem. Idem dito for the other thread. Wim

You're right. Didn't take enough notice of the fact it's an A340-500. Point.0 is the extra center main gear. But I stay with my initial reply to increase the Max/Static Ratio (the 2.500 value). Wim

Sorry Charlie, I dare to disagree. To make the nose gear stiffer, the Max/Static Ratio should increase. For example: point.0= 1.000, -7.750, 0.001, -17.600, 1574.800, 0.000, 2.367, 0.000, 2.210, 3.000, 0.847, 11.700, 11.100, 1.000, 0.000, 0.000 Formula is: Static Compression = Max Travel divided by Max/Static Ratio Static compression itself can maybe be lowered a bit, but don't change too much at a time in between test flights, and make backups! [EDIT] From the original CP section, we can calculate Max Travel as 2.210 * 2.200 = 4.862 When increasing the ratio to 3.00, Static Compression should be 4.862 / 3.00 = 1.621 The numbers are an example, and IMO 3.00 is too high, and therefore 1.621 too low. BTW By assigning a key combo to "Aircraft Reload", you can keep aircraft.cfg open for editing, and test the results without leaving FSX. Wim

No, that was the FS9 way. In FSX they don't show because they don't have a panel folder, as Jorgen said. Wim

In the FMS you can change the programmed speeds for CLB/CRZ/DES. The procedure depends on the type of FMS. Wim

Some FSX models use specular map for reflections. Alpha is more FS9 style. For some reason, which I can’t remember, I’ve dumped the QW 757. So I can’t check. Wim

I watched the video. Looks correct and complete to me. The steps to solve the black cockpit are at 6:40 Copying and renaming the textures and very important at 7:50 Creating a texture.cfg. Wim

This eliminates liveries only when using a selective search in the Aircraft Selection UI. BTW. If it was my sim, I'd change all ui_manufacturer entries to "Piper", as it is in RW. Alabeo only deserves the ui_createdby entry. Wim

I hope I'm wrong, but imo AIG (amonst others) has silently dropped FSX forever. Their announcement for AI Manager 1.1 Beta only mentions P3D and "the game". AI Manager 1.0 (with FSX support) has been taken offline. Wim

The FS2004 feature of adding a bitmap as foreground to outside views was discarded in FSX. In stead, the virtual cockpit is shown when using the hat switch. Your Osprey most likely doesn't have a VC. Wim

DLed and installed the panel. In addition to yr observations: the gauge is there (I see the cursor change to hand, and there's a tooltip) but I can't get it to work either. This is where my contribution ends, I'm afraid. Wim

I don't have it installed, just "stole" the image from the download preview. You know the gauge name? Can you check if the gauge is listed in panel.cfg? If so, you only need to copy the corresponding .gau, .xml or whatever file to the panel folder. Wim