Tried an experiment on why I am getting 4 FPS during shootouts on an Athalon 2000 with a GeForce 3 Ti 200. So, I installed the game on my older system, which is an Intel 600E CPU with a Hercules GeForce 2 32MB card, and 528MB PC100 RAM.

I had NO...NONE..ZERO....NADA FPS drops during shootouts. I worked pretty #### great on this older system.

So it appears that this might have something to do with the Athalon CPU

Can anyone reason why?

1) Considering that SoF2 automatically sets certain options according to the system, I bet the configs aren't the same at all within the game...

2)  Did you read the FAQ re: AMD processors?  There are reg edits available for WinXP and Win2k.

See my post in this thread:

http://204.97.248.99/ib....;t=1406

I used to think that when AMD added 3DNOW to their processors that they'd fixed their performance problems in 3d applications (I have an Athlon t-bird 1400)....does anyone know if the XP CPU is better? Or should I just look into upgrading to an intel machine?

Yep,

Added the REGEDIT...even though it is not necessary with Windows XP systems. Please bear in mind, I ran the older computer with the EXACT same settings as my newer, "faster" system.

I still got the FPS drop during combat, reloading, or any type of weapons handling.

The Athlons have no issues.

Games built today have the issues that thier not properly made according to how the amd's work.

And btw, that fix didnt do anything for most of us. I think you lucked out hammer. thats still cool tho. mainly cause its not a xP fix, and sadly not many people use 2k anymore. (was and still is a great OS)

Tired of people "blaming" the processors when its the game that isnt compatible.

sorry, in a rant mood, just been one of those days.

Some people have found that firing the weapons can cause lag if forcefeedback is turned on in the mouse settings.

Athlons are awesome.  They have hardly any issues whatsoever.  They do have known "bugs", called "errata" in tech-speak.  But so does every other processor, including P4.  You normally don't need to worry about it at all.  It's the people who design BIOS, compilers and operating systems that need to worry about those.

If you don't trust me, just take a look at this link: Intel Pentium Spec Update.  Just search for the word "errata" within that web page and read.

Anyway, game designers do not program the CPU directly in this day and age.  They use a C or C++ compiler to generate code.  It's the job and duty of the C/C++ compiler to generate proper code for the CPU.  The game programmers should not need to be aware of the CPU brand the gamer is actually using.

If there was a problem with the CPU it'd be found by now.  CPU problems are nearly impossible to hide because CPU is a single and critical point of failure.

Stop blaming Athlon.  This game has bugs.  MS Windows itself has bugs.  Drivers have bugs.  (Oh yea, and even console games have bugs).

Turning of the mouse force feedback solved the problem completely!

I am in heaven