SeanBH

You mean there are others out there????!!! lol! B)

Hi All: Bryan...absolutely fantastic product...thank you very much for all your work on this. So many features and changes! My NGX has been hangared since you announced you were doing this, and after using the 777 since then, have really come to enjoy the voice product for it. So far, I've only used SOP1, but will be getting to SOP2 later today! If there was one thing I'd like to see, though, that is available in the 777 version, is the ability to use voice to direct the FO to change speed, heading, and altitudes in the MCP whilst on the ground. I realize the fact that the PF is the only one that should change the MCP, but after having that feature in the 777, I've come to miss it in Reboot! Again, thank you for a great product! Sean

Very nice! Thanks Mark!

Hey Jim! Thanks for the info...I have run the cleaner program, and AMDA00 still won't go away. I only get the error once after booting, so it appears that error is just a boot timing/driver load issue. But it's one of the few remaining errors I'd like to get rid of! Just for kicks, I tried downloading the Cleaner again, and I don't know what's different than before, but now my Norton 360 desparately HATES that file....it's deleted it twice. Malwarebytes didn't have any problem with a single scan, but N360 won't let me do anything with it. I think I'll try to look some more for problems with this.....thanks again! Sean

I upgraded my system with a i7-4770K CPU and Asus Maximus VI Formula MOBO on Dec 14th, and am finally getting to the final stages of resolving the last of the Event errors plaguing my system. When I re-installed Win8Pro64, I used the MOBO disk to load all the ancillary drivers and such, and happened to also load AI Suite III, which was a total mistake that I didn't remember that from my earlier days. I have run the Asus AISuite3 uninstaller, but can't seen to get one last crumb gone: the AMDA00 interface. With little to go on Google-wise, I see that it is related to AISuite3, and some comments simply advise to delete it. But it's the proverbial boomerang- it just installs itself again, then generates Event Viewer messages that WUDFRd can't load the driver.. I suspect from the lack of web content that this is a fairly new issue, although I did find some references to AISuite2. Trying to use Asus' Forum to interact is just a horrible waste of time- I can't even get the website to let me type a post. I love their products, but their website skills are completely left to be desired. Has anyone run into this? How did you fix [trash] it? Thanks! Sean

Nice tip! How in the heck did you find this out? I 've looked at FSUIPC's screens for years thinking they might have well been written in Greek. ^_^ Any way to check CPU/MB temps with any other values?! Anything else? Thanks!

I have had this problem as well, and was thinking this was going to be one of those "OMG- will I ever find the answer"-kinda issues. What was strange is that I could mouse around in my other screens where I place displays such as the PFD and HSI, but not my main screen where the VC was. I could even "A" over to the FO view and others, and the mouse was controlling just fine there. Found it was the viewpoint being too far back- by merely resetting it (I have a joystick button dedicated to that), my mouse recovered control. There is a specific distance back that control will disappear, and you don't have to be in back of the headrest to have the issue.

Wow...didn't know that either....switching to PMDG to set that! Schwweeeeet!

As "telling" as this summation might be, I (and I'm betting many others) will have a hard time with the NGX on that list, and will agree that a percentage of total owners, as you suggested, might be a better indicator. Everywhere I've read about it it's been the most beloved and most accurate of all sim objects. Perhaps its own complexity is the reason for this, given the variety of simmers' experience and knowledge out there? For me, it was a great learning curve, but I welcomed it and it's the only plane I fly now.

Another vote for: PMDG 737NGX FS2Crew 737NGX Then also... GSX REX Essential Plus and last, but not least, Pete and his legendary FSUIPC.

After seeing a post suggesting that logbooks can be corrupted, I looked at my current one and found that my copying over my old one didn't take when I fully reinstalled my system to upgrade to Windows 8. Googling "merging FSX logbooks" did not yield any discernible results. I had over 3200 hours in my old one since 2008, and I'm up to almost 100 hours in my new one. Is there any way to merge them into one file? Thanks!

Jim: Come to think about it, I did have similar issues when I installed my new SSD in my Sabertooth Z77 system. Getting the proper boot order in the BIOS was a bit contentious. I wish I could tell you how I resolved it, but that was a few brain cells ago! :-) And in the vein of "if it ain't broke don't fix it" theme, things have been running great so far, so if you don't mind, I'm gonna leave my FSX as Win7 Compatible. :rolleyes: Any more luck last night? You were up way past your bedtime!!! :-)

Bryan: I can't thank you enough for responding and rectifying this issue as quickly as you have. It speaks volumes to the integrity of yourself and the FS2Crew organization. This is the type of SUPPORT that I spoke of earlier in another thread, and at least to me, is a major factor in determining if a product is worthy of a purchase. This action now leaves no doubt as to the customer commitment that FS2Crew has to their customers. THANK YOU!

UPDATE!!!! In the same fashion that we've come to expect with great products from FS2Crew, they have confirmed their integrity with a VERY quick resolution to my issue, and it is exemplary! My hat goes off to Bryan and the FS2Crew for clarifying on the product page that the MD-11 version is button only- seemingly within minutes of our conversation. This is all I asked for the sake of those reading this and other threads pertaining to the MD-11 product. I can't thank FS2Crew enough for taking appropriate action on this issue. Thanks to all of you for your contribution to this point.

absolutely Pete...it's a marketing issue that can easily be solved IMHO.