January 4, 201313 yr Oh my God, Bryan, I never thought I would meet it again! After my first flight (about 50 minutes duration) after quite a long time, again the crash as soon as I shut down the engines and the FO set the wheel chocks! I am speechless... :( James Goggi
January 5, 201313 yr Commercial Member Well, no one else has reported that in ages. Maybe it's just a one off thing. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
January 13, 201313 yr I've been having this same issue across many fs2crew versions, but never bothered to report it, because 1) was not sure it was in fact fs2crew related and 2)small problem as it did not ruin the actual flying. I run NGX latest SP on FSX Gold SP 2. Win 7 64 bit. Ezdok, fsinn and ivap networked to 2nd pc along with SAS VA flight recording softwarw on networked pc also. ASE 2012 networked along with track IR, ENB series, Shader for FSX and a tonnes of addon sceneries, UTX Europe, Ground environment prof, fs global ultimate europe and africa. Fs2crew is voice edition. Mas Martin Jensen
January 14, 201313 yr Commercial Member Hi Mas, Try moving your sliders a little to the left and turn down your LOD a bit. You're pushing your system very hard. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
January 14, 201313 yr Hi byork - thx for your suggestion, but i have infact updated my hardware. Im now running 8 gb ram and have installed the new 660ti gpu. I'm seeing good fps all over. Can't determine fs2crew to be the issue, but I suspect the va software to cause unwanted probs actually... Mas Martin Jensen
January 15, 201313 yr I am having the same issue crashing PC after running preflight? ill try and uninstall and see how i go. I have not used FS2 crew since re doing my pc and have no crashes in the past now i start FS2 Crew and 15 min in bang crash pc reboots. not overclocked either. Wayne. http://fs2crew.com/banners/Banner_FS2Crew_MJC_Supporter.png Wayne HART
January 15, 201313 yr Commercial Member Well, not to pass the buck, but FS2Crew NGX has a huge number of users. Crashes are reported very, very rarely, and they're usually the result of people setting their sliders too far right when running memory hog 3rd party scenery. FS2Crew's memory footprint is very small, since FS2Crew hardly uses any graphics save for a few simple panels. My advice to anyone getting a crash is to check the CTD forum in Avsim. There are numerous tips, fixes and suggestions to help minimize crashing in FSX, such as running ******* Bejote's FSX.cfg utility. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
January 15, 201313 yr Commercial Member It may be helpful to look at the NT events for the CTD, there should be an entry for the CTD and in what .dll or .exe it came from. Steve Waite: Engineer at codelegend.com
January 15, 201313 yr Commercial Member Yes, "Event Viewer" can give you more info. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
January 18, 201313 yr I get the occasional CTD when using this FSCrew program Always a BEX app crash which through research is when FSX goes to look for something, does not find it and crashes. This crash is always always right after I tell the F/O to do something. I did a flight just now and got this CTD after a while of not getting any. This was just after saying, "after t/o checklist". The last time was just right after saying, "set heading to 180". This was flying out of a default airport as well. An no, my system is not running sliders to far to the right. I can go into any and all 3rd party scenery with the NGX at current slider position without issues. Eric
January 19, 201313 yr Commercial Member Hi Eric, Please make sure you have the "UIAutomation.dll" fix installed. It'll help. As for your BEX error, I've never seen that one. Please google "FSX BEX"... there's a lot of discussion about possible causes and solutions in the various forums. Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
January 19, 201313 yr I have the uiautomation.dll fix applied. It's been applied for years. I know this has to do with your software whether you acknowledge that fact or not. In fact I find it troubling that users come in here saying they get ctd's whilst using your software yet you never seem to believe it's your issue to deal with and that there is no way it could be faulty code. I see that with some frequency in various posts you blame users computers or setups and thats the end of the topic as far as your concerned. You show zero desire to want to help users trouble shoot what is going on or investigate it further with your beta team. Sent from my Samsung Galaxy Note 2 Eric
January 19, 201313 yr Mine was a motherboard issue I think just reinstalled everything took 2 and a 1/2 days new board looking ok so far Bryan will report back. http://fs2crew.com/banners/Banner_FS2Crew_MJC_Supporter.png Wayne HART
January 19, 201313 yr Commercial Member Glad you you appear to have it sorted. I do my best to help customers... I do a lot of Remote Desktops to help people... but sometimes I just have to throw the ball back into the user's court. 9 times out of 10 they're able to resolve the issue on their own. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
Create an account or sign in to comment