JoeViking245

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.

If they all work fine running directly through the emulator(s), and not through LaunchBox, 1st thought is double check the rom's location in Edit game(s). (stranger thins have happened...) Next verify the emulator settings in the Emulation tab. Edit the emulator selected. Verify the emulator path is pointing to the correct (updated) location/executable. You mentioned looking for a file in a folder in a zip.... Could it be somehow "Extract ROM..." inadvertently got checked?

@XC-3730C I got curious and thought I'd check it out 1st hand. Here's what I found: ---edited--- (corrected) Right trigger is JOY1_RZAXIS_POS Left trigger is JOY1_ZAXIS_POS Just add those respectively in your Supermodel.ini file on the lines InputAccelerator = "KEY_UP, JOY1_RZAXIS_POS" InputBrake = "KEY_DOWN, JOY1_ZAXIS_POS" Adding those to the ini file and using the following command, for me the xbox 360 triggers works for gas/brake. Supermodel daytona2.zip -input-system=xinput I got to messing with the Force Feedback feature and it works great for those 3 games they list. I've add to my Supermodel.ini file: [ Global ] ; my oddball monitor default resolution XResolution = 1680 YResolution = 1050 FullScreen = 1 ; add force feedback for the xbox 360 controller ForceFeedback = 1 XInputConstForceThreshold = 30 XInputConstForceMax = 100 XInputVibrateMax = 100 The resolution and FullScreen can be in the command line or here. AND... thanks to you, I discovered a new emulator that opens up new games. Games I apparently already had (in my Full Set) that otherwise didn't work. Thank you. Gotta love learning something new everyday!!!

Your talking the triggers right? and not the shoulder buttons? Per that link I had (and under the "Basic Usage" link under help) the shoulders are 'built-in' but to get the triggers to work, you need to add to the command line -input system=xinput Plan B is to just configure them manually. supermodel -config-inputs -input-system=xinput ..and follow the prompts. Plan C... check their forum https://www.supermodel3.com/Forum/index.php

For LT and RT, try JOY1_RZAXIS_NEG JOY1_RZAXIS_POS You'll also need to add -input-system=xinput to the command line per https://www.supermodel3.com/AdvancedUsage.html

For CriticalZoneV2, in Visual Studio I've never been able to see the top half of the screen (preview) due to some error or another. However you can still make changes to the code and it does work in LB/BB without issue. You just don't get the WYSIWYG effect and can't make adjustments on the upper half by dragging. The Default theme you can. It just lacks the <!--comments--> CZ2 has to help show you where you're at.

Assuming "xpadder.exe" is located in "D:\RocketLauncher\Profiles\Xpadder\", to load a profile you need the run the program and tell it the profile name. (Also the "/w" might be causing the blank screen issue. So take it out.) start "" D:\RocketLauncher\Profiles\Xpadder\xpadder.exe "D:\RocketLauncher\Profiles\Xpadder\AAE\_Default\p1.xpadderprofile" /M Did you already have a batch file to start AAE that looked like...? : D:\Hyperspin\Emulators\AAE\aae.exe %1 "D:\Hyperspin\Roms\AAE\%1.zip" If it works, great! But it doesn't need the last part. The 1st "%1" tells it the roms path and filename already. (On this line, keep "/w" in.) start /w "" D:\Hyperspin\Emulators\AAE\aae.exe %1 The 'Batch file emulator' pict you show looks fine. So "AAE Batch.bat" would look like start "" D:\RocketLauncher\Profiles\Xpadder\xpadder.exe "D:\RocketLauncher\Profiles\Xpadder\AAE\_Default\p1.xpadderprofile" /M start /w "" D:\Hyperspin\Emulators\AAE\aae.exe %1 start "" D:\RocketLauncher\Profiles\Xpadder\xpadder.exe "D:\RocketLauncher\Profiles\Xpadder\AAE\_Default\blank.xpadderprofile" /M For Daphne, you said you already use a batch file to load/run the games that looked like: Daphne.exe %1 vldp -fullscreen -x 1920 -y 1080 -framefile "D:\Hyperspin\Emulators\Daphne\framefile\%1.txt" Adding start /w "" in front of it shouldn't (wouldn't?) cause a syntax error.

When I 1st tried, I was having a heck of a time to get it to work. Like you, I tried the URL with and without the trailing slash, with and without the http: and so on. I'm not saying anyone is as slow as me ?, but it wasn't 'til I realized that the Steam Import Wizard wasn't showing an "example" of the URL, it was actually providing the 1st part of it... that I got it to work. So in the empty field, I only needed to enter just my Steam user id name.

I really don't know anything about the Daphne emu or xpadder. A quick search looks like to load the profile you need: "D:\<path_to>\xpadder.exe" "D:\RocketLauncher\Profiles\Xpadder\Daphne\_Default\p1.xpadderprofile" /M ....just reread your comment about using a batch file..... why didn't you say so.. lol Edit your batch file to read... start /w "" "D:\<path_to>\xpadder.exe" "D:\RocketLauncher\Profiles\Xpadder\Daphne\_Default\p1.xpadderprofile" /M start /w "" Daphne.exe %1 vldp -fullscreen -x 1920 -y 1080 -framefile "D:\Hyperspin\Emulators\Daphne\framefile\%1.txt" start "" "D:\<path_to>\xpadder.exe" "D:\RocketLauncher\Profiles\Xpadder\Daphne\_Default\blank.xpadderprofile" /M This is assuming that is indeed the command line to apply a profile for xpadder (including the /M). The "/w" after "start" just says 'wait for it to finish it's thing before going to the next line'. We put it on the 1st line because without it, line 1 and 2 will load virtually simultaneously and Daphne might kick in before 'it was told' we're using p1'. Line 3, load profile "blank", won't start until Daphne closes. For the 2nd line, adding in start /w "" you may need to put Daphne.exe in quotes. But nothing else on that line changes. If that all works, we (or you) can figure out how to hide xpadder command-prompt windows that'll pop up.

No. The "Exit AutoHotkey Script" is only for closing (shutting down) the emulator. Not sure what the other one does. ? The alternative to editing each and every game to have a 'launch before' and 'launch after' like what you show in your pict. is to write an AutoHotkey script (or a batch file) that will send the commands that will: load your xpadder profile run the game (** see note) (then when you exit the game) load the blank profile Then in LaunchBox go to: Tools Manage Emulators Add Give it a name (like maybe Daphne Xpadder) Under Application Path, Browse to were you have the AHK or batch file that you created. Put a check in "Don't use quotes.." In Associated Platforms tab, add Daphne. **note: LaunchBox will pass the games name (rom file name) as %1 to the script or batch file. So if you write an AHK script, this line might look like RunWait, "D:\Emulators\Daphne\Daphne.exe" %1 Or in a batch file start /w "" "D:\Emulators\Daphne\Daphne.exe" %1

The only way I've found to do what you're asking to create a new 'emulator' based off a script. Something like: Run, xpadder-load-commandline RunWait, "path_to_Daphne.exe" %1 Run, blank-load-commandline And have that Platforms default emulator be the script. I've only tried something to that affect with Mame and it worked great. 'Worked' (past tense)... actually it still does, but with Mame I can't seem to properly pass "-keyboardprovider" to get the LB Pause Screen to work via the scripted-emu. I think LB need to get that argument 1st hand and it (sorta) can't through a script in this manner. I have not tested this with any other emulator.

VPX and FP are free to use and definitely do work in LB/BB. They are easily imported with a drag-and-drop. Of course you'll need to set up the Platforms and emulators. The BIG issue I think is supporting the import of metadata (which is a lot of what LB/BB is about) as there are no standards for file-naming conventions. For tables or images. If something were figured out, then there'd be the issue of "...hey! I have JPSalas' version of the table, but the scraped image is from Xenonph's table." I don't envy the person who sets out to work on that. For game info (notes), I don't know if IPDB.org is open to allow for scraping. But then that'd only get info about the commercially made tables (vs Originals). As Awesome as it would be, I feel Jason's pain. I'm guessing he doesn't want to add platform/emu defaults if he can't properly support it beyond that ('the Big issue'). Oh the repercussions he'd get from the masses... lol?

The "Exit AutoHotkey script" is used to send whatever key presses are necessary to close the specific emulator. It redirects the Esc key to do this. Since Mame (and many other eum's) already uses the Esc for this, it's not required to add this in. For something like PCSX2, Esc doesn't close it. You need to close the emu, i.e. Alt+F4, or possibly a little cleaner, shutdown or Close the process. Process, Close, {{{StartupEXE}}} To reset your mouse sensitivity after exiting a game, you'll need to add that code/batch file to the games "Additional Apps" and select it to "Automatically Run After Main Application". The only issue with that is you'll need to add that in for every game.

It should be in wherever you installed Launchbox and then sub directory Themes. Of course it is possible that I found it somewhere else a long while back (thus forgot) and put there myself. It looks something like: (hopefully it attached here) Documentation.pdf

Check out the Documentation.pdf in the ..\LaunchBox\Themes directory. There's a link at the beginning for getting started. When you open it (and after watching it) there are links on the right for more videos.

In LaunchBox, go to your Arcade platform (assuming you didn't call it something else), select all games. Go to the Tools menu and select - Export/Copy ROM Files from Selected Games to New Folder... Follow the prompts to tell it where to copy the roms to. As this only copies them and doesn't change anything else, when that's done: Select all games (again). Go to the Tools menu and select - Change ROMs Folder Path for Selected Games... Follow the prompts to tell it where the roms are now located. The caveat is [I'm pretty sure...] it doesn't copy any necessary bios/device/chd files.

I could probably make it so they all change to 0 (zero). ? So, do you mean something like your ctrl+A selecting, edit thing to get to the Bulk Edit Wizard. Then select the "Field" Genre: and under "Value", check Action and also Fighter / 2D and click 'Next', 'Next'? Now I can't attest that it works for "Playlists" though.

@cleverest How about a LaucnhBox plugin that'll do that? ? I recently watched one of @Jason Carr's videos (made 2 yrs ago) about building plugins... ..and thought how cool is that! I've worked with various programming languages (self taught, just geeking around) but never specifically C# or using Visual Studio. After watching the video (rewind-watch, rewind-watch again) and taking notes I was able to recreate the sample plugins he was going over AND get them to work . After going over the Notepad++ resolution (above) and your "user friendlier" comment I started to write an AutoHotKey script. After a while I got to thinking I should probably try to do it the right way. Grabbed my notes for the video, started VS, a little copy/paste, some adjustments, a quick C# search or 2. Build/test/refine a couple times and "Oh Wow! It works!" ...short story long...... It's not 'built-in' per se , but at least plugin-able.

Reset Play Count to zero - Plugin View File Edit: This is now a builtin LaunchBox feature as of release 10.7-beta-1. Resets a games Play Count to 0 (zero). Place the "ResetPlayCount.dll" file into your ..\LaunchBox\Plugins\ folder. *edit* Right click ResetPlayCount.dll, select Properties and click "Unblock". Start LaunchBox. Select just one, multiple or all (Ctrl+A) games. Right-click and then click on "Reset Play Count" located at (or near) the bottom of the popup menu. There is no "Please Confirm" nor "Play Counts have been reset to 0 (zero)" message boxes. It just does it as soon as you click it. (V1.0) *edit* Version 1.1 adds a confirmation message box. ResetPlayCount.dll - 6KB Submitter JoeViking245 Submitted 06/22/2019 Category Third-party Apps and Plugins

Manually reset all PlayCounts in all Platforms to 0 (zero) using Notepad++: In windows Explorer, go to your "..\LaunchBox\Data\Platforms" directory. MAKE A BACKUP OF YOUR xml Documents FILES FIRST! Select all files (Ctrl+A). Right click and select "Edit with Notepad++" Click "Search" "Replace" (or hit Crtl+H) In "Find what:", insert <PlayCount>\d+</PlayCount> In "Replace with:", insert <PlayCount>0</PlayCount> Under "Search Mode", select "Regular expression" Then click "Replace All in All Opened Documents" Save all and exit. \d means any digit(s). + means.... well.... plus. So... look for "<PlayCount>" followed by any number(s), followed by "<\PlayCount>"

Yes. Include the quotes just like where he and you typed it. You can also see it has them in the image (a little above the OK and Cancel buttons).