DJ_GLiTCH

I won't spam the channel with the massive changelog, but I have added many new features that may be useful to some of you, particularly the command line automation (headless mode). Don't forget to check in every once and a while for updates that add new features via the Configurator app.

I have now released a "Configurator" app that can be used to install my MAME State Output project, which is now a single native MAME plugin, that will automatically install, update, and configure everything in one click. The beta label will be removed later this week when the Configurator hits v1.0.0 (currently v0.9.3). I would highly recommend downloading the latest Configurator release from my GitHub and use that to automatically install and configure state output support in MAME. The Configurator app will automatically migrate an existing installation that uses my old Lua scripts to the new MAME Plugin architecture as well. The Configurator app will also handle all future updates automatically, which means you spend less time tinkering and more time playing. I hope you all enjoy this new plugin. 🙂

For Supermodel3, they need to enable network output support for states first, which I believe is being added natively via the following pull request: Add network output compatible with MAME. by tbreckle · Pull Request #303 · trzy/Supermodel (https://github.com/trzy/Supermodel/pull/303) As for which games do and don't support state outputs natively for Model 3, that I'm unsure of, and I don't know if Supermodel3 supports LUA scripts in the same manner as MAME (or if it does at all). I will look into this in the future, but for now I think it'd be best for me to focus on finishing all MAME games first before looking into Supermodel3 games. If you know that LUA scripts are supported in Supermodel3 then I can maybe take a look at things sooner, but it'd take a lot of time for me to learn how to map memory addresses in a different emulator environment and make sense of what I'm looking at, so I wouldn't expect anything for this anytime soon unfortunately.

@Benoid I have just released the latest version on GitHub, if you wouldn't mind confirming whether this works better for you now and whether the aspect ratio command is needed in the defaultLG files for HOTR still or not? Many thanks in advance.

Thanks @Benoid for letting me know. Could you confirm if this change was needed in the end to fix your aiming precision, as well as let me know what version of MAME you were/are using? I'll need to test this change with some other users (to confirm it doesn't negatively impact Sinden users, etc.), but for now you can update your defaultLG files to use the attached version (which includes the ">AspectRatio_4:3" change). I'll be uploading another major update within the next few days, so please check my GitHub page every now and then to make sure you get the latest version. All of the tweaks and bug fixes to the underlying script are just about complete, and there's a few rom specific fixes as well. 🙂 defaultLG (Universal MAME LUA Script) - 2026.04.06.zip

@Benoid I've just read up on the HOTR documentation for commands (https://hotr.6bolt.com/pmwiki.php/GameFiles/Commands), and maybe you can try this for aspect ratio to see if it helps: AspectRatio_16:9 This command tells the light gun that the screen aspect ratio is 16:9. Usually used right after ‘Open_COM’ or right before ‘Close_COM’. AspectRatio_4:3 This command tells the light gun that the screen aspect ratio is 4:3. Or simulating a 4:3 screen on a 16:9 screen. Usually used right after ‘Open_COM’ or right before ‘Close_COM’. I have attached an example for duckhunt and lethalen which uses the command ">AspectRatio_4:3" and they don't crash for me. If you could let me know if this works and improves the gameplay, I can update the other defaultLG files for the other games. duckhunt.txt lethalen.txt

The txt files that go into your HookOfTheReaper\defaultLG folder are not meant to be edited, as the only commands that should exist within these files are already included. When it comes to aspect ratios, I have a 4k monitor (16:9), and I just set MAME to automatically adjust the aspect ratio depending on the game. That way the calibration for my monitor remains 16:9 at all times, and when a game has a native 4:3 ratio MAME will automatically display the game in 4:3 aspect ratio and create "black" borders (and you can use bezel artwork to fill in the black borders using game specific artwork). Is the aspect ratio something you used to use before, or are you just trying to implement it for the first time? By default you should be good to go with MAME, as I've never had to touch the aspect ratio settings at all.

Thanks @Benoid, appreciate the feedback. Would you mind elaborating on what you mean by the game.txt file? If you can take some screenshots and share an example that will help me understand what you mean, cheers.

So glad this post helped someone. I was chasing this issue for so long and it was so simple to fix in the end. 😄

Glad to hear it's working. I just released a new version today as well, so please be sure to use the latest files as they include a few bug fixes. 👍

Copilot is wrong. You just need the tools I mentioned earlier, and to ensure you have set "output network" in your mame.ini file.

No worries, hope you enjoy it. Not all games/ROMs in MAME require these LUA scripts to enable recoil/rumble in light gun games, only some. What you need is any version of MAME, but I always recommend the latest version (currently 0.285), a tool called Hook Of The Reaper (HOTR), which is needed to communicate between games and your light guns to control recoil/rumble/etc, and then my files, which enable support for games/ROMs in MAME that don't typically support recoil/rumble. To install my scripts, you just need to copy the relevant files into the relevant MAME and HOTR folders, which are already in the correct folder location in the downloaded file. Hope this helps.

This tool is designed to enable simultaneous output of network and windows in MAME without modifying the core MAME source code. To achieve this, the MAME Bridge NetToWin tool will handle "output windows" as an additional add-on when you have "output network" set in MAME. The reason this tool exists is because natively you can only choose "windows" or "network" in MAME settings (mame.ini), not both at once. To enable simultaneous dual output, configure MAME to output "network" (find the relevant "output" line in "mame.ini" and set this to "output network"). If "network" output is detected on 127.0.0.1:8000 for MAME, then this tool will interpret all state outputs received by the TCP server and relay them to windows by simulating the native MAME "output windows" method, which is used by tools like LEDBlinky or MameHooker. I have previously proven that simultaneous dual output is possible natively in MAME with a custom build of MAME (I called this "output netwin"), but as I am not confident in my ability to maintain this code within the main release branch of MAME, I thought this tool would work better as it can be used with all future vanilla releases of MAME without code customisation. MAME Bridge NetToWin (Download Link / GitHub): https://github.com/djGLiTCH/MAME-Bridge-NetToWin LEDBlinky (https://www.ledblinky.net/) Specific Notes: If you are using LEDBlinky (v8.2.2 or lower), then you will need to ensure all ROMs are loaded with the command "-output network" when launching ROMs with MAME, as LEDBlinky can revert the output setting in mame.ini from "network" to "windows" (even if mame.ini is set to read-only). This may not be an issue in newer version of LEDBlinky if they make use of network output functionality in MAME, but while it relies on windows output this will remain the case. Launchbox Launch Parameter Settings: The steps below will add network output to MAME when launching ROMs through Launchbox. This will override whatever output setting is used in your mame.ini file (which is needed since LEDBlinky can change the mame.ini setting to "output windows", but we need "output network" for HOTR, and MAME Bridge NetToWin will relay the messages from network to windows so LEDBlinky can work as intended in parallel). 1. Open Launchbox 2. Select Tools > Manage > Emulators 3. Select MAME (it will highlight once selected), then select "Edit..." 4. Select Details in the left pane, then in the "Default Command-Line Parameters", you will want to add "-output network" (without quotations), then select "OK" 5. Close the Emulator window 6. Restart Launchbox (not needed, but good practice) General Notes: I would recommend using this tool with Hook Of The Reaper or OutputHooker over MameHooker, as that is what I have tested with. Hook Of The Reaper (https://github.com/6Bolt/Hook-Of-The-Reaper) and OutputHooker (https://github.com/PolybiusExtreme/OutputHooker) use "network" output, which is why LEDBlinky can access the "windows" output created by this tool, and both can work together without any communication clashes. Feel free to experiment with other combinations, but please know I may not be able to assist with any issues you may encounter.

Update 1 June 2026: I have now released a "Configurator" app that can be used to install my MAME State Output project, which is now a single native MAME plugin, that will automatically install, update, and configure everything in one click. The beta label will be removed later this week when the Configurator hits v1.0.0 (currently v0.9.3). I would highly recommend downloading the latest Configurator release from my GitHub and use that to automatically install and configure state output support in MAME. The Configurator app will automatically migrate an existing installation that uses my old Lua scripts to the new MAME Plugin architecture as well. The Configurator app will also handle all future updates automatically, which means you spend less time tinkering and more time playing. I hope you all enjoy this new plugin. 🙂 Old text below from back when the project was one Lua script and ini file per game (not recommended anymore): I just wanted to share my project with everyone that aims to add light gun force feedback to a bunch more MAME games via LUA script and is compatible with Mamehooker and Hook Of The Reaper (preference is to use HOTR as that is what I'm personally more familiar with). It operates under a universal script I made that has enough settings to be useful for any game, so the community can use it and add support for more games, which I can add into future releases. The list of supported games is available in the "Progress Notes" text file on GitHub, and in the release description. Please read the GitHub readme for more details. It's still in the final beta testing phase, but it should be finalised very soon. I hope the community finds it useful. https://github.com/djGLiTCH/MAME-LUA-SCRIPT-STATE-OUTPUTS EDIT: While Hook Of The Reaper now includes MAME LUA scripts with each new release (as of v1.3.0), they are still not as complete as the ones I have released on GitHub (in both features and list of games), so I would still highly recommend using my project instead.

No worries, and thanks for the appreciation. It sounds like my tool may not be needed for all that much longer, as LEDBlinky may have support for network output soon, but it's still handy for use today and for any versions of LEDBlinky v8.2.2 and below (and for those who do not want to upgrade from working copies of older LEDBlinky versions of course). The steps below will add network output to MAME when launching ROMs through Launchbox. This will override whatever output setting is used in your mame.ini file (which is needed since LEDBlinky can change the mame.ini setting to "output windows", but we need "output network" for HOTR and my tool will relay the messages from network to windows so LEDBlinky can work as intended in parallel). Open Launchbox Select Tools > Manage > Emulators Select MAME (it will highlight once selected), then select "Edit..." Select Details in the left pane, then in the "Default Command-Line Parameters", you will want to add "-output network" (without quotations), then select "OK" Close the Emulator window Restart Launchbox (not needed, but good practice) Some screenshots of these steps are below with red highlights of what you need to do: