Launch on primary display in Windows

[mydoghasworms]

In Windows, mame does not respect the primary display setting to launch on the primary display.

I have a Windows 10 laptop with a monitor connected via HDMI. In the Windows settings, I have set the monitor to the primary display, but mame always launches on the laptop display.

I have tried the command line flags with little or no success, but it would be nice not to have to tinker with those and have mame just working "as expected".

There is a similar bug for Linux: #7532

[john-iv]

Run mame with the -v command to get the displays interrogated:

Mame dkong -v|find \.\DISPLAYfile://./DISPLAY

In my 3 monitor case it produces: Video: Monitor 65539 = "\.\DISPLAY1" Video: Monitor 65537 = "\.\DISPLAY2" (primary) Video: Monitor 65541 = “\.\DISPLAY3file://./DISPLAY3”

Then use mame dkong -screen \.\DISPLAY2file://./DISPLAY2 in this case.

I agree though, it would be nice for MAME to default to the primary.

From: Martin Ceronio @.> Sent: Saturday, April 3, 2021 6:59 AM To: mamedev/mame @.> Cc: Subscribed @.***> Subject: [mamedev/mame] Launch on primary display in Windows (#7922)

In Windows, mame does not respect the primary display setting to launch on the primary display.

I have a Windows 10 laptop with a monitor connected via HDMI. In the Windows settings, I have set the monitor to the primary display, but mame always launches on the laptop display.

I have tried the command line flags with little or no success, but it would be nice not to have to tinker with those and have mame just working "as expected".

There is a similar bug for Linux: #7532https://github.com/mamedev/mame/issues/7532

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/mamedev/mame/issues/7922, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACGGUOYF22ULCZWQ6YUERNLTG4NKBANCNFSM42KISOVA.

[ghost]

yeah MAME's behavior here is against the grain, especially as the default option is 'auto' which would suggest an intelligent choice. In reality, it just always chooses 'screen1'

[Davidian1024]

For what it's worth I found a fix that's working for me on Ubuntu 20.04.6. Maybe it'll work for you as well. https://github.com/mamedev/mame/issues/7532#issuecomment-1713880191

[Davidian1024]

This might be fixed as of 0.259