Widescreen Gaming Forum

currently the only nvidia driver that the gxm powerdesk is scripted to add the direct support of the widescreen resolutions to the list avalible is the 175.19 not 175.16 if you grabbed the drivers listed i believe all of your problems will be solved.

if you don't mind me asking what are the current parts you are using in your computer, motherboard, CPU, GPU, and the monitors you are attemping to run, maybe i can help you get it working right...

also keep in mind that FSX is probebly the worst possible 3d engine i have ever seen in my life, well next to the one used in grid. Specifically for the support of high end components any way.

I have a EVGA 790I FTW, Q9550 @ 3.83Ghz x4 cores, OCZFXT320001G DDR3 ram 1800Mhz FSB 7-7-7-26, (2) 9800 GX2 (quad-sli) water cooled videocards running 750Mhz per core and 2200Mhz ram, 4x 500Gb sata2 3gbps 32mb cache HDD's in raid 0, 3x 22" benq FP202w v3 monitors and a 37" high def tv through hdmi (new 180.13 nvidia drivers allow sli and multimonitor) I'm not bragging what i'm about to say will shock you.. ready, FSX runs like crap on this machine. WHY??? because its not sli enhanced, bearly multicore opimized, and the textures are the worst compression format in the history of bad, i can run the game at 26-40 fps with all setting maxed except traffic and tree gen at 5040x1050 however i get major lag spikes and texture crawl, not to mention no support for monitor sync.

If you want to enjoy a flight sim with 3 monitors and smooth FPS try x-plane 9. the author has most of the kinks worked out, but headtracking support is a plugin and the cockpit 3d artist for the plugin, well sucks. but if headtracking isnt important you'll probebly notice that xplanes physics is far superior and the graphics are nearly identical as far as the specail effects and stuff go.

meizme,

i got a 9800gx2 too, so you got also vista ultimate 64? which driver are you using if you do?

I am frustrated because i just can try out, and the last step that ive not tried out is, to get that 226bw out of my config and trying with 3 226cw, which is said by others here to work with 57 hz.

well i dont have 220 Euro to try out, and if its not the solution, what then? can i give the lcd back? i have no friend who could give me a different lcd to test if my problem comes this from.

i need facts about my hardware, so i am lucky you got my graphiccard. if u use vista 64, with 175.19 i would change back to that driver, and try what happens to me. i am using the th2go firmware it had when i bought it, and the gxm of the cd. i also tried firmware and gxm of 5th of august which is the actual download.... nothing worked to me. the difference is, in the old firmware i see a column wich is called "suported" and there is shown for the 3 new widescreen "no".
the matrox compability tool says my system can run them.
otherwise i am not sure to plug off th2go and plug the 226bw alone to try it alone at 57hz, but if i can get behind that without i would spare a lot of time...

i just need an advice how i can find out that the samsung 226bw is causing the problem, due to its inability to run at 57 hz...

_________________
1st: [email protected], MSI X58 Pro-e, 24 GB Tripplechannel 1333, TUL R9 280X and Powercolor 7970 @ Crossfire with 2x Samsung 226CW 1x Dell P2210 @ 5040x1050 and Iiyama 2250MTS @ 1920x1080, Bequit Darkpower P8 1200W, G13, G15, G35, Hotas Warthog, Saitek Rudder, Saitek Yoke, Obutto R3volution Cockpit
http://ralfesser.de

meizme,

i got a 9800gx2 too, so you got also vista ultimate 64? which driver are you using if you do?

I am frustrated because i just can try out, and the last step that ive not tried out is, to get that 226bw out of my config and trying with 3 226cw, which is said by others here to work with 57 hz.

well i dont have 220 Euro to try out, and if its not the solution, what then? can i give the lcd back? i have no friend who could give me a different lcd to test if my problem comes this from.

i need facts about my hardware, so i am lucky you got my graphiccard. if u use vista 64, with 175.19 i would change back to that driver, and try what happens to me. i am using the th2go firmware it had when i bought it, and the gxm of the cd. i also tried firmware and gxm of 5th of august which is the actual download.... nothing worked to me. the difference is, in the old firmware i see a column wich is called "suported" and there is shown for the 3 new widescreen "no".
the matrox compability tool says my system can run them.
otherwise i am not sure to plug off th2go and plug the 226bw alone to try it alone at 57hz, but if i can get behind that without i would spare a lot of time...

i just need an advice how i can find out that the samsung 226bw is causing the problem, due to its inability to run at 57 hz...

Falke, where did you read that the 226bw does work? I did post here that the 225bw works.

Can you create a custom resolution for 1 monitor? Just plug 1 monitor in, and try to set it to 1680x1050@57Hz. If that doesn't work than 3 monitors won't work either.

I do have some sympathy with the Op. I think he's entitled to post here seeing as Matrox closed their forum months ago. If it wasn't for this community, most people wouldn't get the best out of their equipment. Matrox obviously like this arrangement as they can dip in and out as they choose to get a handle on what people with their hardware are up to...

I do think they could give more info on their product with regards 5040x1050, and be less misleading, but then I guess it wouldn't sell as much. The silence is deafening with regards the DX10 support (I'm still miffed that a DX10 card is required, but it doesn't actually support DX10 ingame - however that is dressed up, it's misleading).

With regards triple widescreen support, I understand that 5040x1050 is pushing the limit of video cards, but what of the lower resolutions? Why don't they work in DX10 either?

Anyway I don't want to hijack the Ops post by going on about DX10, I just empathise with his predicament. Matrox do say update to the latest Nvidia drivers to ensure compatibility/stability, but we all know they just don't work (and I'm not including manual entering custom resolutions - you shouldn't have to do that!). Only very specific Nvidia drivers work. That just cannot be right? Most people will download the latest driver and not understand why it's not working.

Unless you subscribe to the theory that you must have a fairly high level of technical expertise to buy this product, the casual enthusiast is going to struggle not just to get the best from it, but to actually make it work...

@P-Storm

thanks, ill check this the afternoon

@khula

DX10 is not supported ^^ ROFL, well ok, thats not tragic but nice 2 know ^^

_________________
1st: [email protected], MSI X58 Pro-e, 24 GB Tripplechannel 1333, TUL R9 280X and Powercolor 7970 @ Crossfire with 2x Samsung 226CW 1x Dell P2210 @ 5040x1050 and Iiyama 2250MTS @ 1920x1080, Bequit Darkpower P8 1200W, G13, G15, G35, Hotas Warthog, Saitek Rudder, Saitek Yoke, Obutto R3volution Cockpit
http://ralfesser.de

C.) The firmware patch added the feature for the 5:1 ratio triple widescreen setting not the matrox powerdesk software, if you use the "configure custom resolutions" you can add them manually (which btw is what the 158.19 driver script built into the matrox software does)

So, the Matrox driver just adds a custom resolution to the NVIDIA software? I saw the custom resolutions in mine, and made this assumption myself. I would only expect Matrox to support the current WHQL driver. I don't think it's in their best interest to support the moving target of a beta driver. Now, if this is how it's done, I would expect them to update the GXM for each driver, and provide a sniffer to know the GXM needs to be updated.

For a beta driver, couldn't you add the custom resolution manually?

I can't test this myself but I just thought of something that might possibly help 3x1680x1050@57Hz problems:

1- Disable all but 1 of the monitors, set it to 1024x768@60Hz.
2- Use nvidia custom res. to add 1680x1050@57Hz with advanced->auto
3- Use nvidia custom res. to add 5040x1050@57Hz with advanced->auto
4- repeat above with each monitor
5- reenable all 3 monitors
6- test if desktop can be set to 5040x1050@57Hz

The single monitor part I can test, I've just added 1680x1050@57Hz to this westinghouse, it didn't work before when I tried it. I've found the set to a supported res. fix since and this time it worked.

No idea if it'll work but the 1024x768 fix worked for me to get scaling with fixed aspect ratio working when it didn't before.

DX10 is a graphics subsystem, the th2g is external and only displays video, so dx10 is natively supported, if your referring to the software to setup the game ini's, the SGU then maybe but i manually tweak all my games. and to the OP, yes vista x64 ult. and i use 180.43 nvidia driver, which is in my post, just kinda hidden in there hehe. and to the poster about single monitor res at 1680x1050 @ 57hz that might not work cause the underlying pixel clock and hor/vert rates would be off from the ones used in triple monitor setups / 3, sorta like buying a chair at 70% off isn't the same as getting 20% off and then 50% of the remaining total.

I don't want you to think i am completely without problems, cause i am definatly not. bezel management throws one of my monitors into a tizzy, the SGU and Powerdesk software won't work under my new drivers (20.08 nforce & 180.43 geforce) so i need to manually setup all my games, oh and farcry 2 Runs like poop with quad-sli, and the aspect ratio of the game is figured out by your desktop res, so you gotta use the same desktop res and the ingame for it to look right.

biggest performance boost to FSX was to rename the defualt.xml file in autogen to defualt.bak (removed building and tree autogen.)

So you're saying you can play at 5040x1050 in DX10 mode ingame?

If so I'm sorry to say I just don't believe that. Every game I've tried in DX mode at that resolution does not work...

the EDID in dx10 won't list 5040x1050 because the firmware adds support for it but doesn't make it the native resolution, the native res is stil listed as 3840x1024 so you got to hack the EDID with the EDIDrestrictionflag 0 in the registry for dx10 and 5:1 aspect.