David Rogers I believe has discovered a big part in what's causing the CTD issue with the Airsimmer A320. It's not the add-on itself but rather a conflict with another add-on most of us have installed. That's why some of this crap can't be discoverd from just beta testers alone as we all have different things installed. David ran a bare bones install of FS9 with Airsimmer's A320 installed and nothing else. He has not experienced one single instance of a CTD. Many beta team members today are FSX'ers with FS9 installed on the side, that's how things like this can get missed. Unless your a true FS9 user with hundreds of add-ons installed you wouldn't see an issue. It would take a simmer has every meaningful add-on in existence installed in FS9 to catch an incompatibility with another product. This is more of a case or should I say consequence of our split market environment versus a design screwup on Airsimmer's part. It's going to take everyone who bought this add-on to help if they can to find out what the conflict is. This same issue happened with Eaglesoft's new Beechjet and SSTSIM's Concord. There was a SSTSIM gauge file that caused a serious problem with ES's Beechjet. Once this was discovered SSTSIM adjusted their gauge file and the issue was solved. So like everything else, before we jump to a conclusion and blame a whole development team there's has to be an understanding of the environment we live in today with this split market. Some bugs won't rear their ugly heads until the product is put to market. Even knowing the info we know now can you imagine how hard it's going to be to nail down what add-on is in conflict with Airsimmer's A320?So the bottom line is if you have a somewhat bare install of FS9 with few add-ons you won't have a CTD problem with Airsimmer's A320 (also depends on what add-ons you do have installed). I guess this would apply to simmers that are more FSX users than FS9 users.For us hardcore FS9 users there's a common add-on we all have that's not working with this A320, stay tuned....

Les, My rig has both FSX and FS9. My FS9 install has all the bells and whistles, (Ground Environment Pro, Ultimate Terrain, Active Sky Advanced, FS Elemental, World of AI. I bought the Airsimmer A320 because I figured it was a no lose situation. In the next 30 days, if Airsimmer hasn't fixed a number of bugs , I can always get a refund. It's like I rented the plane for a month. That being said, I have not had a single CTD. Yes the aircraft has some flaws and some things I wish they had implimented, but all in all it's not that bad. I'm hoping Airsimmer can get their act together, because this release was a real train wreck.

David Rogers I believe has discovered a big part in what's causing the CTD issue with the Airsimmer A320. It's not the add-on itself but rather a conflict with another add-on most of us have installed. That's why some of this crap can't be discoverd from just beta testers alone as we all have different things installed. David ran a bare bones install of FS9 with Airsimmer's A320 installed and nothing else. He has not experienced one single instance of a CTD.

Dillon, that's an excellent point. As a developer I have multiple FS "environments" that I can choose from for testing:FS9 Virgin (v9.1, no addons at all)FS9 Virgin (v9.1 + FSUIPC + FSSound + GaugeSound)FS9 Full (v9.1, and many, many addons!)FSX Virgin RTMFSX Virgin SP1aFSX Virgin SP2FSX Virgin AccelerationFSX Full AccelerationIt takes a bit of effort to keep everything isolated, but it's the only way I can think of to do proper testing and problem diagnosis of products... ;)

Les, My rig has both FSX and FS9. My FS9 install has all the bells and whistles, (Ground Environment Pro, Ultimate Terrain, Active Sky Advanced, FS Elemental, World of AI. I bought the Airsimmer A320 because I figured it was a no lose situation. In the next 30 days, if Airsimmer hasn't fixed a number of bugs , I can always get a refund. It's like I rented the plane for a month. That being said, I have not had a single CTD. Yes the aircraft has some flaws and some things I wish they had implimented, but all in all it's not that bad. I'm hoping Airsimmer can get their act together, because this release was a real train wreck.

Your right Mike... I just got threw flying a number of flights loading up the default Cessna first and shutting everything off. Loading up the AS A320 from there has given me the ability 100% of the time to fly full routes without a CTD issue...

loading up the default Cessna first and shutting everything off. Loading up the AS A320 from there has given me the ability 100% of the time to fly full routes without a CTD issue...

That's one thing I always do first. Load the default Cessna. That was recommended for a number of addon aircraft.

Your right Mike... I just got threw flying a number of flights loading up the default Cessna first and shutting everything off. Loading up the AS A320 from there has given me the ability 100% of the time to fly full routes without a CTD issue...

For how many years has this been recommended as a "best practice" for properly initializing the FS engine for any advanced aircraft? :( I'm happy to begin reading some positive reports for this release. Although I'm not especially interested in any heavy metal, I do hate seeing any developer getting a "bad rep" for things that are wholly under the user's control... :(

David Rogers I believe has discovered a big part in what's causing the CTD issue with the Airsimmer A320. It's not the add-on itself but rather a conflict with another add-on most of us have installed. That's why some of this crap can't be discoverd from just beta testers alone as we all have different things installed. David ran a bare bones install of FS9 with Airsimmer's A320 installed and nothing else. He has not experienced one single instance of a CTD. Many beta team members today are FSX'ers with FS9 installed on the side, that's how things like this can get missed. Unless your a true FS9 user with hundreds of add-ons installed you wouldn't see an issue. It would take a simmer has every meaningful add-on in existence installed in FS9 to catch an incompatibility with another product. This is more of a case or should I say consequence of our split market environment versus a design screwup on Airsimmer's part. It's going to take everyone who bought this add-on to help if they can to find out what the conflict is. This same issue happened with Eaglesoft's new Beechjet and SSTSIM's Concord. There was a SSTSIM gauge file that caused a serious problem with ES's Beechjet. Once this was discovered SSTSIM adjusted their gauge file and the issue was solved. So like everything else, before we jump to a conclusion and blame a whole development team there's has to be an understanding of the environment we live in today with this split market. Some bugs won't rear their ugly heads until the product is put to market. Even knowing the info we know now can you imagine how hard it's going to be to nail down what add-on is in conflict with Airsimmer's A320?So the bottom line is if you have a somewhat bare install of FS9 with few add-ons you won't have a CTD problem with Airsimmer's A320 (also depends on what add-ons you do have installed). I guess this would apply to simmers that are more FSX users than FS9 users.For us hardcore FS9 users there's a common add-on we all have that's not working with this A320, stay tuned....

What is the add-on you refer to?

For how many years has this been recommended as a "best practice" for properly initializing the FS engine for any advanced aircraft? :( I'm happy to begin reading some positive reports for this release. Although I'm not especially interested in any heavy metal, I do hate seeing any developer getting a "bad rep" for things that are wholly under the user's control... :(

It's even still being recommended in FSX as well!!

What is the add-on you refer to?

That's the million dollar question at this point. Just the same to get around the CTD issue just load up the default Cessna first and shut everything down including the master power switch. Load up the A320 from there and you'll have no issue with CTD's. Everything works as it should for the most part from the autopilot (full ILS approaches) to the basic functions of the MCDU. Now that the CTD issue is a none issue this add-on for the most part is pretty enjoyable... If I'm reading things correctly on Airsimmer's site this add-on is one of those rare models ever created for FS9 that doesn't require FSUIPC to run. That would explain allot as most if not all other add-ons run under FSUIPC. You had to make special concessions with the Wilco bird in FSUIPC for the throttles to work correctly. With this bird you don't which surprised me when I first loaded it up. With FSUIPC running in the background I could understand how in a weird way that would cause a conflict with this bird. This is not confirmed but just the same you can get around the CTD issue by first doing what I stated above. The Airbus was a hard bird to bring to FS9 that's why so many developers didn't bother. This add-on in order to model FBW and the throttle correctly had the developers drop the use of FSUIPC and go another route. This all makes since why there would be a conflict with everything else we own.

I can understand an addon causing a ctd, but what is very peculiar to me is that there are ctd's for various issues and at different times. For example: Today i was flying from KLAS-KATL @ FL350. I hadn't touched the computer in 45 minutes. I glanced up and it had crashed. I wasn't pushing a button, or shooting an approach. It was just sitting there in straight and level flight. Now I could see if everybody was getting a ctd at a certain part of the flight, or if it happened by pushing a particular button. They are just so random.BTW, I do load up the default Cessna and shut it down prior to loading the bus

Hi all,A full day of flying the AS A320 and absolutely no CTDs or any other type of hang or crash. As Les said, I believe the 'virgin FS9 install' is the primary reason I am seeing no issues. I have now tested all liveries and also the IAE models and again no crashes. I have started every flight by first loading the default C172, and setting her to dark and cold; Battery off, magnetos (key) off, mixture control IN. Even though the battery is OFF, keep the Avionics switch ON, or it could cause an issue with avionics in the A320. (Unlikely but safe).On Autopilot issues also, spme people may recall that when the feelThere 737PIC was first released for FS9, it also did not use FSUIPC and it suffered eratic AP behaviour for users that had the current verison of FSUIPC, and as I recollect, especially users of 'registered FSUIPC', who had many configuration options set up in FSUIPC.The workaround was to temporarily remove FSUIPC.DLL from the FS9 Modules folder. This completely resolved the issue (at the loss of being able to enjoy other FSUIPC features).Subsequently, either an update to FSUIPC or to the 737PIC itself (can't recall which) resolved the issue without the need to remove FSUIPC when using the 737.So...... although I am a huge FSUIPC fan and use it thoroughly in FSX, again my fresh FS9 install does not have FSUIPC, neither unregistered or registered versions. And thus, I have not experienced a single AP issue - no disconnects, no wobble in cruise, no eratic vertical speed changes. The AP is rock solid for me, in fact it grips the LOC and GS better than most planes in FS9. :)Don't get me wrong, there are a couple of bugs in the AS A320, but the only ones I can recall are :-- Flaps assigned to an joystick axis aren't working for me. But flap comands assigned to a key press (ie 'flaps extend incrementally') work fine.- Flight Director does not command a roll indication when HDG mode is used for take-off (but it does when HDG is selected once in the air).- There is a sound 'interuption' during the engine start up phase.That's it for me, no other bugs experienced. I hope Airsimmer release a SP that adds a couple of things like FLEX functionality for take-off, and INIT2, but I have to say, I am really enjoying this bird, even as she is....

I have FSUIPC installed and never have to remove it to fly this add-on. I also wouldn't recommend doing so as things like Active Sky is tied to it. Like I said loading up the Cessna and choosing your flight plan in FS9 is the way to go. Once at the gate with the Cessna cold and dark load up the A320 and it's smooth sailing from there...Concerning the Autopilot I concur it's rock solid on my end as well. It follows the FMC flight plan, it's stable at altitude, and captures the ILS without issue...

FSUIPC is a vital part of the FS9 and many add-ons rely on it. This is the first time I'm hearing that an add-on is not compatible with the fsuipc.

On a slightly different note, has anyone figured out how to adjust the horizontal stabs so that they aren't pointed upward? Adjusting trim does nothing to alleviate it either on the ground or in flight... that's abot the only flaw I have seen in the VISUAL model... - Alex

FSUIPC is a vital part of the FS9 and many add-ons rely on it. This is the first time I'm hearing that an add-on is not compatible with the fsuipc.

I wouldn't say 'not compatible' but rather designed independent of it. The A320 doesn't need FSUIPC to run but just the same so many of our add-ons in FS9 are dependent upon FSUIPC that a potential conflict has arisen somewhere...

On a slightly different note, has anyone figured out how to adjust the horizontal stabs so that they aren't pointed upward? Adjusting trim does nothing to alleviate it either on the ground or in flight... that's abot the only flaw I have seen in the VISUAL model... - Alex

That's something to report as it needs to get fixed. I noticed the same thing myself and if you look at the trim tape in the VC (in flight) it's off. It's not a show stopper that affects flight though...