IS THERE ANY WAY TO MAKE IT WORK LIKE THAY PROMISED ?

Simu67 · Post by **Simu67** » 22 Oct 2008, 23:45

HI

Is there REALY any way to obtain what they promised ? Since 2 months, i trusted what Matrox said, bought a DTH2Go and three 22" screens. And since 2 months, no way to have the result they have announced.

My Vista 64 machine with Nvidia 8800GTX machine cannot give me the 5040X1050 resolution. I have tried a dozen of drivers, only one works in native resolution, but only in Windows, GXM cannot propose triple 1680X1050. And this driver is crashing FSX after 10 seconds, all 2D apps after 10 minutes.

When your setup is cumulating Windows bugs, Nvidia bugs, GXM bugs and FSX bugs, your coming crazy !

I saw a few threads here showing me that I am not alone with such desappointements, but Matrox doesn't advertise from such incompatibilities. I think after 2 months, we can hope better support.

Denis

meizme · Post by **meizme** » 23 Oct 2008, 02:33

Considering your post was so poorly written I am going to assume that your native language is not that of english origin, so i will try to make this as easy to understand as possible. I am not afiliated with matrox and have only owned their Triplehead2go for a short while, however i have been in the software and hardware bussiness for quite some time and would gladly address some of your conserns.

A.) the ammount of data required to travel down the dvi-dual link cale is nearly maxed out @ 5040x1050 57hz (5 megapixels 57 times in 1 second) thats near the realm of insane!

B.) nvidia drivers are not the problem, they are EXTREMELY tight to the specs of microsofts Directx and D3d standards, in fact i can give you many examples were they are so perfect that they cause problems with weak edid's.

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)

D.) matrox is a small company with only a even smaller market to cater to, the fact that they put in the R&D time to add widescreen resolutions to their product and have it work so well is amazing!

E.) lockups after minutes of use usually indicate a bad driver install, lack of power for the cpu or NB or SB or GPU, Corrupt or failing ram, or many other thing which piont to... YOUR COMPUTER, and not matrox's hardware.

Anyway good luck with your problem, however next time don't start asking for help by being rude!

Mesh · Post by **Mesh** » 23 Oct 2008, 06:29

Any resolution at 57Hz is not remotely standard. Most lcds run at 60Hz, if they work a bit more or less than that, bonus, they're not expected to.

That I've seen issues with resolutions not functionning have more to do with lcd that don't like any setting outside their native resolution and scan rate.

You should not blame a company for expecting more then was available when -you- decided to purchase that hardware.

If you are unwilling to accept some amount of failure, incompatibilities and general unexpected results from the bleeding egde that is pc usage, may I suggest you move to a console and save your blame for a company that doesn't catter to it's users?

Falke · Post by **Falke** » 23 Oct 2008, 09:01

mesh and meizme,

normally i would agree with you, but in fact i feel the same like the thread opener, upset. why?

http://matrox.com/graphics/en/support/drivers/download/gxm/tool/

there exists a matrox tool which tells you if you can run th2go or nor. it tells me i can go th2go, even with 5040*1050 at 57Hz. but in fact it doesnt.
I find my monitors in the thread of supporting monitors, so my lcds cant be the problem. i also find technical documents, telling me, a 9800gx2 got a dual dvi output. and there exist a thread in this forum, of ppl. confirming some drivers wont work....

btw i am also poorly speaking english, sorry for that, i am german.

Mesh · Post by **Mesh** » 23 Oct 2008, 17:10

Falke, I replied for a single reason:

This kind of thread is pointless.

No matter what outrage you might have that your gear isn't working, posting this kind of thread doesn't help.

If what is supposed to work doesn't then be in contact with those that can impact it, be it microsoft, nvidia, matrox or someone else.

The energy you waste posting about it here could be better server getting lines with those that can do something about it, the devs., the driver writers, anyone but here.

Simu67 · Post by **Simu67** » 23 Oct 2008, 22:00

Hi everybody,Thank you for your answers (right, English isn't my native langage).

I've actually the native resolution, so no problems with LCD frequencies, cable default or GXM soft. The only driver I have found that allows me this resolution is 175.16.

BUT : GXM does not propose this resolution, so in 3D app, the i have to interpolthe screens. I can only rech trhe triple 1680X1050 with Windows settings. I have tried to set a manual resolution with GXM, but each time, the screens stay black : 5040X1050@57hz is not working.

AND I am a Flight Simulator fan (since 1988). The 175.16 is unable to run FSX longer than 10 secs (e.g . 178.16 can run FSX 12 hours without any trouble, I can switch from full screen to windowed mode, open other applications, and there is virtually no way to crash this driver.

So, I have never reached the native resolution in my favorite application, and the only driver that works in this resolution under windows doesnt like my simulator (and is crashing in 2D apps all 10 minutes).

What I would appeciate is to know if anybody has other Nvidia driver for Vista64 that reaches the 5040X1050 in windows (I've tried 17 different drivers and this is a lot of time).

If I see a few answers like "my setup runs Vista64 and full triple wide works with someNvidia drivers that i've till tried, so, OK, I would admit it si my machine. But for the moment, I have not such answer ? I have seen a lot of messages from people having similar probs, and didn't have some solution.

I can understand that Matrox is not a Major Company, but I think they could advertise people that Nvidia + Vista64 does actually not work, or give a minimal indications to overcome this probs.

And I must add that Matrox's support does'nt answer to my mails, so I have now certain reason to be bad ! I could accept an answer like: OK, we know this kind of problem, we are working with Microsoft or Nvidia to solve this, but i simply get noyhing, and this is not fair !

Best regards

Post by **scavvenjahh** » 23 Oct 2008, 22:23

That's what I use my sig for : a not-too-intrusive space for the free expression of my frustration. Much better than mad posts with titles in caps ;) :lol:

Folks, if you're running Vista : create a new partition and try installing a trial version of XP. Chances are 5040x1050 will work flawlessly on that OS, it does on my rig. If not, well maybe there's sth more to it than "Matrox's fault"...

And have faith/patience ! I'm confident Matrox didn't introduce support for those new resolutions just to withdraw it a couple months later and leave us to our misery...

Mud · Post by **Mud** » 23 Oct 2008, 22:32

I'm confident Matrox didn't introduce support for those new resolutions just to withdraw it a couple months later and leave us to our misery...

You don't think it's anything to do with the increasing scarcity of 1280x1024 screens? :lol:

It is laudable however that they did it as a firmware upgrade rather than a new box.

Post by **scavvenjahh** » 23 Oct 2008, 22:49

Are you trying to ruin my guileless, cheerful post or sth ? :? :lol:

Simu67 : 5040x1050 works for me on Vista64 with forceware drivers 177.41 :) No idea how your particular graphics card and FSX like that version though.

Mud · Post by **Mud** » 23 Oct 2008, 22:55

No satirical posts until I'm off 177.41s, all sniping must be explicit!

meizme · Post by **meizme** » 24 Oct 2008, 04:08

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.

Falke · Post by **Falke** » 24 Oct 2008, 10:24

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...

P-Storm · Post by **P-Storm** » 24 Oct 2008, 12:17

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.

khula · Post by **khula** » 24 Oct 2008, 12:57

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...

Falke · Post by **Falke** » 24 Oct 2008, 13:14

@P-Storm

thanks, ill check this the afternoon

@khula

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

Post by **skipclarke** » 24 Oct 2008, 14:20

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?

Mesh · Post by **Mesh** » 24 Oct 2008, 16:30

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.

meizme · Post by **meizme** » 24 Oct 2008, 16:55

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.)

khula · Post by **khula** » 24 Oct 2008, 17:15

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...

meizme · Post by **meizme** » 24 Oct 2008, 17:40

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.

Widescreen Gaming Forum