The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    169.01's and Source Engine Games - stupidly low framerates

    Discussion in 'Gaming (Software and Graphics Cards)' started by joebusby, Oct 31, 2007.

  1. joebusby

    joebusby Notebook Consultant

    Reputations:
    2
    Messages:
    176
    Likes Received:
    0
    Trophy Points:
    30
    PC in sig. Previously at capped rates, even playing with low qual models for better head visibility (css). On external monitor.

    Low and shakey rates, all the way down to 15's with lots of nades.

    Only since crysis driver, installed to play crysis (Which runs faster than this ****).
     
    joebusby, Oct 31, 2007
    #1
  2. alkaeda

    alkaeda Notebook Evangelist

    Reputations:
    14
    Messages:
    418
    Likes Received:
    0
    Trophy Points:
    30
    i have pretty much same spec and if anything my fps has risen....
     
    alkaeda, Oct 31, 2007
    #2
  3. bobz99by

    bobz99by Notebook Consultant

    Reputations:
    21
    Messages:
    148
    Likes Received:
    0
    Trophy Points:
    30
    using 169.01 my hl2 stress test rose from 90 to 100 fps at 1440x900 with 4x aa. OC'd 8600 gt to 588/700
     
    bobz99by, Oct 31, 2007
    #3
  4. Xelloss

    Xelloss Notebook Consultant

    Reputations:
    5
    Messages:
    155
    Likes Received:
    0
    Trophy Points:
    30
    I would make sure first the driver is installed correctly, go to the Nvidia control panel by right clicking anywhere on the desktop and selecting it then go to Help and System Info, make sure you have the correct drivers, if you do uninstall and downgrade or try reinstalling the drivers.
     
    Xelloss, Oct 31, 2007
    #4