Widescreen Gaming Forum

Forget about that max pixel count... It's confusing at best. Even a single 8800 GT can display 5040x1050, period. All you need to achieve that res using TH2G is a DX10-compliant nvidia card. (Yeah, that DX10 part is confusing, too) :lol:

So it seems your panels can't do 1680x1050@57Hz, plain and simple. :( I'd love to see how it looks though. 26 "missing" pixels in height can't really ruin graphics I suppose. Could you post a couple game screenshots in the surround section ?

List corrected, thanks for your input !

Good news :D :D

I used the data for the user specific resolution in this thread:
[url]http://www.widescreengamingforum.com/node/9732]

and now 5040 * 1050 works on Samsung 2443BW :!:

So it seems your panels can't do 1680x1050@57Hz, plain and simple. :( I'd love to see how it looks though. 26 "missing" pixels in height can't really ruin graphics I suppose. Could you post a couple game screenshots in the surround section ?

Not sure what you mean by "in the surround section". But here are a couple of "Portal" screen shots at 5040x1024 using my Acer V223W monitors. It's puzzling to me is that these monitors will do 1680x1050 at 60hz (if, for example, I run Windows on only 2 screens) and 1680x1024 at 57hz but not 1680x1050 at 57hz. Bummer.

The image still looks pretty good though at 1680x1024 per monitor. If not for the monitor's self reporting "info" button on the front panel I would never have know it wasn't displaying 1050. I tried to find a similar info button on a high-end Dell 24" monitor at work and I couldn't find any way to get it to tell me what res it was running at. That makes me wonder if anybody is being fooled by what they are seeing?





If these should be posted in some other forum let me know and I will move them.

Well, your screenies are 1050 pixel high. So maybe that's just what is displayed and your monitors' OSD simply can't detect the actual res properly, since 1680x1050@57Hz is not a stock setting. I'll put your monitor model in a "special" sublist. :?

Grek1956, good news indeed. List updated again ;)

If only I knew what the indigenous code is for those clean little black dots the original list has and I can't even put an english name on !! :x

[list]
[*]Monitor 1[/*:m]
[*]Monitor 2[/*:m]
[*]Monitor 3[/*:m][/list:u]

And they're called Bullet Points ;)

_________________
Formerly eZ`

Follow me on twitter: @theg00seberry and find me on Steam

Double thanks sir ! In french we call'em "puces" i.e "fleas". (All in all, squashing insects and wasting ammo both seem pretty moronic ways to write down lists. Ah, vocabulary and ways of life.)

Well, your screenies are 1050 pixel high. So maybe that's just what is displayed and your monitors' OSD simply can't detect the actual res properly, since 1680x1050@57Hz is not a stock setting. I'll put your monitor model in a "special" sublist. :?

Sheesh! What a dummy. With all the screen capture, save, upload etc. I never noticed that the screenshot was 5040x1050.

As a note, on my Dell 2208WFPs, I have to run the scaling at 1:1 for 5040x1050 to work properly. Otherwise it cuts off the bottom of the screen. 4320x900 (and everything else) is fine with "fill" scaling. The OSD shows 5040x1050 at 57Hz.

I can confirm the new Samsung 2253BW has the issue with the OSD Not Optimal Range and then going black.

If you hit the source button it will bring it back but again the message stays on screen and eventually turns back off again.

I have 2 x 2253BW's and a 1 x 226BW. The 226BW I have works perfectly.

---

Did anyone find a solution/trick to making various models of the Samsung happy?

Someone said try Nvidia 175.19, did that solve the OSD message issue and allow you full 5040x1050?

Thanks
Tim

Did anyone find a solution/trick to making various models of the Samsung happy?

Someone said try Nvidia 175.19, did that solve the OSD message issue and allow you full 5040x1050?

Hi Tim

I'm currently running 3 Samsung 226BW's I was initially getting the OSD warning message on two out of the three panels. After I followed the instructions in this thread [url]http://www.widescreengamingforum.com/node/9799] the OSD warning hasn't reappeared.

The most important step in setting up the cutom display is when doing the Back-End Parameters select CVT Reduced Blank as the timing standard and then select manual before changing the values. This changes the pixel clock and Horizontal scan rate which you can't otherwise modify.

I've currently got values for Horizontal Scan Rate = 64.08 and Pixel Clock = 336.7500

I'm also using the new 180.48 Nvidia drivers and new 2.4.0.11 Matrox GXM (PowerDesk-SE).

See if doing this helps you out.

Regards,
Nigel