Home > Flight Simulation, Flightsim, FSX > New NVidia 91.47 driver test with FSX

New NVidia 91.47 driver test with FSX

Sunday, October 22nd, 2006

I tried out the new NVidia driver from a few days ago.  It’s still numbered 91.47, which I don’t understand, but now has an FSX suggested set of settings.  I ignored that and ran some benchmarks.  All use the same settings (saved as benchmark reference), and saved flight scenarios.  I wish I understood what has changed here.  The “17-Oct-2006” 91.47 driver is still dated 11-Aug-2006. I set AF=16, and AA to 4, Texture Filtering to High Quality.  Here’s the results, using average frame rates.  All scenarios are in slew mode, hovering over or near the airport, included some airports in day, some at night, all with no traffic.  Sept and Oct refer to the 91.47 version.  Can anybody confirm these findings?

                        Sept        Oct

KLAX             9.8          10.2      Improvement – not significant

KORD             6.2          9.1        Improvement 2.9fps = 47%

KPMD             31.5        40.6      Improvement 9.1fps = 29%

EDDF              9.5          12.4      Improvement 2.9 fps = 31%

CYKA             19.0        27.2      Improvement 9.2 fps = 43%

 

So there appears to be a significant performance increase in FSX. Incidentally, here’s the chunk of FSX.cfg settings that allow viewing of min/average/max framerates.

EDIT: Thanks Doug for the correction.

[TextInfo.1]
Latitude=1,1
Longitude=1,2
Altitude=1,3
Heading=1,4
AirSpeed=1,5
WindDirectionAndSpeed=1,6

[TextInfo.2]
FrameRate=1,1
LockedFrameRate=1,2
GForce=1,3
FuelPercentage=1,4
AverageFrameRate=1,5 //Added
[TextInfo.3]
Latitude=1,1
Longitude=1,2
Altitude=1,3
Heading=1,4
AirSpeed=1,5
WindDirectionAndSpeed=1,6
FrameRate=2,1
LockedFrameRate=2,2
GForce=2,3
FuelPercentage=2,4
AverageFrameRate=2,5 //Added

[SlewTextInfo.1]
Latitude=1,1
Longitude=1,2
Altitude=1,3
Heading=1,4
AirSpeed=1,5

[SlewTextInfo.2]
FrameRate=1,1
LockedFrameRate=1,2
AverageFrameRate=1,3 //Added

[SlewTextInfo.3]
Latitude=1,1
Longitude=1,2
Altitude=1,3
Heading=1,4
AirSpeed=1,5
FrameRate=2,1
LockedFrameRate=2,2
AverageFrameRate=2,3 //Added 

Advertisements
  1. Frank Grindel
    Monday, October 23rd, 2006 at 4:47 am

    Hi Jon,

    I had the previous 91.47 driver already installed and FSX kept quiting to the desktop at various times. After I installed this updated 91.47 the problem vanished and the FPS increased. I also don’t know what is different but it does work and FSX is now playable.
    Cheers,
    Frank

  2. Fabio
    Monday, October 23rd, 2006 at 11:24 pm

    No improvments for me

  3. Doug Horton
    Tuesday, October 24th, 2006 at 5:40 am

    Thanks for discovering how to add the average framerate display.

    Suggest you check numbering in testinfo.2 section as 2,2 is repeated.

    Also, you may wish to check order, as you have different order between average and locked fields in .2 and .3 for both normal and slew sections.

  4. Ken McKenze
    Tuesday, October 24th, 2006 at 7:49 am

    Hi Jon

    I flew the KingAir 350 from YVR to 2500′ turned North until I was off UBC. I turned East along Spanish Banks over the downtown core to SFU.
    I then turned South until I was in the Localizer and turned West until I was over YVR. I then turned East and flew to Chilliwack. I averaged 23.8FPS. All with the “old” 91.47 drivers.

    I unistalled the drivers and rebooted into the stock VGA drivers. I then installed the “new” 91.47 drivers into a separate directory and deleted the “old” 91.47 directory just to be on the safe side.

    I reflew the same flight and averaged 28.3FPS! 🙂 Best of all though I don’t not have the “shimmer” problem with the newer drivers.

    Ken

    A8N32-SLI with 1 7800GT….Athlon X2 4600+…..2 gig of ram

  5. Doug Horton
    Thursday, October 26th, 2006 at 3:57 am

    Jon,

    Slight correction to my post above. It’s 1,2 that’s repeated in your [TextInfo.2] section. Second occurrence should be changed to 1,3 and lines below should be renumbered 1,4 and 1,5

  6. Thursday, October 26th, 2006 at 1:27 pm

    @Fabio: thx for the report.
    @Doug: thx for the clarification. My (very bad) shimmer is unchanged, but I suspect my video card and BFG is willing to RMA it once I can get around to it.
    @Ken: thx for the spec, very close to mine, but what’s the context?

    I also heard that some folks were getting better results with latest DirectX 9.0C. But most reports I’ve seen indicate no difference, and even some glitches.

  7. Ken McKenzie
    Tuesday, October 31st, 2006 at 6:54 am

    Sorry, Jon….it’s early and I’ve only had 2 sips of coffee…what are you asking with your “what’s the context” comment? 🙂

    Ken

  8. Tuesday, October 31st, 2006 at 7:41 am

    Hi Ken,

    LOL, I think I replied to the wrong post! Thanks for your comments…

    Jon

  9. Tuesday, October 31st, 2006 at 7:46 am

    @Doug, I’ve fixed up that coding on the frame rate display.

  1. No trackbacks yet.
Comments are closed.