JoeViking245

Since you can load a profile before a game starts under Running AutoHotKey Script in Edit Emulator, try adding something below what you have like Process,WaitClose,mame64.exe MsgBox,,, hello world Of course replacing the Hello World line with your Load_BB_Controller_Profile_Command_Line.

Replied under other post in Auto Hot Key Scripts

You can try... in 'run before starting game..' Process,Wait,cxbx.exe Sleep,2000 ;this is buffer that may need to be longer send,{F5} send,!{enter} ...but I don't how you'd get it to wait until you're ready to quit to have it send send,{F6} send,!{F4}

@andreasrochaWhat did you end up doing to get it working properly?

I'm highly convinced that if you can run a program (any program) from the command prompt (directly or through a batch file), you can run it through LaunchBox. In your Mame - Edit Emulator - Details tab, is your "Use file name only..." un-checked? I'd never tried running SNES through Mame before and got intrigued. I set it up like you showed with no luck. So I created a new emulator "Mame-SNES" with the default command line parameters "snes -cart" and it worked. I looked to see what was different between the 2 and Mame had that box checked whereas Mame-SNES did not. I un-checked it MAME and it was then able to load.

Try deleting your retroarch.cfg file (actually, make a backup.. i.e rename it). When you restart RA, it'll generate a new one. https://forums.libretro.com/t/solved-retroarch-not-respond-to-keyboard-respond-to-controller/10943/2 If that doesn't work: See note 5) here. (granted, this is for a per core configuration. But hopefully will shed some light). http://www.rlauncher.com/forum/showthread.php?1421-RetroArch-Input-Mapping-for-Keyboard And if you want to get real crazy, edit retroarch.cfg and set the values to like those here. https://gist.github.com/Monroe88/0f7aa02156af6ae2a0e728852dcbfc90 If you still have issues, attach a/some screenshots for us to look at.

You are very welcome. Ya, there really isn't a way (that I'm aware of) to 'know' if a program has completely loaded. It can only check that it's started/running. And like you said, load time can vary depending on what else is working in the background. But at least there's the catch to make sure it has focus so we're not sending keys to another program that may pop up while waiting. ...which makes line 3 a little less 'optional'. If 9000 (9 seconds) for sure works, you can always try to trim it down to 8500 or 8800 or 8602 or 8150... you get the picture. Hey, in this fast paced world why wait 9 seconds when we can get away with just 8.602 seconds. lol

That's how RetroArch is, unfortunately. I know there's several if not many posts on this site asking similar questions about RA (with answers). You can search around. Or go straight to the source. http://docs.libretro.com/guides/input-and-controls/

So I re-read your post... I think this is more what you were actually asking for. Srry 'bout that. Process,Wait,notepad.exe ;wait here until 'my_program.exe' is running Sleep,8000 ;wait for 8 seconds WinActivate,ahk_exe notepad.exe ;set (make sure) my_program is the active window send,{right} ;press the right arrow key send,6 ;press the number 6 key (optional) Line 3 just makes sure that "Right" and "6" are being sent to the program we were waiting for. Just in case other programs take focus during the 8-sec pause.

I kind of get lost in log files... but are you installing this on your Desktop? "C:\Users\redve\Desktop\New folder (8)\"

#j:: ;press Win+J to start Sleep, 8000 send, {right} Process,Wait,notepad.exe Sleep,1000 send, 6 return This assumes that when it ('notepad') opens, it has focus. If it's possible to be already open.... you'll want some more checks and balances in the code. The 2nd sleep is just a buffer to make sure 'notepad.exe' is fully there. Probably can be omitted, but a good safety net. You know. It's Windows and all. Line 1: Can be deleted if you don't need a hotkey. BTW, J is for JoeViking. ?

Yes! I have an I-Pac-2 in my cab as well and also use an Xbox 360 controller. Set up your LB/BB for both cab buttons (aka keyboard input) and controller input. You can set up your emulators the same way. RetroArch example:What RA is calling the "User 1 B button", I can press button 1 (labeled A) on my controller OR on my cab, the left-side-controls "2" button (which through I-Pac is assigned to the "ALT" key).

@kal9000 tell us more about your cab. For example, my cab uses I-Pac/2 to control all the buttons. Which are all basically keystrokes on the keyboard.In BigBox, the Player 1 button (top row, left) acts as Select and the Play/Pause (top, middle) acts as Back. The Play/Pause button (assigned to "P" on the keyboard) also pauses the game to bring up the LB/BB Pause screen. Granted, to hit "Enter", you press 'Player 1 + Player 1 Coin' (top 2 left buttons) and to hit "Esc", it's 'Player 1 + Play/Pause'. But that's how it's assigned in I-Pac. Also for BigBox, I assigned the 'Player-1-Controls - Button 1' (lower left green button) to Start Game. Vs. when looking at the game you want to play, press Select (which brings up the games menu) and pressing Select again to Play. This assignment doesn't interfere with in-game play. Again this is for cab controls. Now if you're talking about handheld controllers... never mind. ?

Not sure if it's work with LaunchBox pause screen... but have you tried redirecting the pause button/command in you specific emulator? The problem I think is most the buttons are tied up to be used to play an actual game. Hence the hold button which actually adds more functionality to ones' controller.

Options. Controller settings.Go down to emulated Wii Remote and Configure.Set device to ...Keyboard Mouse.Then start assigning buttons etc. i.e. (in the pict.) next to "A", click "Button A" then hit the button on your cab you want to be "A". Let's assume you use button 1 on your cab. When you click "Button A" then hit cab button 1, it'll probably say "Ctrl" (or 'Control' or 'Left Control'....) D-Pad on a cab is kind of a pain, so I'd leave those be. Go to the Motion Controls tab and do like you did with "A" for Point assigning Up, Down, Left, Right to the joystick. Do that on the Extension tab as well for Stick. Be sure on General and Options tab, Nunchuck is selected under Extension.

@XC-3730C Can you show us your Supermodel.ini file? My thinkin' is "it's just gotta work." Open Supermodel.ini in a text editor. Highlight all (Ctrl+A) and copy (Ctrl+C). In your reply here, click the Insert Code 'button' (<>) and then paste the contents (Ctrl+V). Also, there's a newer version of Supermodel that's not on their main download page. I'm not sure if it'll make any difference here, but there is a 7.5 year spread between the two. The latest can be found on their forums here. It's the 1st link in the tread "SVN 775 Release". The OP was in 2016, but the link is newer. If you right click Supermodel.exe, and select Properties, look at the Date Created. (SVN 775 is the March one)

Sorry to hear it's not working. That's weird though that in the menu (I assume you're talking the games' menu like when you're selecting [right trigger/gas] a car and/or level) it does work, but not during the game.

Ya, I was looking at that so I tried it both ways but both seemed to work. Glad it's working now! ?

Reading through the following, you can use either to launch. I tried Party Zone and it was a no go probably because I don't "own" it. Fish Tales is free, and that did work. That's why I asked to check it. Don't know what else to check.

Without changing anything, try launching Fish Tales (through LaunchBox).

Yes, it will go directly to the specific table. The Emulation tab has nothing extra. Only thing I can think of is double check that you have the same emulator settings. the path to Steam.exe the command line (best to do a copy & paste) Two boxes checked ("No space..." and " "Use file name only...") and under "Associated Platforms" tab.....assuming that's what you named the Platform.

For the individual table, point to the pxp.And for the emulator, have the command line be -applaunch 442120 -table_

That works great for Star Wars! Thank @Lordmonkus! For the Input, Star Wars uses the AD Stick whereas Operation Wolf uses a Lightgun. So I think the Analog Controls don't really do much for a lightgun. Maybe kind of an apples and oranges thing. @LMD75 in mame.ini, just below joystick_deadzone is joystick_saturation. By default it's set to 0.85. Try changing that to 1. It's seems to help some. Either that or with all this testing, I'm getting more gentile with the control stick. lol

I just tested Operation Wolf with my 360 controller. The default Lightgun X/Y Analog settings on mine were for the left joystick (JOY1 LSX/Y) and ya, it was majorly wonky! In game, I went to settings [tab] and Input (This Machine). I change the lightgun to the right joystick, and now the right joystick was wonky (as should be expected). BUT the left joystick was able to control the crosshairs and was working smoothly. ????? This was done when launching it through LaunchBox. I exited LB and ran it directly through Mame and with the lightgun still set to the right joystick, the left didn't do anything and the right remained wonky. So what I think is happening... is maybe the "new" command line in LB -keyboardprovider dinput has something to do with it. I went back and set the lightgun to <None> for both X and Y (just press Del). Direct through Mame no joy (no pun intended). Launching through LB, the left Joystick was working smoothly (and the right not doing anything). I also tested in BigBox with the same results. Setting them to JOY1 you do get the 'snap-back' to center screen when you let go. Setting to <None>, you do not (when launching though LB). Also, setting to <None> and launching through LB, when you go to settings [tab] and then go to Analog Controls, any adjustments you make to the lightgun settings actually do something for the joystick. This is good. So, Kind of a bizarre 'fix', but seems to work here.

It looks like MK4 was last updated (Jan 2013). So somewhere between Mame revision 0.148 (Jan 2013) and 0.149 (June 2013) . (Assuming where I'm looking at is telling me correctly) So that's probably where the life bar and visual glitches you see with 0.139b weren't quite fixed yet. Although it's still not perfectly emulated. But is playable. It also requires the device file tms32032.zip.