pedrornunes96 Posted May 5, 2016 Share Posted May 5, 2016 Good afternoon everyone! I'm sorry to be very straight to point... In the past few days I've tried to port my Aerosim Boeing 737-200 and 747 Classics from FS9 to FSX, and in the beginning (A/C taxi, take-off and climbout) everything works as a charm. However, after a few minutes, FSX gets a CTD fatal error and everything is lost. I'm really getting frustrated for this has happened every single time I jump into and fly the AS 747. I am aware that this is an "FS9 only" addon (http://www.avsim.com/pages/0609/Aerosim/CL1.htm), but I would like to get this airplane to work in FSX, as it is one of few 747 classics that I can run smoothly in my machine that has an integrated 3D cockpit. I've already searched other threads here and I found a few useful, but I've run out of options :confused:: https://www.flightsim.com/vbfs/showthread.php?155413-Classic-Liners! https://www.flightsim.com/vbfs/showthread.php?227304-Aerosim-s-L-1011-for-FS2004-Does-it-work-in-FSX With this thread I post my error details. All of the previous reports are also related to the file "AS_CL1_B42.GAU", so I assume it's a gauge's problem: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: AS_CL1_B42.GAU, version: 1.0.0.1, time stamp: 0x439bdcea Exception code: 0xc0000005 Fault offset: 0x0000dec3 Faulting process id: 0x17e4 Faulting application start time: 0x01d1a6bfea52b846 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\AS_CL1_B42.GAU Report Id: 89904427-12b6-11e6-99a1-00269ea6593c My computer specs: x64-bit MSWin7 Home Premium; Intel Core 2 Duo CPU T6600 @ 2.20GHz,2200MHz,2 cores,2 logic processors; NVIDIA GeForce G 103M version 9.18.13.4052 Link to comment Share on other sites More sharing options...
mrzippy Posted May 5, 2016 Share Posted May 5, 2016 Have you tried looking for that particular gauge in the panel.cfg and adding // in front of it so the Sim will not try to use it? Still thinking about a new flightsim only computer! Link to comment Share on other sites More sharing options...
pedrornunes96 Posted May 5, 2016 Author Share Posted May 5, 2016 Have you tried looking for that particular gauge in the panel.cfg and adding // in front of it so the Sim will not try to use it? Problem is, every single line in the panel uses the same gauge file... too bad ***The following is just for the window00:*** [Window00] file_1024=AS_B42_MAIN_P2.bmp size_mm=1024,768 window_size_ratio=1.0 position=1 visible=1 ident=MAIN_PANEL gauge00=AS_CL1_B42!ASI, 26, 509, 101 gauge01=AS_CL1_B42!RMI, 43, 630, 83 gauge02=AS_CL1_B42!ADI, 137, 487, 134 gauge03=AS_CL1_B42!HSI, 140, 635, 128 gauge04=AS_CL1_B42!GPS, 301, 351 gauge05=AS_CL1_B42!FMA, 272, 419 gauge06=AS_CL1_B42!RALT, 369, 508,76 gauge07=AS_CL1_B42!VS, 281, 597, 76 gauge08=AS_CL1_B42!Cs, 468, 684, 76 gauge09=AS_CL1_B42!NAV1, 389, 351 gauge10=AS_CL1_B42!SATT, 467, 474, 83 gauge11=AS_CL1_B42!AP, 517, 328 gauge12=AS_CL1_B42!GPWS2, 569, 428 gauge13=AS_CL1_B42!GPWS, 864, 430 gauge14=AS_CL1_B42!REV1, 570, 460 gauge15=AS_CL1_B42!EPRb,558, 487 gauge16=AS_CL1_B42!N1B, 650, 487 gauge17=AS_CL1_B42!N2B, 700, 487 gauge18=AS_CL1_B42!REV2, 641, 460 gauge19=AS_CL1_B42!EGTB, 750, 487 gauge20=AS_CL1_B42!FFB, 800, 487 gauge21=AS_CL1_B42!ANN1, 558, 690 gauge22=AS_CL1_B42!ANN2, 736, 687 gauge23=AS_CL1_B42!REV3, 711, 460 gauge24=AS_CL1_B42!REV4, 781, 460 gauge25=AS_CL1_B42!TAT, 861, 467,56 gauge26=AS_CL1_B42!FLAP1, 854, 536, 63 gauge27=AS_CL1_B42!FLAP2, 854, 610, 63 gauge28=AS_CL1_B42!REM, 852, 679 gauge29=AS_CL1_B42!GIND, 946, 458 gauge30=AS_CL1_B42!GEAR, 932, 500 gauge41=AS_CL1_B42!CDUB, 456, 454, 23, 23 gauge42=SimIcons!ATC Icon, 456, 576, 23, 23 gauge43=SimIcons!GPS Icon, 510, 576, 23, 23 gauge44=SimIcons!Map Icon, 483, 576, 23, 23 gauge45=SimIcons!Avionics Icon, 483, 454, 23, 23 gauge46=SimIcons!ECU Icon, 537, 576 , 23, 23 gauge47=AS_CL1_B42!OHB, 537, 454, 23, 23 gauge48=AS_CL1_B42!FUELB, 510, 454, 23, 23 gauge39=Magnetic_Compass!Magnetic-Compass, 815, -17, 80 gauge40=737-400!OMI Lights, 418, 433, 26 gauge41=AS_CL1_B42!APVS, 854, 328 gauge42=AS_CL1_B42!trs, 188, 608 gauge43=AS_CL1_B42!ALT, 281, 508, 77 gauge44=AS_CL1_B42!ALTA, 288, 490,34 gauge45=AS_CL1_B42!ADF, 365, 595,81 gauge46=AS_CL1_B42!CLK, 365, 678, 88 gauge47=AS_CL1_B42!TAS, 861, 704,56 gauge48=737-400!Pitch Trim, 1, 672, 30 gauge49=AS_CL1_B42!FMAT, 372, 433 gauge50=AS_CL1_B42!SAT, 677, 703,55 gauge51=CALLOUT_SOUND!dsd_xml_sound3, 0,0,0,0, Sound\CALLOUT\Sound.ini gauge52=CALLOUT_BigJets!CALLOUT2500, 0,0,0,0 gauge53=CALLOUT_BigJets!CALLOUT1000, 0,0,0,0 gauge54=CALLOUT_BigJets!CALLOUT500, 0,0,0,0 gauge55=CALLOUT_BigJets!CALLOUT100, 0,0,0,0 gauge56=CALLOUT_BigJets!CALLOUT50, 0,0,0,0 gauge57=CALLOUT_BigJets!CALLOUT40, 0,0,0,0 gauge58=CALLOUT_BigJets!CALLOUT30, 0,0,0,0 gauge59=CALLOUT_BigJets!CALLOUT20, 0,0,0,0 gauge60=CALLOUT_BigJets!CALLOUT10, 0,0,0,0 gauge61=CALLOUT_BigJets!CALLOUTAPPMIN, 0,0,0,0 gauge62=CALLOUT_BigJets!CALLOUTMIN, 0,0,0,0 gauge72=../civa/INS!Config, 0, 0, 0, 0, AS_B747200B_CL gauge73=../civa/INS!NavModeTriple, 126, 437, 78, 47 gauge74=../civa/INS!MsuPanelIcon, 201, 412, 20, 20, 40 gauge75=../civa/INS!CduPanelIcon, 177, 412, 20, 20, 41 gauge76=../civa/INS!AdeuPanelIcon, 225, 412, 20, 20, 42 gauge77=../civa/INS!UpdateFlags, 65, 464, 55, 30 Link to comment Share on other sites More sharing options...
mrzippy Posted May 5, 2016 Share Posted May 5, 2016 Yep, I agree that it will be tough finding the one causing the CTD! Any of the display gauges can be easily eliminated because they work on the ground and during takeoff and climb out. Things that might happen after climb out like engaging AP/AT, GPWS, etc. might be the ones to look at. Still thinking about a new flightsim only computer! Link to comment Share on other sites More sharing options...
pedrornunes96 Posted May 6, 2016 Author Share Posted May 6, 2016 Yep, I agree that it will be tough finding the one causing the CTD! Any of the display gauges can be easily eliminated because they work on the ground and during takeoff and climb out. Things that might happen after climb out like engaging AP/AT, GPWS, etc. might be the ones to look at. Indeed... and wow, I've only thought of the gauge files as a whole, you are right, there can be just one out of many causing the CTD. In that case I'll put "//" in every (or most) lines of the panel.cfg and then reactivate them, one by one. I hope the problem is not related with the entire gauge file... This will be a tricky one :p Anyways, thanks for the help, when reaching a conclusion I'll post here. Link to comment Share on other sites More sharing options...
pedrornunes96 Posted May 7, 2016 Author Share Posted May 7, 2016 Hi MrZippy! After some deliberation I find myself to reach the conclusion that the FSX CTD I was experiencing was caused by myself :p After flying around with the 747 I noticed how many times the GPWS was annoyingly saying "don't sink" or "too low terrain", so I renamed the sound files related to the GPWS gauges in the hope of disabling them. However this proved to be not true, and instead of disabling the GPWS I disabled the entire simulation XD So I followed your advice and I found the GPWS to be the culprit. I have since yesterday removed the lines: gauge12=AS_CL1_B42!GPWS2, 569, 428 gauge13=AS_CL1_B42!GPWS, 864, 430 ...and everything is working just fine now. Thank you again, and have a nice weekend :pilot: Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.