wolfenstein0099 Posted Sunday at 02:42 AM Posted Sunday at 02:42 AM 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 Sunday at 03:42 AM Posted Sunday at 03:42 AM 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 Sunday at 01:13 PM Author Posted Sunday at 01:13 PM 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 Sunday at 02:50 PM Posted Sunday at 02:50 PM 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. 1 Quote
wolfenstein0099 Posted Sunday at 04:11 PM Author Posted Sunday at 04:11 PM (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 Sunday at 04:15 PM by wolfenstein0099 1 Quote
JoeViking245 Posted 15 hours ago Posted 15 hours ago For anyone [else] following, this was resolved after a couple DM's back and forth. The Fix: install a fresh copy of MAME and install MSOP onto it. U-Shoot: There's a little writeup I did here on how to add it as an emulator in LaunchBox. https://forums.launchbox-app.com/files/file/5633-demulshooter-auto-launcher/?tab=comments#findComment-20827 But before you can start adding games to use this "emulator", you need to set the games up in U-Shoot itself. Complete instructions for setting up games in U-Shoot can be found on its Wiki page. If you setup the games per the Wiki and the outputs work when being launched from the U-Shoot GUI, then add the 'emulator' and games per my writeup linked above, and the outputs don't work when launching a game from LaunchBox... I really don't know what to tell you. Quote
wolfenstein0099 Posted 14 hours ago Author Posted 14 hours ago 54 minutes ago, JoeViking245 said: For anyone [else] following, this was resolved after a couple DM's back and forth. The Fix: install a fresh copy of MAME and install MSOP onto it. U-Shoot: There's a little writeup I did here on how to add it as an emulator in LaunchBox. https://forums.launchbox-app.com/files/file/5633-demulshooter-auto-launcher/?tab=comments#findComment-20827 But before you can start adding games to use this "emulator", you need to set the games up in U-Shoot itself. Complete instructions for setting up games in U-Shoot can be found on its Wiki page. If you setup the games per the Wiki and the outputs work when being launched from the U-Shoot GUI, then add the 'emulator' and games per my writeup linked above, and the outputs don't work when launching a game from LaunchBox... I really don't know what to tell you. Thanks again Joe! Just for more context I reinstalled hook of the reaper as well and readded the files in the plugins folder. With u shoot I ran the xml for the game after I made u shoot an emulator and I got this.... If I try to run u shoot as the emulator it just crashes. Quote
JoeViking245 Posted 14 hours ago Posted 14 hours ago First thing's first... When you select the game in U-Shoot and click the play icon , does it launch and play? All the outputs work? 14 minutes ago, wolfenstein0099 said: With u shoot I ran the xml for the game after I made u shoot an emulator and I got this.... Edit the game and in the Emulation section, check the box to use an emulator then select the emulator you added for U-Shoot. 9 minutes ago, wolfenstein0099 said: If I try to run u shoot as the emulator it just crashes. Then something's not setup correctly. Edit your U-Shoot emulator (in LaunchBox) and share [legible] a screenshot of the Details section. Quote
wolfenstein0099 Posted 13 hours ago Author Posted 13 hours ago 27 minutes ago, JoeViking245 said: First thing's first... When you select the game in U-Shoot and click the play icon , does it launch and play? All the outputs work? Edit the game and in the Emulation section, check the box to use an emulator then select the emulator you added for U-Shoot. Then something's not setup correctly. Edit your U-Shoot emulator (in LaunchBox) and share [legible] a screenshot of the Details section. Hey Joe so u shoot was working yesterday but I tried to launch it by itself and getting this error. Now I made sure hook of the reaper isn't running in the background and it's running as admin. Same error every time I boot it. Quote
JoeViking245 Posted 13 hours ago Posted 13 hours ago 6 minutes ago, wolfenstein0099 said: it's running as admin Don't run things as Admin! If you have to do that, you'll never get things running in LaunchBox. That's not a threat or a warning. It's a promise. (just sayin' ) 8 minutes ago, wolfenstein0099 said: Same error every time I boot it. I'll have to resort to the proverbial "have you tried turning it off and back on again?" (restart the computer) Quote
wolfenstein0099 Posted 7 hours ago Author Posted 7 hours ago 5 hours ago, JoeViking245 said: Don't run things as Admin! If you have to do that, you'll never get things running in LaunchBox. That's not a threat or a warning. It's a promise. (just sayin' ) I'll have to resort to the proverbial "have you tried turning it off and back on again?" (restart the computer) Hey Bud! So I restarted my PC since error wouldn't stop. Fixed the issue and the crashing. Now boots great with the hook. Tried house of the dead 2 and confessional mission on Namoi. I recently updated flycast and was having lag with my shots on confessional mission. I had this problem before with my Nvida GPU. I think I went into the Nvida app and added flycast and change settings to fix the gun lag. Forgot what I did. I'm going to try and figure it out tonight. Was working today. Thanks for that secret sauce. Now it's all working, almost. Thanks bud 1 Quote
JoeViking245 Posted 6 hours ago Posted 6 hours ago 46 minutes ago, wolfenstein0099 said: added flycast and change settings to fix the gun lag. Forgot what I did If you re-figure it out, be sure to share. Quote
wolfenstein0099 Posted 4 hours ago Author Posted 4 hours ago (edited) 2 hours ago, JoeViking245 said: If you re-figure it out, be sure to share. Thanks bud! Yes, I figured it out. I set cap of my frame rate to 60. Not unlimited, prefer maximum performance, also set my vsynic to fast to fix the flickering and in flycast. I have vsynic set to on, vulcan and per pixel. Now the gun works great and no screen tearing as well. Thanks a million bud! I'm even playing target bravo through u shoot with force feedback. Adding info LB after dinner. Also my standalone crisis games work now with hook of the reaper. Gonna have a blast now! Thanks a million Joe. Once I reonstalled everything it fixed all my issues! Edited 4 hours ago by wolfenstein0099 1 Quote
JoeViking245 Posted 3 hours ago Posted 3 hours ago 19 minutes ago, wolfenstein0099 said: Thanks bud! You can call me Joe. (Bud reminds me of Jeff Spicole. lol) 23 minutes ago, wolfenstein0099 said: I set cap of my frame rate to 60. Not unlimited, prefer maximum performance, also set my vsynic to fast to fix the flickering and in flycast. I have vsynic set to on, vulcan and per pixel. Now the gun works great and no screen tearing as well. Thanks. Was this all in Flycast? Or in the NVidia Control Panel. 26 minutes ago, wolfenstein0099 said: Thanks a million Joe. Once I reonstalled everything it fixed all my issues! (much better. ) Always glad to help. Glad to hear it's fixed. Quote
wolfenstein0099 Posted 1 hour ago Author Posted 1 hour ago 1 hour ago, JoeViking245 said: You can call me Joe. (Bud reminds me of Jeff Spicole. lol) Lol sounds good Joe! 1 hour ago, JoeViking245 said: Thanks. Was this all in Flycast? Or in the NVidia Control Panel. So the 1st part is the Nvida control panel then when I said flycast. It was for flycast. I really hope this helps someone else. I had it working the 1st time but I did update it and seems like the same settings. 1 hour ago, JoeViking245 said: (much better. ) Always glad to help. Glad to hear it's fixed. Your a good guy, Joe! Always helping me. Really appreciate it. I could never get it to work with mame before but now it's working great. Well expect for T2. Thanks for everything and if you have any other questions. Fire away so we can help someone else. 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.