NVIDIA ForceWare 169.04 Beta


Recommended Posts

NVIDIA has new beta drivers up for download!

Release highlights:

* Beta driver for GeForce FX, 6, 7, and 8 series GPUs including GeForce 8800 GT.

* Recommended driver for Crysis single player game demo and TimeShift.

* Several game and application compatibility fixes. Please read the release notes for more information on product support, features, driver fixes and known compatibility issues.

* If you would like to be notified of upcoming drivers, please subscribe to the newsletter.

* Please read the driver installation hints before you install this driver.

Download for Windows Vista

English: 32-bit | 64-bit

International: 32-bit | 64-bit

Download for Windows XP

English: 32-bit | 64-bit

International: 32-bit | 64-bit

Link to comment
https://www.neowin.net/forum/topic/597548-nvidia-forceware-16904-beta/
Share on other sites

Hopefully this will solve the 64-bit Crysis demo freeze issue I'm having. About five seconds after Crysis starts in full screen, it becomes unresponsive - I have to go into Task Manager and kill it. 32-bit works fine.

I've heard that there supposedly is a 20% performance benefit if you run it in 64-bit mode vs. 32-bit, and am anxious to test it out.

again? That's a lot of beta releases in a short period. Will have to install when I get home.

No kidding! They released the 169.01 driver on Friday, the 169.02 driver on Monday, and the 169.04 driver today.

Nate,

There are several reasons why the 64bit may not work.

The first was the leaked pre-order version of the SP Demo. It had 64 bit executable issues.

It is recommended to use the rereleased public version.

The second was the 169.01 drivers. They apparently have done more harm than good, and their main focus was to help optimize some GPU hardware that had fallen by the wayside, which was a concern given that the SP demo is considerably old; rather than particularly increase performance, which, is a bit of a moot point, given the age of the demo. They also do not work with RivaTuner. And I suspect these new ones do not as well, as even the 2.06 version of Riva only covers the 163.7X series and older.

The third was some users, especially those using Nhancer, had multiple profiles in their Nvidia control panel or Nhancer database. Also, if you do not have duplicate or multiple profiles, you should at least remove the executable that the profile points to, and replace it with the newly installed 64 bit one.

There is another quirky suggestion that seem to have 'done the trick for some. That was to set GPU to default clocks, run the game in 32bit mode, set your visuals, save and exit, reboot, then run in 64bit. If it works, then modify clock settings.

What we know, is that the public release of the demo, using 163.69 Vista 64 drivers is confirmed as working, without flaws.

General FPS reports (1280X1024, no AA, Very High (a.k.a. DX10)) settings are:

high teens - high twenties for GTX users and mid teens-mid twenties for GTS users (roughly speaking).

The 64 bit will help processing, but it won't necessarily return better frame rates.

Edited by hopeful

Vsync and AF are non existent in the demo. And indeed it might be an issue, which is why checking the nvidia/nhancer profiles is a good idea, to ensure everything is disabled until you secure the stability first.

I'll add that to the notes, thank you.

And I'm not surprised the drivers give less performance with UT3, it was already performing great. These are just shoddy beta drivers, that have no need.

If you want drivers for Crysis, just wait a few days till after it's gone retail.

Vsync and AF are non existent in the demo. And indeed it might be an issue, which is why checking the nvidia/nhancer profiles is a good idea, to ensure everything is disabled until you secure the stability first.

I'll add that to the notes, thank you.

And I'm not surprised the drivers give less performance with UT3, it was already performing great. These are just shoddy beta drivers, that have no need.

If you want drivers for Crysis, just wait a few days till after it's gone retail.

This fix is for those who are having the 5 second fullscreen freeze, or that are unable to progress past the first ad screen in fullscreen mode.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I like the show more options. The only problem with it is that it's not always in a consistent spot in the menu. If the copy/paste/cut, happens to show on top, then more option is the last in the menu. But if copy/paste/cut happens to show on the bottom, then more options is before the copy/paste/cut. But I do like the more options because it hides the stuff that I rarely use. But I would like to choose what it is or isn't hiding. That would make it better.
    • I wonder if "put it back the way it was for decades" ever crossed their minds? 🤣
    • Rescind the stupid "Show more options" in context menus and just give us the full menu instead of adding more steps to get to what we want. The "simpler by default" makes me think they'll go in the opposite direction. Every context menu should have a configure button so you can pick and choose what options should be shown, I know you can do that with some registry fu but that shouldn't be required.
    • This is why competition must exist. Finally, pressure is mounting on Microsoft to move in the right direction.
    • Microsoft is making Windows 11's context menus faster, simpler, and configurable by Taras Buria Five years ago, Windows 11 introduced redesigned context menus, offering users a simpler, more modern design. However, customers quickly discovered that the new menus leave a lot to be desired. Many are unhappy with performance (they are really slow), while others dislike the double-layed design, where many options are hidden behind the "Show more options" button. In addition, over the years, menus became cluttered and overloaded. While Microsoft has already fixed plenty of pain points across Windows 11, context menus remain mostly unchanged. Fortunately, Microsoft is finally listening. Marcus Ash, Design and Research Lead for Windows at Microsoft, responded to a tweet on X, confirming that the company is working on fixing Windows 11's context menus. Reworked context menus are supposed to be faster, simpler by default, and "configurable to what you use most." What the latter means is unknown, just like whether Microsoft plans to keep the classic menu alongside the modern one, but according to Marcus, the wait should finally be over soon, as he promised to "share our approach soon." Improved context menus will most likely appear first in Windows 11 preview builds in the Experimental Channel. While we wait for Microsoft to release them, you can try fixing context menus on your PC with a simple tool called Windows 11 Context Menu Manager. It lets you disable entries you do not need, not only cleaning up context menus, but also making them significantly faster. Microsoft has already improved Windows 11's Start menu and taskbar, so hopefully it will address user criticism of the context menu as well. Stay tuned for new Windows 11 preview builds, which usually arrive every Friday.
  • Recent Achievements

    • Week One Done
      I2D earned a badge
      Week One Done
    • One Month Later
      Carru_123 earned a badge
      One Month Later
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      472
    2. 2
      PsYcHoKiLLa
      249
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      65
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!