Forceware fixed aspect ratio scaling problem
Posted: 27 Mar 2006, 20:29
Hello
I'm having a problem with the fixed aspect ratio scaling in forceware. I'm really hoping someone is going to have some input as all my searching for similar problems have been in vain. Please don't refer me to the how-to thread on this site, it's not the same problem ;)
I have a Viewsonic VA1912W monitor capable of running 1440x900. Nvidia's Forceware drivers should be able to let me turn on fixed aspect ratio scaling so I can play my older games with black bars on the sides instead of having everything stretched. When I try turning this on though, the display becomes garbled and unreadable, like running an unsupported resolution on a CRT monitor. I think this is indeed what's happening as the monitors own info screen says it's now running 1280x1024. I'm quite sure this isn't supposed to happen... Right?
Using the centered output option gives the exact same results. Does anyone have any ideas as to what's going on here? Is this an error on my part or is it the .inf's or something? I'm running different versions of the 80.xx to 84.25 drivers...
I'm really looking forward to hearing from you, thanks in advance
I'm having a problem with the fixed aspect ratio scaling in forceware. I'm really hoping someone is going to have some input as all my searching for similar problems have been in vain. Please don't refer me to the how-to thread on this site, it's not the same problem ;)
I have a Viewsonic VA1912W monitor capable of running 1440x900. Nvidia's Forceware drivers should be able to let me turn on fixed aspect ratio scaling so I can play my older games with black bars on the sides instead of having everything stretched. When I try turning this on though, the display becomes garbled and unreadable, like running an unsupported resolution on a CRT monitor. I think this is indeed what's happening as the monitors own info screen says it's now running 1280x1024. I'm quite sure this isn't supposed to happen... Right?
Using the centered output option gives the exact same results. Does anyone have any ideas as to what's going on here? Is this an error on my part or is it the .inf's or something? I'm running different versions of the 80.xx to 84.25 drivers...
I'm really looking forward to hearing from you, thanks in advance