JoeViking245

Edit the game that's missing the image, go to Media - Images and select Download Media and then uncheck all boxes except Screenshot -Gameplay and click Download. If you have EmuMovies setup, be sure to uncheck/check the boxes on that tab as well before downloading.

@The_Keeper86 Sort answer: no. Medium answer (which is actually a question): is there a command of sorts (or program) you can run that will actually "turn off" a controller? Longer answer: assuming the answer to my question is yes, the easiest way to do this is to create a batch file that starts BigBox, waits for it (BB) to close and then runs the "program" to turn off the PS4 controller. @echo off d: cd "D:\LaunchBox\Core" start /w "" BigBox.exe cd "D:\PS4_Controller_Folder" start "" "Turn_Off_PS4_Controller_Program.exe" If you're feeling really ambitious, you could create a plugin and use the API call "BigBoxShutdownBeginning" and then run your "turn off" program there.

I don't use RocketLauncher, so I'm not in a position to say anything good or bad about it other than what I'd get out of it isn't worth the pain it is to A) figure out how to set it up, then B) actually get it setup, and lastly C) have it actually work. I think @Koroth's script is the cleanest way to do this. I don't know if BetterJoy needs to be running BEFORE Dolphin starts, but as I think about it, it would make sense that the Running AutoHotkey Script setup for the emulator would execute before having the emulator launch the game. Koroth, have you personally used this as the Running AutoHotkey Script for starting (and stopping) BetterJoy? (you didn't say and I know nothing about BetterJoy )

This may be a longshot..... look for the files this plugin is supposed to produce inside your ../LaunchBox/Core/obs/ folder.

Either you've been a bad apple in the past, or you got your VPN goin' on. Not sure if they have any 'ad-blocker' blockers or not.

If you can find 0.225, you're really not missing much. But if you search around, I'm sure you'll find something.

It's not like other emus where an older revision works better for certain games. So go for 0.226. ?

This sounds most likely to be a rom - emulator mismatch. More recent revisions of the emulator are not necessarily backwards compatible with older roms. That's why it's stressed to have a matching romset and emulator. Another possibility is a missing (or mismatched) device file. In the case of Marvel Super Heroes, "qsound_hle.zip" (device file) is also needed to run the game. Again, making sure you have the matching revision for the rom and the emulator.

As you discovered, mixing different revisions of MAME roms and the MAME emulator itself is never a good idea. Since (I assume) you have them matched now, you shouldn't need to update anything. (well.... maybe your settings ) Since they now work directly in MAME (thank you for checking that 1st), MAME itself should be good to go. Now make sure the MAME emulator in LaunchBox is setup correctly.Double check the Emulator Application Path (verifying you're point to your 'good' copy of MAME). Check both "Don't use quotes..." and "Use file name only...". Depending on how old your MAME revision is, you may need to remove the "Default Command-Line Parameters:". (I don't recall what revision that parameter became available). In the Associated Platforms tab, bake sure the Arcade (assuming that's what you called it) Platform is there [and typically "Default Emulator" will be checked]. Now make sure your games in the Arcade Platform are all pointing to the correct folder and file for the Rom File (in the "Launching" section). And lastly (hopefully), in the "Emulation" section, be sure the chosen Emulator is the same one you setup (above).

You sure? Morbid curiosity got and had to check it out (c64_cass). Ended up using c64 -autoboot_delay "2" -autoboot_command "load\n" -cass Then press {Scroll Lock} to enable the Keyboard - Partial Emulation, then press {F2} to "Play" the tape. You can bypass needing to press {Scroll Lock} by adding "-ui_active" c64 -autoboot_delay "2" -autoboot_command "load\n" -ui_active -cass But you can't bypass the need to press {F2}. Unfortunately. BTW, "3D Pinball".... {F1} starts the game, Left flipper is {Left-Alt}, Right flipper is {right-Control}, and {F4} launches the ball.

It's working with 11.7. The [Application] Path to the Game [file] contains the word "rom".

If after it loads, all you need to do is type "run" and press Enter to get it to start, you can try the Default Command-Line Parameter for that Platform... c64 -autoboot_delay "2" -autoboot_command "run\n" -cass (not tested) MAME loads the 'game'. Then "-autoboot_delay" tells it to wait "2" seconds. Then after those 2 seconds, "-autoboot_command" tells MAME to type in "run" and then press Enter ("\n"). You may need to increase the delay time ("2"). Depends on how long it takes to get to the "blue prompt screen".

Open up vsav.zip and see how many files are in it. If there's more than 21 (or 22) files, you probably then have a merged set. Which would mean the clones are inside the Parent zip file.

The 'white' ones are Parent roms and the 'grey' ones are Clones [of the Parent]. So looking at Vampire Savior, the "Euro" one is the parent rom ("Romset: vsav" aka "vsav.zip" in your roms directory). The "Asia" is a clone of "Euro" with the Romset: vsava (aka "vsava.zip"). We you have "Unfiltered" selected, you see all [MAME] available roms. And then selecting "Available" you see what you have in your roms directory. Since some of these are disappearing, I'm guessing you have a non-merged set. The ones that work in MAME and not in LaunchBox, verify that LaunchBox is pointing to the correct Romset (zip file name) that you have. ("vsav" vs "vsava"). If you specified a Region priority when importing, it might be pointing to the USA version ("vsavu.zip").

@Drybonz You did a MAME Arcade Full Set Import using 0.225? Did it import "Super Bubble Bobble" by Sum Mixing using the Parent rom "sbubsm"?

I personally have never worked with theme creation. But I imagine any data you can get using the LaunchBox API can be added anywhere in your theme, for any View you choose. But again, I'm not familiar with Themes and am not sure if they can access the API the same way that plugins do. Assuming you have this plugin installed and the games Custom Fields have been populated with the [Field] Name "Hi-Scores", you can use the API's ICustomField Interface to get your local [top 3] high scores. "Local" meaning the top scores stored in your game(s) that are on your computer. You would need to see how the Community Leaderboard is accessed in Themes that have it integrated. (assuming that's what you mean by "top 3 high score") But even then, being able to parse the 'top 3' out of that may or may not be possible. Then if Themes do have access to the API, you can parse the 1st (of 3) [Local] high scores from the Custom Fields. If that's not possible, you could create a UserControl similar to what was done for the 'sister' plugin to this one (and/or BigBox's built-in "View High Scores" for the Community Leaderboards). But again, I don't know if/how you can access the data for the Community Leaderboards or even the built-in "View High Scores" User Control. NOTE: As stated in the description, I only worked on the 'easy' stuff. @jayjay did all the xaml magic. So I can't really be of any help with that and Jay hasn't been around since July. So if I'm getting what you asking about, I think what you're wanting to see is already available in the details pane for Arcade games (Local high score(s) and the LaunchBox Leaderboards). As well as through BigBox's built-in "View High Scores" User Control and the above plugins' User Control to "View Local Hi-Scores". But you'd like to see it in a more 'elegant' manner.

Where there's a will, there's a way. The current LaunchBox MAME metadata is for MAME revision 0.224. But you're all correct, nowhere is it spelled out which release LB is currently using.

I think the button numbers (0, 1, 2, 3...) are a sorta 'standard of the industry'. Besides "1" is a lot easier to remember than the [more precise] Decimal value 4096. aka, Hexadecimal value 0x1000. (I'm sure there's a similar reasoning for Direct Input.) But to call the 4 main buttons A, B, X, Y doesn't really work when all you have is X, circle, square, triangle. As for detecting specific button presses from within a plugin is well beyond my knowledge.

This is not generated by MAME by default. LB would need to do something like "mame64 -lx >list.xml" to generate the 236MB file, then parse from that. Are the 'missing' 100-ish files all 'brand new' to MAME 0.225? As in maybe the LB data file is still on a previous version?

"Temp" and "none" worked on my 'test' of 54 MAME roms (dated April 2019. So whatever versions those came from). [All 54 were imported properly] Using LB 11.7. Just thinking out loud.. maybe a [partially] corrupt data file or something? Maybe reinstall 11.7 (over the top of your existing one)? If you select a different emulator, will they "import" (all 130)? Obviously they won't be named properly...

With all else equal, shouldn't this be Scrape As: Arcade?

Here's some discussion about getting and setting the MAME static ID's.

Set it up in MAME how you want it. "Save Configuration" [in MAME]. Exit MAME. Edit mame.ini to have writeconfig = 0.

All softlists used in MAME will require a Default Command Line Parameter. And they're all different. For the NES it's "nes -cart". Some will also require a BIOS file and some, 1 or more device files. NES (I believe) doesn't require any 'extra' files. Are these other systems working when ran from inside MAME itself?

I think the method you're using is spot on. However I may be biased as that's exactly how it do it. I have my cab connected to my TV (actually to the AVR, then TV) via HDMI. [The cab monitor connects uses the DVI port on the video card] I used a program called MonitorSwitcher (found on SourceForge [it's free]) to create my [custom] different monitor configurations, and then load those from a batch file. The configs used here are "cab-only" (single monitor, only using the cab's monitor) and "TV-Primary" (dual monitor, with the TV as the primary monitor). @echo off f: cd "F:\Monitor Switcher" start /w "" "MonitorSwitcher.exe" -load:TV-Primary.xml cd "F:\LaunchBox\core" start /w "" BigBox.exe cd "F:\Monitor Switcher" start "" "MonitorSwitcher.exe" -load:cab-only.xml You'll note here, I start BigBox from the ../Core/ directory. Reason being... running F:\LaunchBox\BigBox.exe will actually start - exit - then start F:\LaunchBox\Core\BigBox.exe . So you can imagine what that does to the "start /w" in the batch file. Also note the double double-quotes after "start /w". Off hand I forget the what's-and-why-for's they're there. But (without looking it up) I'm sure it's for a good reason. And because it uses the HDMI to the TV (primary), the audio it automatically redirected. Love the use of "DisplaySwitch". I was not aware of that 'command line' option. Thank you. The problem I have with that is the HDMI port on my video card takes to spot of Monitor 1. So not sure how that would work.