Jump to content
LaunchBox Community Forums

Hamburglin

Members
  • Posts

    206
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Hamburglin's Achievements

32-Bit GPU

32-Bit GPU (5/7)

5

Reputation

  1. I doubt it. Unless you set that control at the folder level instead of the specific file level.
  2. Interesting. To me, that feels like a file permissions issue. Can you change the output.txt path to your desktop or somewhere else and see if the output file is correctly written? If so, you'll want to check the read and write permissions for your mame folder. If not, the user executing mame may not have high enough permissions in general. Try running it as administrator to check. If not those, then I'm not sure what's going on.
  3. It looks like that specific output.txt file doesn't exist and isn't getting created. I'd double check that it's there. if it is there and the mame.ini file is being written to correctly then I'm not sure what's going on. As a final effort, you can uncomment the lines that print some variables (remove the # in front of lines that begin withWrite-Output) and run the script in powershell's IDE to see what's going on.
  4. He's talking about an arcade cabinet. He'd just wire his cabinets side buttons (if that's what he has) into the PACTO board. You can wire as many buttons as you want to the same pacto buttons. So, he could have a button from his arcade controls wired to X and also have a side button used for pinball wired to the same X port on the board just fine. I do this for physical coin slots as well. They are wired into the SELECT port along with the normal arcade select/coin buttons.
  5. I still use an IPAC for keyboard and mouse/trackball/spinner. But vpinx uses xinput just fine for controls FYI. You just bind them in the options menu.
  6. Oops. I meant that I recommend the PACTO xinput boards over old-school IPAC boards that typically require intermediary software to turn its (very old) dinput controls into xinput controls. The pacto board makes controls "just work" with today's emulators and regular PC games. I've had zero issues with it This is the one me and my friends use: https://pactotech.com/en-us/products/copy-of-pacto-tech-4000t-4-player-control-interface-for-arcade-cabinets-supports-xinput-protocol
  7. Sorry, I've been busy. Try asking chatgpt how to write a regex to match the exact line you have in your config. Otherwise, if your displays won't ever be two digits again, just use the original script but update it once first, manually.
  8. Glad you got it working. If you aren't using that line already (with {1,2}) then yeah, use it but modify the DISPLAY part to this just in case: '(DISPLAY\d{1,2}\s)'
  9. Yeah so I'm not talking about files at all. Forget about that. In the output of the script on screen, you need to look at the blob of the ini it's going to write to a file later. You'll need to tell me if that looks right not. Check if the right display is in the right spot or not.
  10. Oh, there's nothing to change in any files. There output you see if just temporally in memory. Does the output look right? Is the correct display where it should be in the output of the script? If this is confusing, let me know and I can share some pictures later.
  11. You want to look at the first output of the ini file ( the Write-Output that was near primardisplay yhat you uncommented) and make the that the DISPLAYXX is set on the correct ini line. It's showing what it WOULD write to the ini file if you could (seems like yo can't right now). So it should be set correctly there. I think the line in the ini that should be chanhed us display 1 or main display. I can't remember off the top of my head. The second ini i suhhest to uncomment us literally just reading in the mame.ini file and showing you what it is, unedited. You can comment that back out for now since you know that's working.
  12. Ok. Hopefully that works when he unlocks it. If it still doesn't, you'll want to check on that Write-Output uncomment above to confirm that the main display line is being updated before it even tries writing to mame.ini. This is not the same thing as the DISPLAY14 line you're seeing.
  13. Is it correctly setting the display14, or whatever it is now, too? You'll see it printed via the first Write-Output I showed above.
  14. It might be because you have two digits in your displayname. Try changing this: $content = $content -replace '(DISPLAY\d)',"$primarydisplay" To this: $content = $content -replace '(DISPLAY\d{1,2})',"$primarydisplay" And uncomment this out right below it (remove the #) to see if it worked: #Write-Output $content If that worked, then it should write it correctly to the mame.ini file. If that's not working then double check that it's reading in the mame file by uncommenting the Write-Output line here: #Read in mame.ini $content = Get-Content -Path 'E:\Launchbox\Emulators\MAME Lightgun\ini\mame.ini' #Write-Output $content
  15. So strange that I created that almost a year ago and no one said anything. It seems to be getting attention in the past couple days, though. If you can't get it to work, post in that thread and I'll try to help!
×
×
  • Create New...