BF2 / BF2142 with Dualscreen ? Possible ? What resolution ?

[skipclarke]

can i ask a really stupid question... i havent had a nV card since I had a 6800GT agp card, and i dont have a TH2Go... but seems like there is LOTS of people having problems with running more than standard resolutions.

am i about right there?

To run wide THG with Vista and 200 series card you need the beta power desk plus 182.50 drivers, newer drivers wont work.

:wink:

[skipclarke]

[quote]can i ask a really stupid question... i havent had a nV card since I had a 6800GT agp card, and i dont have a TH2Go... but seems like there is LOTS of people having problems with running more than standard resolutions.

am i about right there?

To run wide THG with Vista and 200 series card you need the beta power desk plus 182.50 drivers, newer drivers wont work.

:wink:
Several newer drivers work if you know how to set them up. They just dont work for everyone. The very latest 190 series have other issues, but 190.38 is my current driver Im gaming with.
To answer Gilly's question, the issue with nVidia and Custom Resolution tests failing is not TH2G or surround related, its any Custom Resolution.

What about using these with the beta powerdesk driver? (which bypasses using custom resolutions; I'm using it because I couldn't get custom resolutions working in the first place.)

Why do you think the Powerdesk beta doesnt use Custom Resolutions? The display driver sets the resolution based on EDID from the "monitor" (TH2G in this case). If Matrox could have the TH2G send 5040x1050 as a valid resolution to display drivers it would be much better.

Powerdesk just automates Custom Resolution insertion but with no user input (such as tweaking the refresh rate) which is why it tends to work on a very specific range of drivers. Its not a viable tool for most people technically, but its the only thing many can or will use.


Incidentally no version of Powerdesk has ever added or displayed 5040x1050 res for me. Ever.

[skipclarke]

The very latest 190 series have other issues, but 190.38 is my current driver Im gaming with.

Can you play at 5040x1050 with the 190 drivers ? Thats interesting, it seems to be impossible here.

[skipclarke]

can i ask a really stupid question... i havent had a nV card since I had a 6800GT agp card, and i dont have a TH2Go... but seems like there is LOTS of people having problems with running more than standard resolutions.

am i about right there?

The only problem is trying to obtain the 5040 resolution (with latest drivers)...every other resolution works fine for all that have nVidia cards.

[skipclarke]

Why do you think the Powerdesk beta doesnt use Custom Resolutions? The display driver sets the resolution based on EDID from the "monitor" (TH2G in this case). If Matrox could have the TH2G send 5040x1050 as a valid resolution to display drivers it would be much better.

Have you tried the latest firmware (2.3.4)? I know it isnt Nvidia cards, but on my ATi card once it was installed it instantly recognized the resolution as a valid display option.

[skipclarke]

There is a lot of confusion here. To anyone that has it working on 200-series, what is your current nVidia driver version and your PowerDesk version?

[skipclarke]

Beta powerdesk and 182.50 drivers here, working fine at 5040x1050.

[skipclarke]

I'm also using GXM 2.05.00.020 and Vista 64 182.50. No matter what I do, I can't get anything newer to run right.

I'm always a fan of conspiracy theories but isn't it odd timing just as things get better for ATI drivers, it starts going to crap on the nVidia drivers?

[skipclarke]

I'm also using GXM 2.05.00.020 and Vista 64 182.50. No matter what I do, I can't get anything newer to run right.

I'm always a fan of conspiracy theories but isn't it odd timing just as things get better for ATI drivers, it starts going to crap on the nVidia drivers?

lol yes, same here :lol:

[skipclarke]

I've posted this before but again about nvidia custom resolutions:

- switch to a standard res. before making a custom res. (aka 1024x768)
- define custom res. as needed, and watch as a previous failed test now works.