For any Widescreen TFT owners, a quick check please

MacX said:
With respect to the VX2025WM, I was getting the very same 'out of range errors' when trying to set the Nvidia control panel 'Fixed Apsect Ratio Scaling' so I could preserve the 4.3 aspect on some of my games.

All I did was power off the PC, plug the DVI Cable into the other output of my 7800gt, restart the PC, and am now able to game with black borders after changing the settings in the control panel. Not sure why that worked, but maybe the PC still thought I had my old CRT plugged in with a standard VGA cable.
Click to expand...

When you get the 'out of range' message, does a reboot by itself work, or do you have to physically change the DVI connection? Does unplugging and then pluggin the DVI cable back into the same slot work?

Also, how are you rebooting when you can't see the screen? Are you holding down the power switch for 'hard' power off, and if so, are you getting any data corruption in XP?
 
Last edited:
Baddass said:
so you have managed to get 4:3 aspect on the VX2025WM?
Click to expand...

It seems so. :D

I didn't even know people were having trouble with it till after I had it delivered from your goodselves the other day and wandered the forums. :)

Before explanations, what there is of one, here are a couple of pictures. The first is Oblivion set at 1280 x 1024, and the Nvidia control panel set to 'Fixed Aspect Ratio Scaling'.

The second picture, I set the resolution of Oblivion to 1024 x 768 and the Nvidia control panel to 'Centred Output'

VX2025_01.jpg



VX2025_02.jpg
 
davidstone28 said:
When you get the 'out of range' message, does a reboot by itself work, or do you have to physically change the DVI connection? Does unplugging and then pluggin the DVI cable back into the same slot work?

Also, how are you rebooting when you can't see the screen? Are you holding down the power switch for 'hard' power off, and if so, are you getting any data corruption in XP?
Click to expand...

All I did was:
1) power off the PC.
2) Remove DVI cable from right hand (viewed from front of tower case) DVI port on 7800gt,
3) Plug DVI cable into left hand port on 7800gt.
4) Reboot PC and allow PC to redetect new monitor on the second port.

I was possibly running with some faulty or twisted logic. I had an old CRT plugged into the left port of the card before the VX2025 arrived. I kind of thought that maybe I was getting the 'out of range error' because the drivers were somehow spooked into 'thinking' there was a CRT still attached, therefore scaling would not work. So I thought it would do no harm to move the TFT to the port the CRT had historically been plugged into, allowing the PC to redetect the new device.

Maybe faulty logic, but as you can see it worked.

Not sure if it would work with a 7900gt or other versions of Forceware. Talking of which I am using 84.25.
 
did the monitor get re-detected when you plugged it into the "new" DVI port? Did it initiate the installation of the Viewsonic driver? I'm wondering whether the presence or absence of the driver would have any effect at all.

what about over VGA, does it work then?
 
Baddass said:
did the monitor get re-detected when you plugged it into the "new" DVI port? Did it initiate the installation of the Viewsonic driver? I'm wondering whether the presence or absence of the driver would have any effect at all.

what about over VGA, does it work then?
Click to expand...

I haven't used any Viewsonic drivers off the disk. I let XP detect it as a VX2025. No windows installation dialogue boxes the first or the second time I plugged the monitor in.

I also calibrate my monitor for photo work with a Spyder2 and this DID give me clue as to whether this was detected as a new device because it squealed that it could find no calibration profile for this monitor after rebooting. I then had to choose a profile for it.

I haven't tested VGA.

*edit*
Just checked Device manager. The monitor is listed as a Plug and play monitor. Only the right-click on desktop, Nvidia Display shows it as a VX2025.
 
Last edited:
MacX said:
I haven't used any Viewsonic drivers off the disk. I let XP detect it as a VX2025. No windows installation dialogue boxes the first or the second time I plugged the monitor in.

I also calibrate my monitor for photo work with a Spyder2 and this DID give me clue as to whether this was detected as a new device because it squealed that it could find no calibration profile for this monitor after rebooting. I then had to choose a profile for it.

I haven't tested VGA.

*edit*
Just checked Device manager. The monitor is listed as a Plug and play monitor. Only the right-click on desktop, Nvidia Display shows it as a VX2025.
Click to expand...
i`d use the driver that came with it and not just let windows sort it out.
i used the CD that came with my LG
 
ShakenNstirred said:
i`d use the driver that came with it and not just let windows sort it out.
i used the CD that came with my LG
Click to expand...

Considering that apparently people are having scaling problems with the VX2025, and mine appears to be working, AND is fully colour calibrated, why would I want to do something as silly as that? :p ;)
 
Nice detective work MacX.

The concern that I would have whether it you would have to swap DVI connections every time you wanted to change aspect ratios.

For example, if you've swapped to the left DVI connector, are running 4:3, then switch back to 16:10, what happens happens when you select a 4:3 resolution again? Does it simply work, or do you have to start swapping connections again?

Would be interesting to know whether this is a full solution or a partial solution (constantly plugging and unplugging DVI connections)?
 
Last edited:
davidstone28 said:
Nice detective work MacX.
Click to expand...

Luck more like. :D I didn't know people were having problems till after I bought it!

The 'out of range error' only occurred when I tried to change the TFT options in the Nvidia control panel the first time. After swapping DVI and rebooting I was able to change the scaling options on the Nvidia control panel with out the error, after which it seems to have stuck. I haven't had to make any more changes since and just use my PC as normal. For instance, I can go between Half Life 2 Ep 1 on widescreen to Oblivion 4:3 (for performance reasons ;)) in the same session without making any more adjustments. :)

Of course if I get home later and it's all gone mad again you'll hear the scream from Northamptonshire quite clearly. ;)
 
Not an expert on this but someone may like to research EDID tables. From memory it works something like this: when a PC connects to a monitor over a DVI connection the PC requests the resolutions that the monitor can handle, receives a response and sets its output accordingly. These are generally VESA standard settings - and are usually 4:3 aspect ratio. I have no idea whether WS formats are now included. This information is in the EDID table and leads to out of range messages and/or blank display or wrong aspect ratios if incorrect.

Connecting/disconnecting/rebooting may fool the PC into delivering formats that haven't been confirmed by the monitor or allow changing from one screen's setting to another to work. Some software utilities can overide the information and send specific resolutions and refresh rates, ignoring the EDID information.

It has even been known (early projectors suffered from this) for the
EDID table to be wrong - in one case a projector did not even list its native resolution to the PC, causing no end of problems. The manufacturer eventually modified it when it was pointed out.

Somewhere there is an application that can be run on a PC that interrogates a monitor and allows you to read the EDID table values. This may be an area for someone with a little more technical ability and motivation than me to explore. Apologies if it's a red herring, it's been a long time since I needed to deal with it.
 
Last edited:
Now thats the sort of info nvidia should have given me. Very helpful indeed.
Obviously we need to know how this is applied to software 1.1 pixel mapping, but it sounds like the monitor must support it in its EDID table, however i'm sure its possible to write software that allows you to ignore that in the EDID table and force it to work with software scaling.
 
I believe that the monitor will display whatever it is given if it's at its native resolution. So a PC that generates a full image at say 1366 x 768 but only inserts 1024 x 768 active pixels as a 1:1 map will fill the rest in as black - that's how it will then appear on the screen.

Obviously any software scaling would be applied prior to transmission to the monitor.

I don't know why some screens should work with 1:1 in this way and others not. I would suspect the driver software, not the screen.
 
Last edited:
MontyUK said:
I don't know why some screens should work with 1:1 in this way and others not. I would suspect the driver software, not the screen.
Click to expand...
Bingo.
Thats exactly what i said to nvidia when they tried to tell me to contact the monitor manufacturer.
They can make this work on any ws monitor if they choose, and if they do it will make a good reason to buy an nvidias card over an ati one.
 
Hey Baddass and co, i've just got my pair of hanns g ws monitors going via dvi and the option for nvidia aspect scaling is in the nvidia control panel!

I'll have to experiment and see if it works, but other hanns g owners said it wasn't there.

This is very good news indeed if it does work.
 
You must log in or register to reply here.
Back
Top Bottom