FC2 crash when cycle trough weapons

[Wags]

Thanks for the reports, we are investigating this.

[mjolner]

Just for further data.

 

I too am experiencing this crash, only in the A10 and only when switching weapons with the D key.

 

I am using a cougar. Not using profile, just mapping keys direct to the stick.

 

My system specs:

 

WIN7 64

I7 920 @ 4ghz, running default speed had no effect.

X58 w/ latest bios

6 G DDR3 1600

RAD 5870 with cat 10.2

SB Xfi xteme gamer

 

Also, fault only occurs in fullscreen mode.

[Gryzor]

SOLUTION to crash cycle weapons

 

SOLUTION:

 

Stablish the FPS limit at "90 fps", in graphics.cfg

 

You don´t will see the ctd anymore

 

Regards !

 

FC

[Distiler]

SOLUTION:

 

Stablish the FPS limit at "90 fps", in graphics.cfg

 

You don´t will see the ctd anymore

 

Regards !

 

FC

 

Oh well, I always had that setting limited, also in Ka-50. Right now at 60, the same as my screen vertical refresh, and never had the ctd.

[Gryzor]

The cause is that when you change weapons, and fps are over 100 (or more), changing weapons in A-10 tends to crash (especially when you see the sky).

[RvEYoda]

SOLUTION:

 

Stablish the FPS limit at "90 fps", in graphics.cfg

 

You don´t will see the ctd anymore

 

Regards !

 

FC

 

This only limits the frequency the crash occurs, but yes the bug is fps related

[unknown]

SOLUTION:

 

Stablish the FPS limit at "90 fps", in graphics.cfg

 

You don´t will see the ctd anymore

 

Regards !

 

FC

 

Confirmed!

Updated to the catalyst 10.3 which crashed after several seconds of cycling trough the weapons. Changed the MaxFPS to 90 and was cycling for 1 minute trough the weapons and NO crash.

 

Thank you very much!

[Mad Dog 7.62]

So change the line MaxFPS = 0 to MaxFPS = 90? Or 90 fps? or does it need the "" marks...ie "90 fps"?

[Wags]

The team is aware of the problem and will try to fix it.

[sage0030]

The team is aware of the problem and will try to fix it.

 

 

 

good to know was happening to me, I guess its only high end computers that can reach that fps lol, to bad for us, :joystick::joystick:

[Slayer]

Instead of messing with config files you could just leave vsync on in your video driver so framrate is caped at 60(or whatever refresh rate you run at)

[theGozr]

Same here crashes.. pretty hard when online..

[theGozr]

Well i followed the instruction on limiting my fps from the graphics.cfg to 90 and i haven't crashed since Offline/Online.

 

( SLI 280 SSC) ( W7U x64 )

 

Thanks :)

Edited April 4, 2010 by theGozr

[Kankkis]

Slayer is right, but i have Win 7 and ATI, my V-sync doesen't work without Rivatuner D3DOoverrider program, at least when i have choosen in game "Full Screen" option, without it no problem.

 

V-Sync is really good, no cockpit tearing at all when you use TiR, and that 60fps is really enough :)

 

Kankkis

[andyfoot]

Got the same problem here, crashing when cycling weapons in A10, but only after several cycles through weapons.

 

System Win 7 64bit HP

i7 930 @ 4Ghz

ATI 5850 Cat 10.3

6Gb Ram,

Track IR4

X52Pro Flight Stick and Rudder Pedals.

 

To change the config file to set Max fps, I need to use Notepad ++ or something don't I?

or would I be better using the Rivatuner (not tried it yet)?

[Lightning]

You can use the windows 7 Wordpad too , works for me

[andyfoot]

Went for the Rivatuner D3DOverrider programme. No crashes so far, my FPS is capped at around 60, but that's good enough. Tried using Wordpad or Notepad in XP to alter a config file on Black Shark about a year ago and it trashed my install, so I'm wary of using Win 7 Wordpad.

Edited April 5, 2010 by andyfoot

[sage0030]

I can confirm that the quick fix for the ctd for the cycle of the weapons with the d key does work tried this after I got off work yesterday,

[104th_Mac]

I am still having FC 2 crashes. I've completely changed the driver by running Phyxion.net's Driver Sweeper. I guarantee you, I have the latest and greatest WHDC certified nVidia driver verson 197.45 for Win7@32. It is definitely Simulator.exe that's crashing but the modules that cause the crash change. The last crash had nvlsp.dll locked up.

 

I signed on multiplayer and ran in observer mode for over two hours. I followed, by F11 and mouse, an F-15 through an engagement. Then, CTD. There was no other input from me to cause this. I had TIR running as was X-52 but not actively getting input from me.

 

Since so many people are running FC 2 with no issues, I am inclined to believe it is my LockOn install. I shall do a clean install, just to make sure. (If I can fly for two hours before I get a CTD, how can it be a bad install???)

 

One detail I found, when CTD, the cursor fails to be painted in any other window except the error message. (Unless, that is, if the cursor goes to my second monitor. Then the cursor is fine.) That might help point out the problem.

[ShadowVonChadwick]

Thanks for the reports, we are investigating this.

 

I turned of fullscreen to get rid of tearing textures & reduce stutter.

Fullscreen also disables Vsync.

Can also reproduce weapons cycle crash with FS on (need to cycle fast multiple times though). No error message just ends mission back to normal UI

Hi AA settings seem to make things worse also. (ATI 4850 x 2)

 

Cheers

Edited April 23, 2010 by ShadowVonChadwick

[ShadowVonChadwick]

Instead of messing with config files you could just leave vsync on in your video driver so framrate is caped at 60(or whatever refresh rate you run at)

 

For me Full Screen disables/overide Vsync on ATI 4850s.

[Tez]

nvlsp.dll is part of NVIDIA nTune. Could you try to uninstall it and perform some tests flights without it.

 

BTW it's a rather old utility, the latest version dated 2007.09.19. So it can be a good idea to move to another product for monitoring and tweaking your graphics card.

I am still having FC 2 crashes. I've completely changed the driver by running Phyxion.net's Driver Sweeper. I guarantee you, I have the latest and greatest WHDC certified nVidia driver verson 197.45 for Win7@32. It is definitely Simulator.exe that's crashing but the modules that cause the crash change. The last crash had nvlsp.dll locked up.

 

I signed on multiplayer and ran in observer mode for over two hours. I followed, by F11 and mouse, an F-15 through an engagement. Then, CTD. There was no other input from me to cause this. I had TIR running as was X-52 but not actively getting input from me.

 

Since so many people are running FC 2 with no issues, I am inclined to believe it is my LockOn install. I shall do a clean install, just to make sure. (If I can fly for two hours before I get a CTD, how can it be a bad install???)

 

One detail I found, when CTD, the cursor fails to be painted in any other window except the error message. (Unless, that is, if the cursor goes to my second monitor. Then the cursor is fine.) That might help point out the problem.

[Slayer]

Ntune is very dangerous to use, some driver versions and graphic card combinations will cause the GPU fan to stick at minimum and overheat your card. I lost one of my 8800 GTX's due to this.

 

EVGA precision is a great utility to monitor or tweak your cards and it has a histogram to see what your temps were while you were playing the game etc. You have to register at EVGA to get it but it works on pretty much any Nvidia card and they keep it updated.

[IvanK]

Vsync. When setting up Nvida profile point nvidia profile to simulator.exe ... it works just fine (GTX 295,Win7 64 bit, 1680 x 1085 full screen)

[topdog]

nvlsp is a network driver (of all things), and must be part of nvidia's awful (it really was) 'game prioritised network' QoS driver in their forceware drivers.

 

These would cause me to have many hard and random lockups when playing games - even non-network / single-player only ones - that I thought I had an acute overheating or faulty RAM problem for a while initially.

 

Getting rid of that was the best thing I did on this system build.