September 10, 201213 yr I have FS9 on Win7/64 and I get a CTD below every time I close it Faulting application name: fs9.exe, version: 9.1.0.40901, time stamp: 0x4135a208 Faulting module name: A320IAE_feelThere.GAU, version: 3.3.0.99, time stamp: 0x494bf768 Exception code: 0xc0000005 I understand that there is nothing that can be done about this, however it started happening in flight, particularly when I land and turn off and exit the runway and I perform multiple tasks, (ie. flaps up, speed brakes down/disarm, contact ground), this is more of a nuisance. I am currently not running in comparability mode but I am running as admin. Does anyone have any insight on what steps I can possibly take to avoid a CTD while in flight?
September 13, 201213 yr Get an aircraft from another company. Seriously. I am sorry and not trying to be a smart mouth but I have never had one aircraft from then that didn't have unsolvable issues. Sent from my iPhone using Tapatalk William Sequeira
September 16, 201213 yr Author Hahaha :-) I really like the these aircraft, what are some similar packages which would work better on FS9?
December 6, 201213 yr Hi I have the evo versions of the Airbus , i havnt had a CTD during flight but i get one 80% of the time after i exit the sim , kind of have to get used to it . Its a shame they dont wanna look into this as maybe its a simple fix . Rich
May 3, 201412 yr Hello, I know this is not a too recent post, but anyway i'll post here one of the things to try out in case that it is 100% certain that there is a Feelthere Gauge causing a CTD... (It can also be a bad format texture, in this case find "dxt3fixer" or "dxtfixer" and let it run on the Feelthere folder where the suspected texture/repaint is, but if you feel this might be a Feelthere Gauge CTD, please continue reading:) Have a look in: ...\Flight Simulator 9\FeelThere\Airbus\FMGC and then into the folder of the Airbus you where recently flying. (A320 / A330 or A340) Every one of these folders contains a "fmgc.cfg" file that basically holds all the MCDU/FMC info, and normally, after a flight, it gets "empty" automatically. (not completely though, as your about to find out...) If this "fmgc.cfg" file is around 7-8 kilobyte (and not like around 400/500 bytes only as this should be) than this "emptying process" went corrupt at shutting down the Airbus after a flight. This can also occur in midflight, taxiing or even taking off... what matters is that the information in the start-up of the Aircraft, and thus also the MCDU/FMC, corrupts with what is inside the "fmgc.cfg" file. What is the solution as to fight this issue? (I take no responsiblities, this worked for me, it MIGHT work for you...) To reset this information! First make sure that your FS2004/FS9 is closed and not running in Windows Task Manager, as this could give File Access errors. Now follow very precisely everything i write down below: Open the culprit "fmgc.cfg" file with Notepad, (rightclick, Open with...) delete any text or info written inside this file, and insert following info: (This is my personal info from my FS9, but at least it gets you to open and fly the Wilco Airbus again, after you can modify this via the FMC/MCDU and by going into the Wilco Airbus Configurator and planning a new flight from scratch) For the Airbus A320 "fmgc.cfg" file: [MCDU]CoRte=FlightNumber=IBE9000[FMGC]FlightPhase=1FMSFlightPhase=1IRSAlignment=0DeltaLat=0.000000DeltaLon=0.000000ZFWCG=25.00ReductionAltitude=3498ReductionAltitudeGenerated=1AccelerationAltitude=3498AccelerationAltitudeGenerated=1TransitionAltitude=18000TransitionAltitudeGenerated=1[Flight Plan]AIRAC-Cycle=1404NumberOfWaypoints=0NextWaypoint=0DepartureIndex=0ArrivalIndex=0 For the Airbus A330 "fmgc.cfg" file: [MCDU]CoRte=FlightNumber=TAM8012[FMGC]FlightPhase=10FMSFlightPhase=8IRSAlignment=0DeltaLat=0.000000DeltaLon=0.000000ZFWCG=25.00ReductionAltitude=1528ReductionAltitudeGenerated=1AccelerationAltitude=1528AccelerationAltitudeGenerated=1TransitionAltitude=18000TransitionAltitudeGenerated=1[Flight Plan]AIRAC-Cycle=1404NumberOfWaypoints=0NextWaypoint=0DepartureIndex=0ArrivalIndex=0 For the Airbus A340 "fmgc.cfg" file: [MCDU]CoRte=FlightNumber=AFR3510[FMGC]FlightPhase=10FMSFlightPhase=8IRSAlignment=0DeltaLat=0.000000DeltaLon=0.000000ZFWCG=25.00ReductionAltitude=1892ReductionAltitudeGenerated=1AccelerationAltitude=1892AccelerationAltitudeGenerated=1TransitionAltitude=18000TransitionAltitudeGenerated=1[Flight Plan]AIRAC-Cycle=1404NumberOfWaypoints=0NextWaypoint=0DepartureIndex=0ArrivalIndex=0 You'll see that once you save this file again as a "fmgc.cfg" file, the size will be around the mentioned 400/500 bytes only, and you can safely close the folders, once everything is edited. Now open up again your FS2004/FS9 and try it out... It should work as good as possible! Just like before... As i know, this has been one of the most famous CTD from the Wilco Airbus family, and not even after the Evolution version this was solved. Note, this is a DIY Workaround, not an official fix. This type of CTD occured to me a couple of times, and i always keep a backup of the "Flight Simulator 9\FeelThere\Airbus\FMGC" folder, so in case this happens, i can copy over the faulty "fmgc.cfg" file. Enjoy your flights, and please do let know of this was usefull to anyone out there... Sure i'm not the only one with trouble with Wilco Airbus.... Greetings, Diego.
