I own both the box versions of the Wilco Vol 1 (deluxe) and Vol 2 with the proper patches installed from the wilco site.My issue is upon exit of the sim (and sometimes during) I get a CTD (FS has shut down) with a A332GE_feelThere.GAU, version: 3.3.0.99 error (for example, when using the other busses I get the respective gauge error for each one).This happens on both my W7 64bit and Vista 64bit machines. It never happened on my old 32bit version of XP. They were as stable as a rock.I also own the FT737, ER170/190 ERJ135/145 V2 and have zero issues with those planes in 64bitI know many simmers have zero issues with the busses in 64bit and would love to do a Q&A with anyone here and hope they can share some tips with me to get rid of this annoying problem.Thank you....

No one? :(

I also own them and on my W7 they seem to work fine. Might be related to your system, but I´m not knowing.

There's no solution for it on W7 64. Just make sure you start with the default cessna before selecting the Airbus. It will still crash on exit of FS but that doesn't really matter does it, you were exiting anyway. only other thing to do is to open task manager after the cash and stop the fs9.exe and explorer (second version using the lower amount of RAM) that are still left open.Feelthere have no solutions to this as of course they didn't test on either W7 or a 64bit OS. If some users are not having this issue and are on W7 64 then that consider yourself lucky!

This is why I asked as several people have stated that they have "zero" issues in 64bit and that I was the one with a problem and or a hosed system.I was hoping for some tip as to help my issue.

hello,did you try to install the wilco with "admin rights"You have to right click on your .exe and select "run as administrator" or something so.I have both airbus vol.1 and 2, on W7 64 bits, without problems. but I'm under FSX

Yes, did that. I get the same issue with FSX as well.....

I've had the busses for years. For me they worked fine on XP, then the problem started on Vista & continues on Win7. It's a known bug and there's is no solution to the CTD on exit. I've searched the web & many have this issue.It's annoying, Make sure you at least have ccleaner installed, because the dumps added up eat a lot of disk space. You'll probably notice some other anomalies during flight as well, I don't use them anymore.This is the error you'll see....Problem signature: Problem Event Name: APPCRASH Application Name: fs9.exe Application Version: 9.1.0.40901 Application Timestamp: 4135a208 Fault Module Name: A320CFM_feelThere.GAU Fault Module Version: 3.3.0.23 Fault Module Timestamp: 4674f62c Exception Code: c0000005 Exception Offset: 0049f65a OS Version: 6.0.6000.2.0.0.768.2 Locale ID: 1033 Additional Information 1: c7d2 Additional Information 2: fbb00695700969fbfb5fb844d8ddb8c3 Additional Information 3: 2ff5 Additional Information 4: f02fbb4ef3777e54f65764764f5f34c9

Yup that is what I got.Might have something to do with the reality settings in the load manager people use? Thus explaining why some get the error and others do not?

Yup that is what I got.Might have something to do with the reality settings in the load manager people use? Thus explaining why some get the error and others do not?

I don't think so, the problem has been known for 3 plus years, we would have worked it out by now. I think it's the way the gauge reacts with the new security features that were implemented when Vista came out, the same measures are intact with Win7, BTW it also crashes on 86 systems, so it's not native to 64..... The Boeing's are better anyway.. ;-) People who report no problem may be on hacked windows versions or still on XP. If you ever figure it out thousands want to know.PS I have more than 2 posts, just forgot my pass for reg Handle & used the login via facebook option, works great, I'm also in Canada. Cheers...Rich

Nice to know I am not alone then. I was sure this was pretty common but was told other different in another thread.

The problem of Wilco Airbus is that it leaks under a 64-bit OS (be it in WinXP or Win7). You can watch the meter ticking in the task manager (fs9.exe process) or just leave the plane cold & dark unattended for a while and find fs9 crashes eventually when the system runs out of memory (no matter even if fs9.exe>2Gb header). Tested and registered the phenomenon under both WinXP-64 and Win7-64. Waiting for the newer version of Airbus.Cheers,Dirk.

People who report no problem may be on hacked windows versions or still on XP. If you ever figure it out thousands want to know.Rich

Thanks for calling me someone with an cracked windows version.

Thanks for calling me someone with an cracked windows version.

I do not recall anyone saying "you" had a cracked windows version in particular, but if you have it working please do tell how you found a work around? Your the only one who has spoken up in this thread that has it working in 64bit so I'm glad your here.Are you running the most up to date patches for it? Are you using the box or download version of the bus? Do you have both versions or only one?

I do not recall anyone saying "you" had a cracked windows version, but if you have it working please do tell how you found a work around?

Well, I would tell you if I could, but I can´t. I did nothing, is just works,I can´t tell you why nine are running fine and yours are buggy like hell.I have both volumes boxed and patched up to date, do you have them patched?