Build Your Own Arcade Controls Forum

Software Support => GroovyMAME => Topic started by: gurbzs on December 19, 2015, 05:45:37 am

Title: win 7 triple screen dual 4890's
Post by: gurbzs on December 19, 2015, 05:45:37 am
Hi Groovy gamers,

I've updated my rig since last year (just4fun buggy boy thread), using now a asus maximus ii formula mono with 2 ati 4890's.
Can't seem to get more screens than 2, whatever I do. (tried donotdetectdisplay regedit)
The two graphic cards have 4 DVI outputs together and win 7 shows all 4 outputs.
I just can not select them: maybe output 1 and 2, 1 and 3 but Not 1,2 AND 3.

Any ideas how to solve this?
Is a 3 screen setup even possible with win 7?

Best regards,

Gurbz

Title: Re: win 7 triple screen dual 4890's
Post by: gurbzs on December 19, 2015, 03:37:19 pm
Allright, made some progress after another tweak.

Used donotdetectdisplay regedit on the other card and I have now three displays.
Still one problem, see the log file.
GM won't start the menu, can't initialise DDraw, etc, unable to create window.

How do I fix this?
Title: Re: win 7 triple screen dual 4890's
Post by: Calamity on December 19, 2015, 04:58:53 pm
Try forcing -video d3d from command line.
Title: Re: win 7 triple screen dual 4890's
Post by: gurbzs on December 19, 2015, 05:05:47 pm
Yeah, it works from the command line, buggy boy runs on triple screen.
Is it the User Interface setting, the game list that triggers this?
Title: Re: win 7 triple screen dual 4890's
Post by: Calamity on December 21, 2015, 05:58:26 am
Yeah, it works from the command line, buggy boy runs on triple screen.
Is it the User Interface setting, the game list that triggers this?

The problem is, there is an issue with W7 and interlaced modes that makes them ran at half their speed, so GM by default selects -video ddraw when an interlaced mode is used. But the funny thing is there's a second bug related to DDraw and W7 mode switching*. This second bug is normally bypassed by Switchres, but Switchres is not applied to secondary displays, so...  By forcing -video d3d from command line you prevent GM to fall back to DDraw, and thus bypass the bug.

You may force -d3d by creating a specific ini for that game and adding -video d3d in it.

Then, you may bypass d3d running at half speed by using -frame_delay.

* This bug is W7's, not GM's-