
midd
Members-
Posts
139 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
midd's Achievements

32-Bit GPU (5/7)
20
Reputation
-
I'm pretty sure the latest version of the plug in only works with 13.19 or higher. Try an older version
- 169 replies
-
- third screen
- platform marquee videos
- (and 3 more)
-
It was the add to gamesDB plugin. I thought that was a "factory" plugin. I dont remember ever installing it.
- 169 replies
-
- third screen
- platform marquee videos
- (and 3 more)
-
I have the 6.0 installed and get the same errors
- 169 replies
-
- third screen
- platform marquee videos
- (and 3 more)
-
here's a decent Youtube tutorial on using a streamdeck in an arcade cabinet. Skip past the first few minutes. The rest is good and informative: https://www.youtube.com/watch?v=0rm0B1M-6Ys&list=PLvNsWRCC6ica5n4spukPjoFfyWnzcUUL6&index=147
-
Automatically set correct DISPLAY in mame.ini at startup - Marquee setups
midd replied to Hamburglin's topic in Emulation
ughh its not writing to the ini after I made the switch. -
Automatically set correct DISPLAY in mame.ini at startup - Marquee setups
midd replied to Hamburglin's topic in Emulation
ok so it appears to be writing to the correct ini file. However I have a new issue. When I booted up this morning, the program lauched and identified \\.\DISPLAY2 as the primary display. But when it wrote to the ini file which was previously DISPLAY14, it put DISPLAY2 and left the 4 on from DISPLAY14 thus giving me DISPLAY24. Should I go back to this : $content = $content -replace '(DISPLAY\d{1,2})',"$primarydisplay" -
Automatically set correct DISPLAY in mame.ini at startup - Marquee setups
midd replied to Hamburglin's topic in Emulation
These are the pop ups. Is this what you are referring to? https://imgur.com/gallery/CGv6f5X Think I figured it out. I assumed the proper mame.ini file was in the ini folder. There's another mame.ini in the mame folder. That's the one. I'll edit the script and see if it changes the righ mame.ini -
Automatically set correct DISPLAY in mame.ini at startup - Marquee setups
midd replied to Hamburglin's topic in Emulation
So your program didn’t update the lightgun ini. . But I downloaded arcade64 to make some changes using the gui. I can assign the screen, display14 and it will show in the ini file, but it’s still going to the marquee if I launch it through Launchbox. If I launch the game just through arcade64, it goes to the main display. must be something with his scripts. -
Automatically set correct DISPLAY in mame.ini at startup - Marquee setups
midd replied to Hamburglin's topic in Emulation
ok it didnt change in the lightgun drive -
Automatically set correct DISPLAY in mame.ini at startup - Marquee setups
midd replied to Hamburglin's topic in Emulation
then what am I looking for when I uncomment it. I did it for both areas as you instructed and a popup window appeared for every line of the .ini file, twice so I assumed it was for read and write. I had to select ok for each line to cycle through it all -
Automatically set correct DISPLAY in mame.ini at startup - Marquee setups
midd replied to Hamburglin's topic in Emulation
yes even with the original script, 2 of my mame ini files are showing Display14. the lightgun drive mame is read only. I've tried changing the permissions to allow write but the mame folder is still showing read only. He's got it locked down. I'm waiting for a reply from him. -
Automatically set correct DISPLAY in mame.ini at startup - Marquee setups
midd replied to Hamburglin's topic in Emulation
so its reading but its either not writing or not saving after it writes. ahhh the ini folder was read only. I'll try again. ok so I use three instances of mame. 2 of them switched. Jasen Baker's Integrum Retro Lightgun drive is read only so thats a problem. I'm waiting to hear back from him -
Automatically set correct DISPLAY in mame.ini at startup - Marquee setups
midd replied to Hamburglin's topic in Emulation
I copy this and changed the pathnames to my proper folders. I'm getting the popup window of \\.\Display14 for my primary screen. But I'm not seeing the change in the mame.ini file #Set working dir to mame directory so that it can read and write the mame.ini Set-Location -Path "E:\Launchbox\Emulators\MAME Lightgun\" #Get-Location #Run mame in verbose to grab display info. Wait 1 second so the file can be written $proc = Start-Process -FilePath "E:\Launchbox\Emulators\MAME Lightgun\mame.exe" -ArgumentList "-verbose" -RedirectStandardOutput output.txt Start-Sleep -Seconds 1 $inputs = Get-Content -Path 'E:\Launchbox\Emulators\MAME Lightgun\output.txt' #Write-Output $inputs #Find primary DISPLAY $primarydisplayline = ($inputs | Select-String "\(primary\)").Line $primarydisplay = $primarydisplayline -replace '.*(DISPLAY\d).*',"`$1" Write-Output $primarydisplayline Write-Output $primarydisplay #Read in mame.ini $content = Get-Content -Path 'E:\Launchbox\Emulators\MAME Lightgun\ini\mame.ini' #Write-Output $content #Edit mame.ini mouse related lines #Update DISPLAYx with primary DISPLAYy $content = $content -replace '(DISPLAY\d)',"$primarydisplay" #Write-Output $content #Write new mame.ini file $content | Set-Content -Path "E:\Launchbox\Emulators\MAME Lightgun\ini\mame.ini" #Kill mame Get-Process -Name MAME -ErrorAction SilentlyContinue | Stop-Process -Force -
Came to ask a similar question when I found this one. So I’ll add my question here. It seems like every time I boot up, my display order gets changed. I have three monitors that I use with the third screen plugin. Windows keeps the order in the display settings. However Mame is currently launching on my marquee screen instead of my main screen. And I change it each time in OSD setting in the .ini setting. And the display number in third screen plugin changes. I think the current config is display 5, display 6 and display 7. EDIT: found this thread and am giving it a try. Hopefully this works.
-
My issue with this is games like Wolfenstein and Beyond Castle Wolfentstein use Escape to save the game prior to exiting. So would I just use a Wait command in the script?