Hi,I ported over the Aerosim L1011 from fs9 into fsx. I read that the crashes are caused by the gauges. Has anyone succeeded in making it work in FSX or found out which gauges are causing the CTD? I really like this plane, and since I'm only flying FSX it's such a waste of a wonderful model.

Not tried fixing the L-1011, but I can tell you the easy way to sort out it out, which I did on the Aerosim B737-200, which also suffers the same crash problem: You are correct incidentally, it is the gauges that cause the crash.The really simple way to fix it is to use FS Panel Studio to swap out gauges via that program, but, you can do it all manually with a text editor, which is not quite so visual a way to go about it, but will work just the same...Basically, what you do is open up the config file for the panel in a text editor (such as Notepad) and open up FS too, then load up the aircraft on the runway ready to roll. Now, save the flight at that point and leave FS running. Next, alt-tab to the text editor, comment out all gauges with the addition of '//' at the start of a line of text for each gauge and save the changes whilst leaving the text file open. Now, alt-tab back to FS, reset the flight in FS (so the panel reloads) and then take off and you should be able to fly okay as all the gauges are disabled; So, now what you do, is alt-tab back to the text file, and systematically repeat that process by removing the '//' from one line at a time, saving, resetting the flight and checking for an FS crash. When you eventually get an FS crash, the last gauge you enabled will be the guilty party and you will know that is the one you have to swap out. There may be more than one culprit gauge that can cause an FS crash (quite a few are problematic in the 737-200), and it may appear more than once in the panel config file too, because it might be in the VC as well as on the 2D panel, so you have to be fairly methodical in checking stuff, but I reckon a cockpit can be checked in this way in about 30 minutes.Once you've found the guilty party, you can then find a similar gauge from another aircraft which works in FSX and paste the name of that gauge into the line you had to comment out to prevent the crash, over the name of the offending gauge (keep all the placement data, just swap the name of the gauge in the line). This is where FS Panel Studio comes in handy, as it makes that process a bit more visual, but you can do it all via the text file if you like.You will find that having an older aircraft which was made for FSX will be a good source for replacement gauges, and a really good one to use is the CLS B-747-200/300, as it has stack of old-style steam gauges, the King Air B200 is another good source for older gauges. You can simply open up the panel config file for these other aircraft and copy the gauge name, then paste the gauge name into place in your Aerosim panel config file.This is all a lot simpler to do than it sounds when reading it or writing it out by the way, but if you are at all unsure about it, simply make a back up copy of the panel config files and stick it on your desktop, so that you can sort things out if you make a mistake.Al

thanks for your reply. I've done the gauge check, and had to leave out the following gauges:The radioalt gaugeAS_CL2_L10!ALTAAS_CL2_L10!GPWS (since pressing the test button lead to a crash)AS_CL2_L10!radAS_CL2_L10!wdsAS_CL2_L10!AP (unfortunately, now we have to use a different autopilot, I'm using the A300 one by Tomas Ruth)I didn't check the gauges of VCockpit05, just left them out.Anyway merging the Tomas Ruth A300B2 panel(2D) with the Vcockpit of the L1011 I can once again take to the sky with this beautiful aircraft.