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.

    Performance of Lower Resolution + nVidia Scaling VS Higher Native Resolution

    Discussion in 'Gaming (Software and Graphics Cards)' started by Brawn, Aug 3, 2010.

  1. Brawn

    Brawn The Awesome

    Reputations:
    145
    Messages:
    1,215
    Likes Received:
    4
    Trophy Points:
    56
    Hi, the native resolution on my laptop is 1600x900. When playing SC2, I lowered it to 1280x720 and am using nVidia's scaling. However, it seems that when I do this, I actually get worse performance (not to mention everything looks worse)

    So why is this? Is it because the scaling takes a lot of processing power?
     
    Brawn, Aug 3, 2010
    #1
  2. Brawn

    Brawn The Awesome

    Reputations:
    145
    Messages:
    1,215
    Likes Received:
    4
    Trophy Points:
    56
    bump anyone?
     
    Brawn, Aug 4, 2010
    #2
  3. key001

    key001 Notebook Evangelist

    Reputations:
    776
    Messages:
    657
    Likes Received:
    7
    Trophy Points:
    31
    well, run sc2 with fraps and tell us the fps with both resolutions
     
    key001, Aug 4, 2010
    #3
  4. Triple_Dude

    Triple_Dude Notebook Evangelist

    Reputations:
    75
    Messages:
    589
    Likes Received:
    0
    Trophy Points:
    30
    No need for FRAPS! Stop saying FRAPS goddamnit! Most PC games nowadays ship with some form of FPS monitoring tool. It's Ctrl + Alt + F for SC2.

    As for your original question: Try upgrading your driver... Lower resolution should by virtue use less processing power, and thus give you higher FPS--unless the driver is faulty and is messing up somewhere during the scaling.
     
    Triple_Dude, Aug 4, 2010
    #4