02-16-2012, 06:27 PM
My experience with FSX and that same crash, with all the fixes mentioned already, if I use the menu bar, or even right click to bring up a menu too many times, bam, CTD. :evil: :evil:
Resolution: EZDok... http://www.flight1.com/products.asp?product=ezdockcam and a nice gaming pad I had. Problem solved!!
I start my flight and only use the menu to start FSInn and FSPassengers, then I hide the menu. I have set up my EZDok for all my views needed, plus have my QT lower buttons set for outside views too. No more crashes. Point here is to stay away from the menu as much as possible. Even with the UIAutomationcore.dll fix, I was still recieveing the CTD at differnts intervels of menu usage.
Good luck and hope this was helpful to you. With EZDok, you don't need a game pad, you can use your keyboard and set it up as you like, I just find the the game pad made it more comfortable for my setup and very easy and quick to navigate the cockpit.
P.S. Sorry, should of asked, are you clicking on the menu or right clicking for the drop down menu prior to your crash????
:mrgreen:
Resolution: EZDok... http://www.flight1.com/products.asp?product=ezdockcam and a nice gaming pad I had. Problem solved!!
I start my flight and only use the menu to start FSInn and FSPassengers, then I hide the menu. I have set up my EZDok for all my views needed, plus have my QT lower buttons set for outside views too. No more crashes. Point here is to stay away from the menu as much as possible. Even with the UIAutomationcore.dll fix, I was still recieveing the CTD at differnts intervels of menu usage.
Good luck and hope this was helpful to you. With EZDok, you don't need a game pad, you can use your keyboard and set it up as you like, I just find the the game pad made it more comfortable for my setup and very easy and quick to navigate the cockpit.
P.S. Sorry, should of asked, are you clicking on the menu or right clicking for the drop down menu prior to your crash????
:mrgreen: