Sign in to follow this  
Guest mau01

Acceleration crashes upon accessing menu bar

Recommended Posts

I started a tread earlier about this very problem.The only other who has came forward has a 7900gt. I have a 7900gtx.I gave up trying to solve it and just use the keyboard to open the menus.So far, its totally random when the sim freezes.This has never happended to me before deceleration. Ahh acceleration.I am pretty conditioned to having problems with computer games and expect it.I just cannot remember having a mouse command trigering a hard crash before.Hopefully someone will stumble apon our post and have a answer.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I think I'm the other guy that JimJam was talking about. I also have a 7900 series card, and like you, I have the lockups.From a lot of trial and error, I figured out a solution that seems to work around the issue. Before accessing a menu, first pause FSX, then access the menus via the keyboard. Alternatively, you can bring FSX into windowed mode (assuming you run full screen normally), and then access the menus, which also seems to prevent the lockups.From what I've seen here, it looks like there is some kind of incompatibility issue with the Nvidia 7900 family and Acceleration which switching drivers around doesn't seem to solve, so hopefully either MS or Nvidia will issue some kind of fix at some point.

Share this post


Link to post
Share on other sites

7600GT and I have it too. Also can crash if I just hit ";" to save.But the pause workaround worked.

Share this post


Link to post
Share on other sites

It would help when posting about problems if you would state whatoperating system you are using...XP or Vista...and which flavor.... Paul

Share this post


Link to post
Share on other sites

I apologize for not seeing the earlier post on this problem. Apart from having cluttered up the forum, had I done so I'd have saved myself the entire day and 4 uninstalls and reinstalls trying to isolate the problem. I'd been watching the forum for insights before installing Acceleration and just missed it. I really appreciate your all taking the time to repeat your findings.The 2 workarounds mentioned indeed work for me. I can either use key commands to navigate the menus or shift into windowed mode. It would really be great if someone with this problem had an extra video card around that isn't a 7900 series and could swap it in to see if that eliminated the problem. If not, then we've got to look elsewhere.In response to Paul, I'm running XP Home SP2.Thanks again for all the input.Robert

Share this post


Link to post
Share on other sites

XP Home SP2 here.I was on final from a short 125m ifr flight when I switch from the vr pit to the 2d. LLLLLOOOOCK UP.......Now Im mad. Menus I got around but now I can have at any moment a total freeze.So from something that worked to something that does not.And the guys who paid through the a** for the latest greatest dx10 hardware got something that 1/2 way works.If I can finish most of the missions and do a few carrier landings, Im afaid Acceleration is on its way to the recycle bin.Looking forward to FS11 already.

Share this post


Link to post
Share on other sites

I just posted about this in the CTD forum. Sorry I hadn't seen this thread.I am running 7800GT with new drivers on AMD 64X2 4200 Win.XP SP2.Never had a CTD until install of Acceleration.Run in full screen, access menu using Alt. key, CTD.

Share this post


Link to post
Share on other sites

I'm having the same CTDs. I just uninstalled acceleration until Aces or Nvida can come up with a fix. I'm runnug XP sp2 on a 7950GX2.Ray

Share this post


Link to post
Share on other sites

Just had another CTD. This time while flying the FA18, opened the GPS window using Shift-3 and entered a Direct flight to KEYW. As soon as I clicked the mouse button to enter and activate, CTD.Sure would like to see a fix for these problems posthaste. Hate to see such a good add-on failing like this.Looks like it has something to do with opening other windows and using the mouse in them.

Share this post


Link to post
Share on other sites

Keeping this thread alive.Anybody have any success or at least figure out whats causing our CTD and lock ups on what appears to be 7 series nvidia cards cards?7900gtx logitech mouse/keyboardasus mob 2 gigs hyperx AMD fx-62 dual coreIm still getting lock ups when I access the menu in flight.Ive also locked up when shift number to open panels.

Share this post


Link to post
Share on other sites

As I said above:"It would really be great if someone with this problem had an extra video card around that isn't a 7900 series and could swap it in to see if that eliminated the problem. If not, then we've got to look elsewhere."Additionally, I and many others are also reporting no daytime panel lights in most of the default planes. This may also be a 7900 series problem and it would be nice to know if there's a common cause here as well.Robert

Share this post


Link to post
Share on other sites

Hi All Just thought i register to let you guys know that im running an 8800GTS 640mb(in DX9 on a core duo2 6800E 2gig ram XP home) and that ive been through about 5 different driver sets trying to cure this mouse menu access problem & nothing works i even went back to the sets they dev'ed on (pre 16x.xx)to see if that would fix it and it does'nt.....btw before someone ask's yes cleaned using driver cleaner in safe mode and then deleted the nvidia FSX profile and remade for each test i also tryed letting fsx rebuild its config file for each set i tested..While trying to find a fix for this issue i came across a post over at simviation that i'll copy and paste here ------------------------------------------------------------------------posted by macca22auBut at the Australian flightsim convention today I heard that there was an sp2a to come as SP2 has in someway affected the functionality of the menu system in FSX.------------------------------------------------------------------------We are not alone in having this problem ive seen many posts about it over ever major and minor FS forum....i wonder how this one(and a whole host of other problems)slipped past the beta testers? maybe they were all to busy posting screenshots and feeding the hype machine...I might have missed it but it would be nice if Aces could confirm that they know about this problem and (if its not a driver problem)will they let us know what they attend to do about it? will they hot fix it or will they make us wait till the free Sp2 download goes live?

Share this post


Link to post
Share on other sites

Gizmo, thanks a lot for reporting your findings, as well as the extent of your investigation. This sure broadens the possible sources of the problem. I too wonder how the beta testing missed this one. I can only conclude that the problem must be a confluence of several factors, only one of which now appears to be an nVidia card.Robert

Share this post


Link to post
Share on other sites

Yeah Im getting a little tired of all the time spent on eye candy and gee wizzz look at that.Moving shadows,wet runways,a coat of shine on everything means nothing to me.Being able to run reasonable settings,get a nice looking picture and actually being able to FLY from point A to B without wondering if I will be able to make it without the computer freezing.Now thats a add on worth buying.PS- Not angry and Im glad Aces are looking into the problem. Its just after a year I still have FS9 loaded, still occasionally buying add ons for it and fly it 50% of the time.Time to quit screwing with FSX, write it off and start working on fs11.

Share this post


Link to post
Share on other sites

>Gizmo, thanks a lot for reporting your findings, as well as>the extent of your investigation. This sure broadens the>possible sources of the problem. I too wonder how the beta>testing missed this one. I can only conclude that the problem>must be a confluence of several factors, only one of which now>appears to be an nVidia card.Why is there always the "assumption" that something slipped past the beta testers?Beta testers report problems. The developers (ACES) either fix them or not. That's their call.After the beta cycle (however many there are) is completed, beta testers don't see the final results until everyone else does...

Share this post


Link to post
Share on other sites

>>Gizmo, thanks a lot for reporting your findings, as well as>>the extent of your investigation. This sure broadens the>>possible sources of the problem. I too wonder how the beta>>testing missed this one. I can only conclude that the>problem>>must be a confluence of several factors, only one of which>now>>appears to be an nVidia card.>>Why is there always the "assumption" that something>slipped past the beta testers?>>Beta testers report problems. The developers (ACES) either fix>them or not. That's their call.>>After the beta cycle (however many there are) is completed,>beta testers don't see the final results until everyone else>does...Its a legitimate question, Bill ... I notice you don't own an Nvidea card or at least list one in your sig! but like it or not ... customers are going to post things as they find them, please stop criticizing legit comments, it just causes grief.One beta tester has already commented that there was not enough testers this time around able to commit to the SP2/Acceleration/DX10 stuff, either because of other commitments or because of a short fall of testers with Vista or DX10 hardware, the bottom line is, Aces said there was a 20% increase using the DX10 preview, that's not the experience of the majority here, you must see that.Finally, don't get me wrong ... I love FSX, have played all in the series from FS2 onwards, the beta testers obviously helped Aces do a wonderful job with SP1, but if something is currently wrong we should be able to discuss it, and if there was a shortfall in SP2 DX10 testers, then this should be discussed too.Thanks.

Share this post


Link to post
Share on other sites

Well I just loaded the latest version of Nhancer and just had a lockup so thats not it.Im scared to install the latest directx version or driver.Seems to mostly deal with dx10 issure and hardware.Im getting this strange feeling MS wants us to ditch xp and move to vista.

Share this post


Link to post
Share on other sites

-SNIP->>Why is there always the "assumption" that something>slipped past the beta testers?>>Beta testers report problems. The developers (ACES) either fix>them or not. That's their call.>>After the beta cycle (however many there are) is completed,>beta testers don't see the final results until everyone else>does...>So, was this problem "reported"?I can't believe that something this blatantly PORKED couldhave NOT been seen in the beta.If it was reported then shame on ACES for allowing the productto ship without addressing something that renders several inflightoptions useless, not to mention compoundimg the possibility ofPORKING the FSX registration during a CTD ( as has happened to me )and putting the user back at the mercy of the questionable activationprocess....It's also rather strange that no one from ACES has commented onthis particular problem...at least not in any of the forumsI read and have seen posts concerning the menuCTD issue. Paul

Share this post


Link to post
Share on other sites

>Well I just loaded the latest version of Nhancer and just had>a lockup so thats not it.>Im scared to install the latest directx version or driver.>Seems to mostly deal with dx10 issure and hardware.>Im getting this strange feeling MS wants us to ditch xp and>move to vista.I've just installed the November DX9 update as well on XP and Vista as part of my ongoing system maintenance.I honestly don't think this is a ploy from MS to get XP ditched in preference of Vista though, from what I've read, things are better on XP for FSX and Acceleration/SP2, so long as you discount the DX10 preview option for Vista as borked, which is what it seems to be for one reason or another just now?Lets keep things in perspective.For the record, I own XP32/ XP64 and Vista 64 Ultimate (as well as DX10 hardware) XP32/Vista64 dual boot on this machine and XP64 on another.Cheers.

Share this post


Link to post
Share on other sites

What a mess.Ok I stopped fooling with the menu when flying till this is sorted.Im flying the F-18 and press a key on the crt. CRAAAAAAASHHHH.Ugly lock up...Lets not get this thread locked and if Im flaming the flames I will stop.Im giving it a few days then back to pre acceleration for me.

Share this post


Link to post
Share on other sites

JimJam,A few questions ... but first:I run Windows XP SP2 with an NVidia 7950 using 6.14.10.9381 drivers. Thus, FSX/Acceleration is using DX9. I have one add-on aircraft (the Alphasim Merlin) and have installed one add-on program (FSRecorder) in this build.I participated in the beta of Acceleration and did not see this problem, and saw nobody else reporting such a problem.Can you provide details like this listing third-party software you may have installed, and what graphics versions you're using? Also, it would be interesting to know whether you have attempted a pristine reinstall. If you have, and are still having the problem, then I'd suspect your video drivers ... if you are using anything other than 6.14.10.9381 with an Nvidia 7950 GX2, then that's the most likely culprit. If you haven't ... that's where I'd start, even if it means having to re-install a lot of third-party apps.

Share this post


Link to post
Share on other sites

Thanks for the advice.I am at the point where I am deciding if what acceleration has added it worth the hassle to do a complete reinstal with alot of addons.My guess is as soon as I hit delete, someone will solve or fix the problem.I still have fs9, just finished Bioshock and getting ready to reload Command and Conquer. So I can do without all the FSX drama for a while. Thanks again:D

Share this post


Link to post
Share on other sites

I would question the source of "there was not enough testers this time around...etc.) as a real beta tester is not allowed to comment on the beta testing process due to the nda. Therefore I would question if this is a "legit" comment to base a further argument upon.Then there is the logic of what is essentially being proposed :... in the phrase "the beta testers missed this"-there are really two logical options:1) A given problem did not happen to the beta testers-hence why they "missed it". It is pretty hard to report something that does not happen....2) A given problem did happen, was reported- but was ignored.If number 1 is valid-then the beta testers did do their job.If number 2 is valid-why would a company have beta testers in the first place? Bill is correct -A developer either fixesthem or not. That's their call. Most companies use beta testers however to find just such problems so they can fix them-otherwise why bother?Now what does make logical sense to me generically-is since a beta team is extremely small proportionally compared to a world wide market-that issues that may not arise in a beta test situation may emerge later because of the vastly greater numbers. We see these with all products-including operating systems. This is why even though a rigorous beta test is performed on most products today, we see patches. How many patches were there for windows xp for instance?-and can you imagine how big that beta team was?I don't think anyone is advocating not discussing a problem or legit complaints. Placing blame on certain parties though-some based on rumor, does not seem the most efficient thing to do to solve that problem .By the way-I own a nvidia card-a 7600 GS-I have never seen this problem.http://mywebpages.comcast.net/geofa/pages/rxp-pilot.jpgForum Moderatorhttp://geofageofa.spaces.live.com/

Share this post


Link to post
Share on other sites

>I would question the source of "there was not enough testers>this time around...etc.) as a real beta tester is not allowed>to comment on the beta testing process due to the nda.Why confuse and obfuscate things? A MS Aces beta tester did mention there were not enough DX10 beta testers for many reasons, the NDA was lifted, they were allowed to talk, if they were not allowed to say negative things on the beta and post beta process about lack of DX10 testing, then that will be addressed soon I guess.The fact remains, an Aces beta tester has told of the lack of DX10 testing amongst the community (for several reasons) DX10 people with hardware and software OS's to suit are in a minority. I can fully understand why some testers only chose DX9 and XP 32 as their holy grail (Vista hatred is like a religion, and that is sad but certainly extends to current FSX beta testers)I've even seen Bill leaming tell others that a DX10 card is a waste of money on here, can provide a link if needed ... now if that is the advice of beta testers of Acceleration/SP2/DX10 ... then where do we stand?All I see is riddles and contradictions just now.I love FS and FSX, but hate double standards, where did that Aces promised 20% performance increase go in DX10 preview? where did it come from? they must have had some sort of DX10 card and driver package along with other hardware to substantiate this ... what was it?I've splashed out a very lot of money on Microsoft OS's, Flight sims and last but not least, hardware over the years ... I'm a smhuck nobody, but I hope my voice still counts.These are honest and legitimate questions from a long time FS enthusiast.

Share this post


Link to post
Share on other sites

I too have the same problem with FSX/Acceleration. Sometimes when I access a menu item (doesn't matter what)... CTD. It's really annoying, but at least this problem is caused by a certain user action. Don't get me wrong; I'm not trying to belittle the problem but this issue isn't as severe as say FSX randomly crashing to the desktop for no apparent reason. (Which happened to me when I was using a nVidia-based motherboard)ACES, if you're reading this: Please fix the CTDs when accessing the menu. ThanksMy system:Processor: Intel Core2 Duo 6700 (2.667 GHz)Motherboard: Gigabyte GA-P35-DS3L/S3LMemory: Corsair DDR2 XMS2 2GB (2x 1GB matched pair)Video: nVidia Geforce 7600 GT (256MB, Driver version 163.71)Sound: Sound Blaster Audigy2 ZSStorage: Western Digital 250GB 7200RPM SATAOptical: Liteon DVD-+RW LightscribePower Supply: Athena Power 550WOS: Windows XP Professional SP2, Windows Vista Ultimate 64bit

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this