| Main > Driving & Racing Cabinets |
| fooling with m2emu network |
| << < (68/68) |
| vertex:
--- Quote from: buttersoft on August 15, 2025, 05:04:54 am --- --- Quote from: Endprodukt on August 14, 2025, 04:10:09 pm ---Do you have further information if they made it work? I'm fighting with the same problem of no state change in m2emu. --- End quote --- No, i have not set up FFBBlaster yet! And TBH i'm not sure it's meant to cover M2emu, but maybe it is? I do, however, have outputs working fine with FFBplugin and Outputblaster. All my files for those two elements, and my complete scripts directory from the m2emu folder, are attached. Using these with the 1.1c update by sailorsat gets me working outputs in mamehooker. MY setup is mostly aimed at STCC as that game is my fav, so you might need to try the different DLL files in there and see. The one with ronames in the title will give individual rom ini's in mamehooker, not just the generic m2emu.ini or whatever it is that covers all roms. --- End quote --- Using your m2emu files and the Sailorsat version, Mamehooker works, but when I exit, sometimes the lights stay on. I have to close Mamehooker and restart it. This doesn't happen with Mame. Is there a specific reason for this? Or is there a way to fix it? mamehooker keeps listening to m2emu outputs, but exiting it doesn't delete the information and sometimes the lights stay on. |
| buttersoft:
--- Quote from: vertex on September 16, 2025, 11:00:48 am ---when I exit, sometimes the lights stay on. I have to close Mamehooker and restart it. This doesn't happen with Mame. Is there a specific reason for this? Or is there a way to fix it? --- End quote --- Firstly, glad to hear you got it working :) Secondly, sometimes the lights stay on. I imagine it's because when you exit, the game never sends a message to your arduino or whatever turn off the output. Happens to me with most games. MAME must have a close protocol that sends a 0 or something. And Mamehooker must do so on startup, or just re-initialise the arduino or something. If you really needed to do something about it, you could write an autohotkey script that fires each time you close a problem game, and closes and re-opens mamehooker... That would be the simplest way i can think of to do it. Or maybe your frontend could do it for you, IDK. |
| Navigation |
| Message Index |
| Previous page |