kvaughn
-
Posts
11 -
Joined
-
Last visited
Content Type
Profiles
Forums
Articles
Downloads
Gallery
Blogs
Posts posted by kvaughn
-
-
15 hours ago, Replay said:
Perhaps manipulating windows display settings swapping what's numbered and such would fix it. Otherwise it seems to be a weird issue.
You could try disabling all artwork (set to 0) CORE ARTWORK OPTIONS
and see if that resolves anything. Sometimes it can play bad with multiple displays
Only one that is enabled is artwork crop
disabling the other monitor has resolved the issue. so much for my hopes of a marquee monitor though
-
I guess I'll just disconnect the other monitor
-
Correction numscreens = 2
video = opengl does not help either
-
no luck...
I even tried copying the ini to the ini folder
-
I will try specifying the ini path using the -inipath switch when i get a chance
https://www.scribd.com/doc/16513476/Mame-Command-Line-Options
-
8 minutes ago, DOS76 said:
Are you using this in the .ini file \\.\DISPLAY2
well it's \\.\DISPLAY17 but yes. Every time i use vmmaker in crtemu drivers it incriments the count by 2. no biggie. This is also what mame64 -verbose shows to use. This is how i got it to load mame on the correct screen when launching it maually.
-
7 minutes ago, Replay said:
Ahhh okay, I missed that part. What version of GM is being used?
numscreen = 1
.192d3dex
i'll try .193 (regular) since d3dex doesn't work for me anyway
-
1 minute ago, DOS76 said:
Last time I had this issue with MAME on my multiple monitor setup restarting the computer fixed it.
rebooting has definitely not helped
-
9 minutes ago, Lordmonkus said:
Is your mame.ini file located in the same folder as your exe file or is it in the \ini folder ?
If it is in \ini folder and not in the main folder with the mame.exe copy it out to where the .exe is and try that.
This is something that seems to have become a common problem a while back now. It seemed to have started with the UI versions of Mame and I am not sure what happened to cause this problem because it wasn't a problem about a year ago or so with older versions of Mame. I have been generating my mame.ini file in the main folder where the mame.exe is located for quite a while so I have never run into this issue personally.
It is located in the same folder as the exe
-
When launching mame (groovymame) manually it will correctly launch to the monitor that is setup in the ini file. Playing from launchbox does not. It's like it's ignoring the ini file.
Launchbox not launching mame on correct monitor
in Troubleshooting
Posted
could it be an issue with windows 10? anyone using it with multiple monitors?