wolfenstein0099 Posted 21 hours ago Posted 21 hours ago I'm having a problem with hook of the repeater and launchbox. Im using u shoot and mame state output project to help with hook of the reaper. Now everything works great outside my launchbox build but when I launch a game, my gun isn't getting the hook. It's only in launchbox. Any ideas of a fix? Quote
JoeViking245 Posted 20 hours ago Posted 20 hours ago 32 minutes ago, wolfenstein0099 said: I'm having a problem with hook of the repeater and launchbox. Im using u shoot and mame state output project to help with hook of the reaper. Now everything works great outside my launchbox build but when I launch a game, my gun isn't getting the hook. It's only in launchbox. Any ideas of a fix? Any chance you're testing against 2 versions of MAME? If the one LB is pointing to is MAME 0.289, M.S.O.P. won't work. One test would be to right-click a game and select Open MAME. Start a game and check your outputs in HOTR. While you're there, in this MAME's GUI, the top of its window will show its version #. If they are indeed and you promise they're the same, show what you have for the command-line parameters (in LB, edit your MAME emulator). It seems to me I had to do something on a per game basis to load the lua script(s) via a custom command-line parameters (in edit game). If nothing above sheds any light, I'll take a look at my cab tomorrow and see if I can find what I did. Quote
wolfenstein0099 Posted 11 hours ago Author Posted 11 hours ago 9 hours ago, JoeViking245 said: Any chance you're testing against 2 versions of MAME? If the one LB is pointing to is MAME 0.289, M.S.O.P. won't work. One test would be to right-click a game and select Open MAME. Start a game and check your outputs in HOTR. While you're there, in this MAME's GUI, the top of its window will show its version #. If they are indeed and you promise they're the same, show what you have for the command-line parameters (in LB, edit your MAME emulator). It seems to me I had to do something on a per game basis to load the lua script(s) via a custom command-line parameters (in edit game). If nothing above sheds any light, I'll take a look at my cab tomorrow and see if I can find what I did. Thanks Joe for the reply. I'm running Mame 288 for my mame emulator inside and outside of launchbox. I'm also using u shoot for flycast. I was playing house of the dead 2 and confessional mission and it worked perfect with u shoot outside of launchbox. So I know it's hooking. Im running hook of the reaper before I even start launchbox or bigbox. It's just not hooking when the game boots. I spent hours trying to use AI on my phone tro try and setup U shoot so I would get the feedback through launch box with house of the dead 2 and CM. I booted up area 51/maximum force cab through launchbox because I know that works but no feedback. Just launching with mame 288. Thanks a million. Would love to get hook of the reaper running through my bigbox build. Quote
JoeViking245 Posted 9 hours ago Posted 9 hours ago 52 minutes ago, wolfenstein0099 said: I'm also using u shoot for flycast. I was playing house of the dead 2 and confessional mission and it worked perfect with u shoot outside of launchbox. So I know it's hooking. I missed the U-Shoot part. 1) So HOTR isn't detecting outputs when launching a game for both MAME with MSOP nor Flycast with U-Shoot from within LaunchBox? aka HOTR isn't detecting any outputs when launching a game from LaunchBox. Let's start with MAME: 2) Is it detecting that a game was even launched [from LaunchBox]? (MAME w/MSOP) 3) Is the game even starting? Or does it just close and go back to LB? 4) You promise that the mame.exe you're testing with is the exact same mame.exe LB is pointing to AND the one you're using outside of LB? I've seen it more-often-than-not that issues like you're having was because the user was testing against different copies of mame.exe. e.g. Outside of LB D:\MAME\mame.exe and inside of LB D:\LaunchBox\Emulators\MAME 0.288\mame.exe 5) In LB when you edit your MAME emulator, in the Plugin Settings, do you have it checked to Let LaunchBox manage these settings? 'Shouldn't' matter. But part of the process-of-elimination. LaunchBox isn't going to block anything that the emulator's trying to do. (just so you know) Suggestions: - Do your testing via LaunchBox. Not Big Box. It's just easier when testing. - Double-click HOTR icon in the taskbar to bring up its window so you can see it. - Start MAME (or press Alt+Enter when it opens) in windowed mode so you can see both it and HOTD's windows. - Or if you have a 2nd monitor, move HOTR to it. - [Temporarily] turn off Startup Screens to help see both windows. - Have LB/BB start HOTR when LB/BB starts. It has a small footprint. 'Hides' in the background. And you'll not ever have to remember. - Add it via Tools < Options < General < Startup Applications - Answer all questions. Note: what I mentioned yesterday about the lua script and command-line parameters, that was for the old version of MSOP. The latest version Just Works™. So disregard. I tested with MAME 0.288 both outside and inside of LB with HOTR and saw this. So I know it works. U-Shoot: That's for another day as it's near-convoluted to setup. But not impossible. Quote
wolfenstein0099 Posted 8 hours ago Author Posted 8 hours ago (edited) 1 hour ago, JoeViking245 said: I missed the U-Shoot part. 1) So HOTR isn't detecting outputs when launching a game for both MAME with MSOP nor Flycast with U-Shoot from within LaunchBox? aka HOTR isn't detecting any outputs when launching a game from LaunchBox. Let's start with MAME: 2) Is it detecting that a game was even launched [from LaunchBox]? (MAME w/MSOP) 3) Is the game even starting? Or does it just close and go back to LB? 4) You promise that the mame.exe you're testing with is the exact same mame.exe LB is pointing to AND the one you're using outside of LB? I've seen it more-often-than-not that issues like you're having was because the user was testing against different copies of mame.exe. e.g. Outside of LB D:\MAME\mame.exe and inside of LB D:\LaunchBox\Emulators\MAME 0.288\mame.exe 5) In LB when you edit your MAME emulator, in the Plugin Settings, do you have it checked to Let LaunchBox manage these settings? 'Shouldn't' matter. But part of the process-of-elimination. LaunchBox isn't going to block anything that the emulator's trying to do. (just so you know) Suggestions: - Do your testing via LaunchBox. Not Big Box. It's just easier when testing. - Double-click HOTR icon in the taskbar to bring up its window so you can see it. - Start MAME (or press Alt+Enter when it opens) in windowed mode so you can see both it and HOTD's windows. - Or if you have a 2nd monitor, move HOTR to it. - [Temporarily] turn off Startup Screens to help see both windows. - Have LB/BB start HOTR when LB/BB starts. It has a small footprint. 'Hides' in the background. And you'll not ever have to remember. - Add it via Tools < Options < General < Startup Applications - Answer all questions. Note: what I mentioned yesterday about the lua script and command-line parameters, that was for the old version of MSOP. The latest version Just Works™. So disregard. I tested with MAME 0.288 both outside and inside of LB with HOTR and saw this. So I know it works. U-Shoot: That's for another day as it's near-convoluted to setup. But not impossible. Thanks Joe. There's defintally something going on with msop and my mame. T2 stopped working even though I have mame in set to network. It also was coming up with an error that msop stopped working. With regular Area 51, virtual cop 1 and 2 and other games. Going to try to reinstall mame tonight and see if I can get the feedback again. Im going to test the dual area 51 cab again and see if the outputs work without msop this time. I was using the latest version and Google said it needs the mesh for those games which isn't even out yet.... Tried an older version and it wouldn't work either. Edited 8 hours ago by wolfenstein0099 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.