JoeViking245

Can you close it from task manager? Try AHK Window Spy and see if you can see something there.

This was kind of mentioned previously, but MAME Software Lists [roms] (vs MAME Arcade Machines [roms] vs PS2 [roms]...etc...) are a unique animal. As you know, MAME uses a shot-name naming convention. i.e. Asteroids is asteroid.zip. Here's why you put them into their own folders... The Arcade Machine rom (file) is named asteroid.zip. The Atari 2600 rom is named asteroid.zip. The ZX Spectrum Cassette rom is names asteroid.zip. See a pattern here? So I suppose you think of the different Consoles (along with Acrade) that MAME can emulate as different 'Platforms'. Which I imagine is how you'd load them into LB.

[alternate method] Open Windows explorer and navigate to the folder that has you "mame64.exe" file (red underline). Click once on the address bar (red dot) and type "cmd" (no quotes) and hit Enter. (Make sure "cmd" is the only thing on the line before hitting Enter)This will open the Command Prompt at the correct location to now enter the command: "Mame64.exe -v cdimono1 hotmario" and press Enter. (again, no quotes)

Maybe add another short Sleep after the RunWait line. Check task manager and see if touchmote.exe is launching a sub process (or something along those lines). Is MAME opening a command prompt window when you run this? [Actually ya, it probably is] Not sure if this'd help with the quitting issue, but it's probably better anyway. RunWait, %comspec% /c "D:\Emulators\MAME\mame64.exe -keyboardprovider dinput %1%",,Hide Did you clear out the Running AutoHotkey script tab? Could it still be running from the above issue? It will attempt to run it only as many times as you tell it to. If you can't find out where/why it's trying to run it twice (which you really should pin point that issue), you could get real crazy and replace that 1st line with something like if !WinExist("ahk_exe touchmote.exe") { Run, "D:\Utils\TouchMote\touchmote.exe" } If all else fails, there's still plan "C". But seriously, there no reason the above shouldn't work.

%1% is a Parameter (or Variable) passed to the executable. In this case it's the rom_file_name (samsho). If you think of it as executing your compiled script from the command prompt, you'd type D:\> MameWithTouchMote.exe samsho "samsho" is the 1st (only) Parameter and the executable program stores that (reusable) Variable as %1% If say you had D:\> MameWithTouchMote.exe samsho astdelux Your compiled script could be like Run, "D:\Utils\TouchMote\touchmote.exe" RunWait, "D:\Emulators\MAME\mame64.exe -keyboardprovider dinput %2%" ;run Asteroids Deluxe RunWait, "D:\Emulators\MAME\mame64.exe -keyboardprovider dinput %1%" ;run Samurai Shodown RunWait, "D:\Emulators\MAME\mame64.exe -keyboardprovider dinput %2%" ;run Asteroids Deluxe WinClose, ahk_exe touchmote.exe Variable. Reusable. Usable in any order. [Of course LB is not going to be passing multiple games to your executable. ]

Ya, I was afraid of that. Plan "C" would be what Headrush69 was leaning towards.... Keep the MAME Emulator unmodified, then for the games add a "Run before Main Application" Additional App that points to touchmote.exe. And then another Additional App that "Run After Main Application" that would either a) point to ../ThirdPaty/AutoHotkey/AutoHotkey.exe and uses the command line D:\path\to\file\ExitTouchMote.ahk or b) point to a compiled copy of ExitTouchMote.exe. Both of which have WinClose, ahk_exe touchmote.exe in it/them. Problem is you'd need to add that for all games in the Arcade Platform. Good thing is, if it's not already built into LB [yet?], there's a plugin in the Downloads area that will "(Bulk) Add Run Before/After Main Application" that adds an Additional Application to more than one game at one time. ....Maybe... ....I might not have uploaded it there. ? (attached) Or just stick with plan "A". Bulk Run Before-After.7z

Hopefully someone with more insight on this will chime in as I'm just grasping at straws. ? Ya, simply leaving dinput off after -keyboardprovider will basically tell MAME to load the keyboardprovider that's called rom_name [whatever the name of the rom is (aka "File") you're trying to load]. I have an Xbox controller as well and (thankfully) haven't ran into this. (no offense) So the full "-keyboardprovider dinput" should not be an issue. My last thought is: in LaunchBox, click Tools, Options... scroll down to Game Controllers and make sure Enable Game Controllers is checked. By default it's not checked.

Plan "B" (afterthought) Set mame64.exe as your emulator. Then in the Running AutoHotkey Script tab Run, "D:\Utils\TouchMote\touchmote.exe" $esc:: { WinClose, ahk_exe touchmote.exe WinClose, ahk_exe mame64.exe }

Maybe your controller (whatever it is) doesn't like to be dinput. Try removing that line from the Default Command-line Parameter.

Add %1% to the end of the Run, mame64.exe.... line. Run, "D:\Utils\TouchMote\touchmote.exe" RunWait, "D:\Emulators\MAME\mame64.exe -keyboardprovider dinput %1%" WinClose, ahk_exe touchmote.exe RunWait will 'pause' the script until the .exe has exited. Then continue [to the next line]. (the quotes may or may not be needed.)

What does your "Default Command-Line Parameters:" look like? Something like this?

No. In fact attempting that may actually cause more problems than do good. The issue here was the plugin looks for Unbroken.Launchbox.Plugins.dll [v11.8 vs v11.4]. Rightfully so, as that's the current release. You might be able to compile it with reference to an older Unbroken.Launchbox.Plugins.dll version (say, 11.4). As I think about it, I haven't updated my plugins in a while and I think they still work. I think the answer it to design for [on] the latest stable release and users be updated to the latest stable release.

VidSnap Scraper plugin is designed around LaunchBox v11.8. When [attempting to] load it in LB v11.4, the debug log will show Could not load file or assembly 'Unbroken.LaunchBox.Plugins, Version=11.8.0.0, Culture=neutral, PublicKeyToken=558191e84f56affc'. The system cannot find the file specified. At least that's what it looks like to me. So I think the solution on this one is to update LaunchBox to v11.8.

Did you unblock the dll file? (right click, properties, unblock) Will probably need to do the exe file as well.

Is "TWORuntimeStandAlone.exe" your Main Application? If so, add another Additional App that'll Run After Main Application.

Unless I missed it in an earlier post, there's the ticket in the 2nd to last line [above]. @Wanderer189 Create a shortcut to your .bat file [that works to do this] that kills the DS4... process. Right click the shortcut, select Properties, then select the "Shortcut" tab. Click "Advanced" and check Run as Administrator". Click OK.... OK. Now in your Running AutoHotkey Script tab, in the $ESC sequence, have it Run, "full/path/to/KillDS4.lnk" Of course changing the path and filename, respectively (too lazy to look back a page. lol). (It'll be similar to what you had before but ".lnk" instead of ".bat") NOTE: that's an "L", not an "I" (eye) in .lnk [.LNK].

Good point! I was just getting to the ['this'] plugins folder, not the LaunchBox root folder. ?

What does the bat file look like?

...also only 2 (3 including the Readme file) files are needed.

There's a multitude of ways to get a directory/folder. The 2 suggested are just a drop in the bucket of the possibilities. The one I threw in may or may not be the best ("correct") way, but it worked. lol

Make a backup of your supermodel.ini file. Then reconfigure your inputs. But instead of inputting what you want, input what you want to learn what it is. So for maybe the first 4 inputs, press the Wii Mote "A". Next 4 press "B" and so on. When done, look in the 'new' supermodel.ini file and match up the inputs you used. Make notes. Restore your backup'd file and edit it accordingly. From readme.txt

In VSScraper.cs, add private string pluginPath = Path.GetDirectoryName(System.Reflection.Assembly.GetExecutingAssembly().Location) + "\\"; In the (4) "Process youtube_dl = new Process();" sections, change: // youtube_dl.StartInfo.FileName = $@"{GetSystemDirectory()}\youtube-dl.exe"; // TO youtube_dl.StartInfo.FileName = pluginPath + "youtube-dl.exe"; And place "youtube-dl.exe" inside the ../Plugins/Vidsnap Scraper/ folder. Then there's no issue with the System32 or WoW-whatever folder issues. Well, it at least worked the one time I tried. ?

When changing this, the line above it (in the ini file) is what will be set to "Reload". InputOffscreen = "KEY_S,JOY1_BUTTON2,MOUSE_RIGHT_BUTTON" ; point off-screen InputAutoTrigger = 1 ; automatic reload when off-screen Since your Wii "A" button reloads, I'm guessing it's mapped (remapped?) somewhere on the "InputOffScreen" line. Shown here is the default [but with "InputAutoTrigger" changed to "1"]. I have no idea how the Wii controllers get mapped, but if it's to "Joy1" (and assuming you didn't change anything on the "InputOffScreen" line) I'd say your Wii "A" button EQUALS JOY1_BUTTON2. But it may be the MOUSE_RIGHT_BUTTON ? [from the readme.txt file...]

@Jocusenz If it's running full screen it should 'fit' to the screen. But you can set a custom resolution per game in your ini file. Example: ; Start Wars Trilogy [ swtrilgy ] XResolution = 800 YResolution = 600 line comment rom_name (include the brackets) X resolution Y resolution In your ini file go to the "Analog guns (Ocean Hunter....)" section. On the InputAnalogGunX(Y) lines remove reference to the JOY1 axis'. ; Analog guns (Ocean Hunter, LA Machineguns) ;InputAnalogGunX = "MOUSE_XAXIS,JOY1_XAXIS" ; analog, full X axis **ORIGINAL ;InputAnalogGunY = "MOUSE_YAXIS,JOY1_YAXIS" ; analog, full Y axis **ORIGINAL InputAnalogGunX = "MOUSE_XAXIS" ; analog, full X axis **REVISED InputAnalogGunY = "MOUSE_YAXIS" ; analog, full Y axis **REVISED

Yes. LaunchBox sees the [Daphne] batch file 'exit', so then runs the Run After Main Application. Try a "wait" instead of "exit". @echo off start /w "" daphne.exe %1 vldp -framefile vldp_dl\%1\%1.txt -blend -ignore_aspect_ratio -blank_searches -min_seek_delay 1000 -seek_frames_per_ms 20 -homedir . -fastboot%bank% -nocrc -noissues -noserversend -sound_buffer 2048 -fullscreen -x 1920 -y 1080 This way, the batch file will 'hang around' until Daphne exits, and THEN close itself. Alerting LB to execute the Run After Main Application app. (note the pair of Double-Quotes after /w) In fact, you could eliminate the "Run After" batch file altogether by putting its' code after the "Start /w" line. (if you wanted to)