Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06510 Graphics Major Always Feb 23, 2017, 22:31 15 days ago
Tester ozfalcon View Status Public Platform SDLMAME
Assigned To Resolution Open OS Linux (32-bit)
Status [?] Acknowledged Driver
Version 0.183 Fixed in Version Build Normal
Summary 06510: SDL2: -screen option not working for first display (of two)
Description Hardware setup is dual monitor - Mame is directed to either monitor.
numscreens is set to 1 (Multiple outputs is not the objective).

When directed to the second monitor, Everything is working as expected - The display appears on the second monitor.
 
When directed to the first monitor, The display appears "On the monitor the mouse is located".
This behaviour also occurs when -screen option is set to default "auto"
Using -screen or -screen0 produces the same result.
Using fullscreen or window produces the same result.
Steps To Reproduce To send display output to first LCD monitor (Not working as expected)
./sdlmame.0183.Mainline -window -screen screen0

To send display output to second LCD monitor (Working as expected)
./sdlmame.0183.Mainline -window -screen screen1
Additional Information There is no warning if an invalid target screen is used.
./sdlmame.0183.Mainline -window -screen RndTxt
No warning is given that display "RndTxt" does not exist.
Flags
Regression Version
Affected Sets / Systems SDL2
Attached Files
 
Relationships
There are no relationsihp linked to this issue.
Notes
4
User avatar
No.13667
shoegazer
Tester
Feb 24, 2017, 21:50
Using SDLMAME 0.183 with Linux Mint 18.1, kernel 4.8 and NVIDIA proprietary drivers, I've confirmed that an invalid target screen does not throw an exception as it should.

I was unable to reproduce the screen0 issue. That doesn't mean it doesn't exist; however I can't extend displays under my current setup, only mirror them, so I can't say for sure.
User avatar
No.13681
B2K24
Moderator
Mar 6, 2017, 04:54
Can anyone else using SDLMAME on Linux repo this?
User avatar
No.14206
ozfalcon
Tester
15 days ago
I thought I'd revisit this issue, And after some testing - Can be considered RESOLVED.

Since this bug was reported there has been a OS update (Debian 8 ---> Debian 9).
Using the same revision of Mame the issue was reported from no longer exhibits the same behaviour.

The correct behaviour occurs when using either window or fullscreen mode.
However no warning is issued if an invalid screen name is used as previously mentioned by shoegzer.
User avatar
No.14207
ozfalcon
Tester
15 days ago
edited on: 15 days ago
This is a separate issue - But related.

Mame is lacking the ability to associate system reported displays with screens available.
For example:
List the display devices.
xrandr |grep connected
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected primary 1280x1024+0+0 (normal left inverted right x axis y axis) 380mm x 300mm
HDMI-0 disconnected (normal left inverted right x axis y axis)
DVI-D-0 connected 1280x1024+1280+0 (normal left inverted right x axis y axis) 380mm x 300mm

There is no way to tell Mame directly to use a specific video output - Even a disconnected one.
Mame lists connected video output devices and assigns "screenX" for reference.
ie. There is no association between "DVI-I-1" and "screen0".
Setting SDL videodriver 'x11' ...
Available videodrivers: x11 wayland dummy
Current Videodriver: x11
Display #0
Renderdrivers:
opengl (0x0)
opengles2 (0x0)
software (0x0)
Display #1
Renderdrivers:
opengl (0x0)
opengles2 (0x0)
software (0x0)

Enter init_monitors
Adding monitor screen0 (1280 x 1024)
Adding monitor screen1 (1280 x 1024)
Leave init_monitors