GETTING HIGH AND STABLE FPS ON MAX SETTINGS

[saisran 84]

I have recently retired my trusted laptop and built a new mATX PC with an I7-3770, 8GB of RAM and a GTX 1070. Admittedly, the only new thing here is the GTX 1070 and the rest are just a collection of bits. But it performs well and runs All of my games at 100+FPS except SF2 which runs at 60+FPS, but even so its smooth and i just think the reason why it doesn't reach 100FPS is because Stary made all that excellent Visual Mods! (i'm not complaining Stary! I love your work to bits!)

 

I was enjoying it until i decided to run a mission on NA and this happens...

23 FPS?

 

 

I have all settings on highest they'll ever go

I also have the pre-rendered Frames Set to 1 and fade set to False

 

I might just be the nature of the game being hard to run and i may just be able to fix it by setting the horizon distance to far instead of very far but the thing is i don't want to really turn down the graphic settings.

 

So is there any further tweaks that i should know that will enable constant high frame rates even on the deck of a carrier on the stock North Atlantic Terrain? The thing is as soon i left the deck the frame rate jumped and even reached 77 FPS with 16 strong F-14B flying in front of me and three more being rendered in the mirror.

 

Thanks for the advice guys!

[GodsLt 3]

I have the exact same issue.

I'm running a highly overclocked GTX960M (laptop card) with this game on "unlimited" settings. Most of the time the framerates are stable, but the moment flak opens up or I'm taking off a carrier or open the TV screen my framerates run into the ground. 

 

I've tracked my GPU usage throughout extended gaming sessions in both SF2 (modded and unmodded) and WarThunder. WarThunder has a much higher Visual Fidelity, and is definitely more taxing on a system. On "high" settings my GPU will be pushed to 95+% usage CONSTANTLY. No drops, no hiccups, nothing. This will keep my framerate locked solidly at 60FPS regardless on what's being rendered.

 

However, the story changes for SF2. After hours of simming, my GPU usage sits happily at around 30%. If I crank up the AA to 8x, MSAA 2x, FXAA 8x and Anisotropic filtering to 8x my usage goes up 5% but my frames still take a dip. If I then render SF2 at 4K (My laptop has a 4K screen), I get a solid 30FPS but my GPU usage hovers around the 40% mark... All of this with ForceVSyncOff=TRUE and Vsync off in the Nvidia control panel.

 

I don't know what gives!

[+Gunrunner 313]

It's not the GPU guys, it's the code, I'm having the same problem but considering that :

 

- I'm between 12 and 15 percent total CPU usage when allowing the use of all cores.

- When dedicating a single core to SF2, I'm never above 70% core usage and lose a maximum of 5 FPS over allowing all cores to be used.

- I'm well below in total memory usage, as well as below the memory allocation for a 32 bits process and data transfers are not reaching any bottleneck.

- Even at full load, I'm at most at 50% GPU usage.

- Even at full load, memory usage, memory controller load and bus interface load are never above 40%.

- With my configuration and settings, below 1680x1050 the lower the resolution, the higher the max and average FPS, above 1680x1050 average and max FPS are about the same until at least 2560x1440, but the higher the resolution, the lower the minimum FPS.

 

The only possible conclusion is that the code/engine is the limiting factor.

 

You can grab a handful of FPS with a beefier GPU, but this has quickly diminishing returns.

You can grab a handful of FPS with a CPU with higher single core performance, but once again, it has quickly diminishing returns (and in your case, an i7 3770, the improvements would be in the single digits realm, all other things being equal).

You can avoid FPS drops by replacing some image formats.

You can increase your FPS by going for lower AA and AF settings or removing custom shaders and configs.

 

The only true benefit of a GPU upgrade is the ability to increase the resolution and have better AA and AF settings (in fact, curiously, with the GTX 970 I have almost the same performance - within the margin of error - whether I play at 1920x1200 or 2560x1440).

 

We are dealing with a 14 years old game engine last seriously updated 4 years ago.

[+daddyairplanes 8,670]

whatcha you all running for RAM (saisran exluded, saw yours)? tried my new toy out overland Iceland to compare to my old one. I7-6700, GTX1070,  and 32 GB RAM and had a wicked drop in fps after dropping Snakes on a hot target..... from 102 down to 77. while i dont think anyone else here is gonna be running 32GB, 16 could be a decent goal.  i updated my usual system few years back from 8 to 16GB and am typing this on a desktop taht needs to be updated (6GB installed, slightly over 3 usable). Iceland is the screwiest of the stock terriains and the more memory available the more stable. i havent messed with edits like forceVsync in a long time btw,  just set high items important to me (mostly outside world) with exception to teh desktop. for the record  on my RAM theory

 

desktop        3.5GB ram     integrated card     30-40 fps norm  drops to single digits

HP dv6         16GB ram      radeon card          50-60 norm       drops to high teens low 20s at worst

xidax XM-10  32 GB ram    nVidia 1070           100 norm           dropped 25 pts

 

just my thoughts on the matter.

[GodsLt 3]

The thing is, on my older laptop (an Asus VivoBook running a GT740M) I had much more stable framerates. My GPU usage was reasonable ~90% as were my temperatures. 

Here is my current system for reference:

    Time of this report: 10/5/2016, 14:34:44

             Machine name: WINDOWS-ULBDE0P

               Machine Id: {E6E516C0-2793-4AE0-A7AE-BD3D8FFC59BA}

         Operating System: Windows 10 Home 64-bit (10.0, Build 14393) (14393.rs1_release.160915-0644)

                 Language: English (Regional Setting: English)

      System Manufacturer: Dell Inc.

             System Model: XPS 15 9550

                     BIOS: 01.02.00

                Processor: Intel® Core i5-6300HQ CPU @ 2.30GHz (4 CPUs), ~2.3GHz

                   Memory: 8192MB RAM

      Available OS Memory: 8048MB RAM

                Page File: 7732MB used, 5317MB available

              Windows Dir: C:\WINDOWS

          DirectX Version: DirectX 12

      DX Setup Parameters: Not found

         User DPI Setting: Using System DPI

       System DPI Setting: 240 DPI (250 percent)

          DWM DPI Scaling: UnKnown

                 Miracast: Available, with HDCP

Microsoft Graphics Hybrid: Supported

           DxDiag Version: 10.00.14393.0000 64bit Unicode

 

---------------

Display Devices

---------------

          Card name: Intel® HD Graphics 530

       Manufacturer: Intel Corporation

          Chip type: Intel® HD Graphics Family

           DAC type: Internal

        Device Type: Full Device

         Device Key: Enum\PCI\VEN_8086&DEV_191B&SUBSYS_06E41028&REV_06

      Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] 

Device Problem Code: No Problem

Driver Problem Code: Unknown

     Display Memory: 4151 MB

   Dedicated Memory: 128 MB

      Shared Memory: 4023 MB

       Current Mode: 3840 x 2160 (32 bit) (60Hz)

       Monitor Name: Generic PnP Monitor

      Monitor Model: unknown

         Monitor Id: SHP143E

        Native Mode: 3840 x 2160(p) (59.997Hz)

        Output Type: Internal

        Driver Name: igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igd12umd64.dll

Driver File Version: 20.19.0015.4454 (English)

     Driver Version: 20.19.15.4454

        DDI Version: 12

     Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1

       Driver Model: WDDM 2.0

Graphics Preemption: Triangle

 Compute Preemption: Thread

           Miracast: Supported

Hybrid Graphics GPU: Integrated

     Power P-states: Not Supported

  Driver Attributes: Final Retail

   Driver Date/Size: 5/3/2016 5:00:00 PM, 39859696 bytes

        WHQL Logo'd: Yes

    WHQL Date Stamp: Unknown

  Device Identifier: {D7B78E66-5A5B-11CF-FE62-EB26BAC2D935}

          Vendor ID: 0x8086

          Device ID: 0x191B

          SubSys ID: 0x06E41028

        Revision ID: 0x0006

 Driver Strong Name: oem45.inf:5f63e5340a14bf6c:iSKLD_w10:20.19.15.4454:pci\ven_8086&dev_191b&subsys_06e41028

     Rank Of Driver: 00D10001

        Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C 

        DXVA2 Modes: DXVA2_ModeMPEG2_VLD  DXVA2_ModeMPEG2_IDCT  DXVA2_ModeVC1_D2010  DXVA2_ModeWMV9_IDCT  DXVA2_ModeVC1_IDCT  DXVA2_ModeH264_VLD_NoFGT  DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT  DXVA2_ModeH264_VLD_Stereo_NoFGT  DXVA2_ModeH264_VLD_Multiview_NoFGT  DXVA2_ModeHEVC_VLD_Main  DXVA2_ModeHEVC_VLD_Main10  

   Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 

                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 

                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 

                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 

                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 

                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 

                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 

                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 

                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 

                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 

                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 

                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 

                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 

                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 

                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 

                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 

                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 

                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 

                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 

                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 

                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 

                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 

                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 

                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 

       D3D9 Overlay: Supported

            DXVA-HD: Supported

       DDraw Status: Enabled

         D3D Status: Enabled

         AGP Status: Enabled

           MPO Caps: Not Supported

        MPO Stretch: Not Supported

    MPO Media Hints: Not Supported

        MPO Formats: Not Supported

 

          Card name: NVIDIA GeForce GTX 960M

       Manufacturer: NVIDIA

          Chip type: GeForce GTX 960M

           DAC type: Integrated RAMDAC

        Device Type: Render-Only Device

         Device Key: Enum\PCI\VEN_10DE&DEV_139B&SUBSYS_06E41028&REV_A2

      Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] 

Device Problem Code: No Problem

Driver Problem Code: Unknown

     Display Memory: 6042 MB

   Dedicated Memory: 2018 MB

      Shared Memory: 4023 MB

       Current Mode: Unknown

        Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_86f2ae812568c59a\nvd3dumx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_86f2ae812568c59a\nvwgf2umx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_86f2ae812568c59a\nvwgf2umx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_86f2ae812568c59a\nvwgf2umx.dll

Driver File Version: 21.21.0013.7290 (English)

     Driver Version: 21.21.13.7290

        DDI Version: 12

     Feature Levels: 11_0,10_1,10_0,9_3,9_2,9_1

       Driver Model: WDDM 2.1

Graphics Preemption: DMA

 Compute Preemption: DMA

           Miracast: Not Supported by Graphics driver

Hybrid Graphics GPU: Discrete

     Power P-states: Not Supported

  Driver Attributes: Final Retail

   Driver Date/Size: 9/15/2016 5:00:00 PM, 17621512 bytes

        WHQL Logo'd: Yes

    WHQL Date Stamp: Unknown

  Device Identifier: Unknown

          Vendor ID: 0x10DE

          Device ID: 0x139B

          SubSys ID: 0x06E41028

        Revision ID: 0x00A2

 Driver Strong Name: oem8.inf:0f066de379c1b3f2:Section190:21.21.13.7290:pci\ven_10de&dev_139b&subsys_06e41028

     Rank Of Driver: 00D10001

        Video Accel: Unknown

        DXVA2 Modes: DXVA2_ModeMPEG2_VLD  DXVA2_ModeVC1_D2010  DXVA2_ModeVC1_VLD  DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT  DXVA2_ModeH264_VLD_Stereo_NoFGT  DXVA2_ModeH264_VLD_NoFGT  DXVA2_ModeHEVC_VLD_Main  DXVA2_ModeMPEG4pt2_VLD_Simple  DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC  

      Deinterlace Caps: n/a

       D3D9 Overlay: Unknown

            DXVA-HD: Unknown

       DDraw Status: Enabled

         D3D Status: Enabled

         AGP Status: Enabled

           MPO Caps: Not Supported

        MPO Stretch: Not Supported

    MPO Media Hints: Not Supported

        MPO Formats: Not Supported

 

[Spudknocker 241]

Well one big thing that can help is converting cockpit and aircraft skins to JPG's this is rather time consuming and annoying but it can help...another thing that can help is by putting effects to high instead of unlimited...while the sun wont look so amazing most effects remain unchanged especially if you have a unified effects package from stary.

 

Also going into the options ini and forcing V sync off can add a little bit of a boost to the FPS 

[Fubar512 1,350]

First off, there's a couple of misconceptions here.  The series is CPU-bound if one sets the horizon draw distance too far.  Pull that back to "normal" and check again.  Also, being a 32-bit game, SF2 is limited to a 4 GB block of memory.  To be truthful, I have never seen it exceed 2.5 GB.  

 

Also, you will not see any gain in FPS with more than 8 GB of system RAM, even under Windows 10. Search on Youtube, and you'll find videos that will bear this out.

 

I run 16 GB in my system because I encode video and audio, and the apps that I use for both are 64-bit, so they are not subject to the 32-bit, 4 GB memory space limitation.

 

In performing experiments with various overclocks (CPU speeds), I've come to the conclusion, that to avoid massive slowdowns in frame rate, one needs in the neighborhood of 4 gHz of processor speed when running the more intensive scenarios (heavy SAM & triple AAA activity over Hanoi, etc), and a bare minimum of 1 GB of dedicated video RAM on either an Nvidia or AMD graphics card. 2 GB is better, and 4 GB of VRAM is probably the maximum that the game will utilize in its current state of development.

 

Another issue, that was brought up, was Anti-aliasing, Anisotropic filtering, and other settings.  I can get away with maxing all these out on a GTX 1070, and I suspect that those with (6 GB) GTX 1060s will be able to this, as well. However, there are settings in the Nvidia control panel that will adversely effect your framerates, without providing any real benefits, or worse yet, no benefits at all. We should perform a test on all these, and then compare results.

 

As Gunrunner mentioned, we're also looking at code that was already old several years old when the series was released in 2003, and upgraded in 2008 to use DX10 (SF2).

Edited October 6, 2016 by Fubar512

[saisran 84]

Thanks for the feed back everyone. I Guess it's really a software thing.  

 

I have a surplus of RAM Sticks but unfortunately none of the combination runs well on Dual Channel on my board. I have to get a dual channel package if im going for 16GB. But honestly, i haven't seen any improvement from 8GB single stick to 16GB dual. 

 

Guess its really with the software. It's funny how an old game is harder to run than the latest AAA Title.

 

Guess a bunch of Testing is in order. While the low framerates in deck isn't that much of a problem. Its a different story when actually flying. Hopefully i dont get FPS drops in that regard.\

 

 

 

I forgot to mention that i'm playing on an HD TV instead of a Monitor. I mostly Play SF2, Racing Games and Some RPG.

Edited October 6, 2016 by saisran

[GodsLt 3]

Alright guys, I think I've made some headway.

I lowered my Horizon distance from unlimited to normal...and wow. Full 60fps in flight and ~50fps in target-rich environments. However, selecting the brimstone's TV display lowers frames to 30fps.

Oddly enough, the SBD TV display does not exhibit the same amount of slowdown, averaging ~40fps. No idea why though.

[Emp_Palpatine 501]

Alright guys, I think I've made some headway.

 

I lowered my Horizon distance from unlimited to normal...and wow. Full 60fps in flight and ~50fps in target-rich environments. However, selecting the brimstone's TV display lowers frames to 30fps.

Oddly enough, the SBD TV display does not exhibit the same amount of slowdown, averaging ~40fps. No idea why though.

Does this works with the extended horizon tricks?

[GodsLt 3]

Hey Emp!
I don't know if it does...I'm using it in the various campaigns available here such as ODS, OD, NA EXP, I EXP, A&G EXP etc.

[+baffmeister 1,205]

I found this site useful when trying to optimize my graphics card. Interesting reading. Here's a link: http://www.tweakguides.com/NVFORCE_6.html

[Spudknocker 241]

to keep from getting a huge FPS slowdown when launching brimstones and mavericks etc lower the sight FOV in the weapons data file to 1.50000 and the problem should be solved