JoeViking245

Oh holy snap!! I never even thought about using FreeFileSync for that! [Homer Simpson "DOH!" forehead slap] And it's way prettier than my little batch script. lol I've been using that program for a couple years now, but guess I never really explored beyond a one way mirror for a backup. I assume it's as simple as selecting "Update >" in the synchronization tab.?. And I suppose if someone was dead set on sticking with batch file, they could run FreeFileSync from a [batch] command line. lol BIg Thanks in return!!

Keeping inline with the simplicity of batch files, once it's initially set up... assuming A) you keep a full (updated) set in one place [well maybe 2. one for roms and one for chd's] and B) no new roms/chds are added... you can use Windows built-in (Windows 7 and above) robocopy to copy only the updated roms/chd to your LB/BB 'subsets' Rem robocopy "f:\source_directory" "d:\destination_directory" /LOG:"logtest.txt" /XL /R:10 /W:10 Rem Rem /LOG:file Redirects output to the specified file, overwriting the file if it already exists. Rem /TEE Log output to both the command prompt (visual monitoring) and the specified file in /LOG Rem /XL Copies a file from the source directory only if a file of the same name already exists in the destination Rem /R:n Specifies the number of retries on failed copies. (The default is 1 million.) Rem /W:n Specifies the wait time between retries. (The default is 30 seconds.) Rem Rem robocopy "F:\Roms\MAME\Roms" "D:\LaunchBox\Games\Naomi\Roms" /LOG:"RomsLog.txt" /TEE /XL /R:10 /W:10 pause robocopy "F:\Roms\MAME\CHDs" "D:\LaunchBox\Games\Naomi\CHDs" /LOG:"CHDsLog.txt" /TEE /XL /R:10 /W:10 pause /XL is the key ingredient here. Copying only the roms from Source that are (by file_name.exe) in the Destination folder and are newer. This way it will only copy the updated roms, saving (at least a little bit of) time. /LOG (optional) is nice if you want to see what and how many were updated/copied. pause is also nice if you want to see what /LOG produces, but as it happens (happened). Of course the caveat being if new roms or chds were added to MAME. But hey, that's what whatsnew.txt is for.

Glad it's working now! Any chance you figured out an autoboot command for APF? I created (edited actually) "apfimage.ini" and put it in ../Mame/ini/ # # SCRIPTING OPTIONS # autoboot_command cload\n autoboot_delay 5 # # CORE INPUT OPTIONS # ui_active 1 You need to press Enter when it first loads (within 5 seconds per the 'delay' setting), then it automatically sends "cload]" (the ] (bracket thingy) being APF for Enter which translates to \n ). After that press F2 (don't need to hit Scroll Lock because ui_active = 1) to start the tape/cass. Then when it's done loading enter in run] (I think that's what it was) to start the game. I tried \n just before cload, but no joy. Apparently Enter and ] are 2 completely different inputs. I never figured out how to send F2, which would be really nice for this and a lot of other soflists!

1) Sure you can. However I just ran some tests and it seemed to work just using the Associated Platform arguments. At least on a select few games I tried. 2) Any chance your Platform isn't named exactly the same as your Associated Platform? 3a) This usually means the rom is not located within in MAME's rompath (mame.ini). Another cause is there's something wrong in the command line. Though it does look right. See item #2. 3b) It sounds like it's executing something like "mame64.exe centiped". Which would launch the Arcade version. I still think it has something to do with item #2. 3c) If you got a kick-arse score on APF Centipede, would it upload the score? No. That would be pretty dang funny though. lol If APF were able to save high scores, it would not be in the same format as it's Arcade Machine counterparts' hi/nvram file. So hi2txt wouldn't be able to read it. The MAME leader boards don't look at the Platform name, but rather it looks for the MAME emulator. (I'm sure there are several good logistical reasons for this). And then from there, looks for games (by rom_name.zip) that are supported in hi2txt.

Sorry man. Just trying to help. But if "not" was supposed to "now"... glad it's working.

For inside of a batch (.bat) file REM your start mousy command here start /w "" demule.exe REM your quit mousy command here For inside of an AHK script ; your start mousy command here RunWait, demule.exe ; your quit mousy command here Both of these will run demule.exe, and then ONLY after it closes/exits, run the "your quit mousy command here".

Can't go giving away all my secrets, but I will share that one... Remember, when trying to figure something out, always start your searches using the "KISS Principle".

You're welcome. FileMove in AHK lingo is synonymous with "file rename'. Basically you're 'moving' the file from folder "A" to folder "B" . In this case, we're "moving" it to the same folder (from "A" to "A") but with a different name. AKA, renaming it. And then in the next step, using FileCopy we're making a copy of the games config file (thus keeping the original in tact [just in case]), and copying it to the default config folder, while at the same time renaming it to "qt-config.ini". (BTW, RockStar - Silver Ice. The only way to go. )

If it's a matter of inserting something into an existing script to backup/copy/restore the ini file, i think you're looking for something along these lines currGame := %1% ;%1% or however you get the games name to this script defConfig := "D:\Emulators\Yuzu\Config\qt-config.ini" defBackup := "D:\Emulators\Yuzu\Config\qt-config.bak" gameConfig := "D:\Emulators\Yuzu\Config\Games\%currGame%.qt-config.ini" if FileExists(%gameConfig%) { FileMove, %defConfig%, %defBackup%, 1 ;rename to .bak, overwrite if it exists FileCopy, %gameConfig%, %defConfig%, 1 ;copy in the game.ini } and then after exiting the game FileCopy, %defConfig%,%gameConfig%, 1 ;copy the game.ini back (because it changes during gameplay???) FileMove, %defBackup%, %defConfig%, 1 ;restore original config file Or compile those to run Before game starts, and After game exits. respectively.

@CtinD Are these custom game config ini files something that could be loaded from a command line parameter? I have never used RL and have no idea what yuzu is, but if it were possible (bear with me here..) Say we have the emulator myEmu.exe it takes the command line -yuzu and then the name of the rom mario.zip myEmu.exe -yuzu mario.zip And say this, by default, loads qt-config.ini. Is there a command you can put in there to load a custom config file? Say something like -config=? myEmu.exe -yuzu -config=mario.qt-config.ini mario.zip And if so, could you then put in a custom command line for each game, replacing both instances of "mario" with the name of the game? If "Yes", then there's a quick, easy solution. (easier than editing each and every game) If "Yes, but I use an AHK script, and the games name would have to change in the script", then there's a relatively easy solution. If "No! You have no idea what you're talking about.", then never mind. I tried. ?

You're welcome. Glad it worked for you. That's probably the most common means of exiting a game and closing its emulator. And usually the hotkeys you setup in LB/BB to exit a game are tied to it. Look at your other emulators and how they're exiting (beyond 'Select' + 'Triangle'). Do they have a Running AutoHotkey script? What do they look like? Can you copy or transpose them into your MAME emulator?

I'm confused by this. Most all emulators require a command line of sorts. For example to load/run Atari 7800 in MAME via LaunchBox, under Edit Emulators in the Associated Platforms tab, you set the Default Command-Line Parameter to "a7800 -cart".And then in the Details tab, check the boxes for "Don't use quotes..." and "Use file name only...".Of course you need to have everything setup and working in MAME itself before attempting to run it from LaunchBox.

No worries at all! Helps keep me on my toes. lol At one point I had thought about incorporating the importing of metadata. Then something about "reinventing the wheel" popped into my head. And then the thought "Sweet! Less work for me." I'm just glad I was able to figure out what I did wrong and now have it working with LB .NET Core betas. Otherwise we might be waiting for "The List" to make its' way down to item #26. Provided it didn't get bumped once again.

@sundogak It wasn't me! I swear! lol (thanks for having my back @neil9000 ) Seriously though, for clarification of what actually this softlist importer plugin does add to LaunchBox... A new Platform (named per your choosing) A new 'game' (Title/Name per MAME's hash file) The 'ApplicationPath' to that new 'game' The 'DateAdedd' (DateTime.Now) The 'DateModified' (DateTime.Now) The associated Emulator [Id] (per your choosing [i.e. MAME]) And checks the box "Broken" (if you imported an "unsupported" [per the hash file] 'game' ) For the selected Emulator: Add's a new Platform Add's the command line for the new Platform (to the best of my ability with the given [hash file] information) And checks the "Default" box The rest of 'what you see is what you get' is all LaunchBox. I suppose I could force a "check" to the "Non-Arcade" field. Though I'm not sure if it would 'stick' after importing metadata. In fact I don't know if "Broken" sticks or not. Hmmm.... (Out of morbid curiosity) I wonder what your audit would look like before you add metadata and media (to the new softlist Platform). Obviously you won't have any images, videos or manuals. But are the extra boxes there? Also, if you update you metadata/media in Arcade, will those "new" boxes now show?

The code works to send Alt+F4 using "BACK" on the XBox 360 controller. (tested) But I don't use Demul to be able to test in it. Try adding a $ in front of Joy7. $Joy7:: Send !{f4} ExitApp Also change Return to ExitApp that way the script won't stay active.

Are you placing the code in the "Running AutoHotkey Script" tab? (Not in the "Exit AutoHotkey Script" tab)

That was something I wrote about a year ago before I knew about being able to modify the startup screen. Honestly, I think you'd be better off going that route (follow the link). Not sure if this'd work, using this script, you could try to manually set the startup screen to say 5 seconds so the game doesn't come up so fast.

PlatformDeviceImage = D:\LaunchBox\Images\Platforms Image = Super Nintendo Entertainment System\Device\SNES Controller.png SplashImage,%PlatformDeviceImage%\%Image%,b Sleep, 5000 SplashImage,off Adjust the path/image accordingly. But with a little bit of reading, this would probably suit your needs [and end up looking a lot] better.

What controller encoder is your cab using? (i.e. I-Pac2) The encoder is what has assigned P1B1 to Ctrl. You could create a 2nd config through/for the encoder and then in LB add "Automatically run before main application" load config 2, and then "Automatically run after..." load config 1 .... for the respective games. But that's kind of a pain. Plan B: In the "Running AutoHotkey script" for the emulator, add $LCtrl:: Send, {LButton} Problem is, every game using that emulator will be affected by that. Though you could create a "new emulator", point it to the same exe, but add in the Run Before/Run After. Plan C : Create and save that AHK script and then compile it, and then add that to "Run Automatically Before..." for the games. But off hand don't know how to make that go away after the game exits. It's possible (and probably easy), but would need to look into it. Plan D : Add another button to your cab dedicated to left click. This has been real handy on my cab, but add 3 (if you can) for Left, Middle and Right clicks.

Glad you got it to work. Now you know where to look. That's where you'll find most of those types, but some Device files are still with the software lists such as scharger.zip for the Atari 2600. You probably know how to set them up. Here's how to save them.

For standalone MAME Software Lists (such as bbcb) add to the command line "-cfg_directory". For example the 'game' "ABC" would look like: mame64.exe bbcb -cfg_directory "d:\emulators\mame\cfg\bbcb\abc" -flop1 abc.zip Your custom controller config files for this game are now saved like so. d:\emulators\mame\cfg\bbcb\abc\bbcb.cfg d:\emulators\mame\cfg\bbcb\abc\default.cfg In LaunchBox, edit the game, go to Emulation, check "Use Custom Command-line Parameters" and fill in this: bbcb -cfg_directory "d:\emulators\mame\cfg\bbcb\abc" -flop1 So it looks like thisNote: "abc" in the command line is the name of the games romfile. So you'll need to do this [custom] for each game. If you decide you like stand alone MAME over RA-MAME, you can quickly add this command line to all games at once using the Bulk Custom Command Line Editor plugin (which can automatically add in the games romfile name in there for you). It can be found in the Downloads section. The command line parameters can also be stacked to do something like: bbcb -cfg_directory "d:\emulators\mame\cfg\bbcb\abc" -autoboot_delay "2" -autoboot_command "*cat\n\n\n\n*exec !boot\n" -flop1 Oh.... and change the path in the above command line(s) so that points to your ../mame/cfg/..... folder. MAME will automatically create the folders (i.e. "bbcb" and "abc") if they don't exist.

@Flickumbicus The files you need to be looking for are apple2ee.zip, apple2e.zip, a2diskiing.zip and d2fdc.zip which you can find in with your 'regular' MAME rom set. (regular vs the Softlists sets).

Go here. scroll down just a little until you see this and click "Download"

@Drakkorcia What revisions are you hearing the pitch differences in? As recent as between 0.221 and 0.222? If they changed something in centiped.cpp that changed the pitch (which seems odd they would), instead of having 2 completely different MAME installs, you could just have multiple copies of the compiled exe in a single MAME setup.Like Neil said, you'll still need to setup a 'new' emulator in LB pointing to the respective exe. However if doing it this way doesn't work to fix the pitch, may want to look inside mame.ini. It's possible something changed in the Core Sound Options or the PortAudio Options or somewhere else. If it is something in the ini, create a 'centiped.ini' file with the known good settings, put it in the ini folder and use the current .exe revision.