JoeViking245

I can't attest to no-intro sets as I've never used them. Assuming you're using MAME as your emulator, are any of the Software Lists NES games working? Or none at all? If using a different emulator, which one? Of MAME's softlists I've imported, NES is the only one I use MAME for. And without issue. I'm sure I had a good reason for using MAME when I set it up that way years ago, but don't remember exactly what it was. For all other MAME softlists I've imported, I use either RetroArch or a stand-alone emulator. again, without issue. Though I really should be using no-intro for cart-based systems.

You're welcome. If you have a non-merged full set (vs. merged or split), these side-effects of MAME will not disappear. Best case-in-point example is scanning for added ROMs where the Source values are different because of where/how they are respectively obtained. How I handle the MAME updates is, after getting the update pack (156 ROMS in .261 to .262) and running them through ClrMamePro, I'll read through "whatsnew.txt". If there are new games I feel I 'must have' in my LB collection, I'll manually add them (which doesn't happen super often). For any removed ROMs, if they're must haves, I move the ROM to a 'Removed ROMs' folder and make note of the MAME version in which it last worked. (I only have one or 2 of those.) I ignore renamed ROMs because most the time they came across a different variant of it and rename the old one (game.zip --> gameA.zip) and name the 'new' one "game.zip". No harm. No foul. No loss. Games they rename without having a new one to replace are probably not in my collection anyway. You should have no issues.

These 2 particular games are 'relatively new' additions to MAME and have not yet been categorized into LaunchBox's Metadata. In fact, don't see them in the database either. When using the MAME Full Set Import Wizard, LaunchBox doesn't really even look at your physical ROMs (other than to count them to see that you have a [near] full set). It uses your rmame.exe to create a list of ROMs that version includes, then imports from it, based on your filters. If your set is a merged or split set, scanning for removed ROMs is going to notice that all clone ROMs are missing. As mentioned, the Full Set Import Wizard works differently than other [regular] import wizards. Regarding duplicates being created after scanning for added ROMs, I'm not entirely sure what all is involved in that process (as far as what exactly is cross-checked. Source may very well be one of the checks.). That said, because of the uniqueness of MAME, it's not advised to use that feature for MAME ROMs. Your 1st "Information" screen shot game came from the Full Set Import in which the Source came directly from the 'list' created by mame.exe. The 2nd one is most likely from the Scan for Added ROMs, where the Source is truncated, and I presume came from the LaunchBox database. Again, because of the uniqueness of MAME and its ROMs, scanning for added or removed ROMs for the "Arcade" platform is not advised (for reasons in which you've discovered). For adding ROMs (i.e. with a MAME updated release), rerun the Full Set Import Wizard. For removed ROMs, it's not very often that MAME will remove games with its updates. And with over 3000 games in your Arcade platform, you probably won't even notice. But if you do, select the game in LaunchBox and delete it there.

It's not possible using this [threads] application. Additional Apps (the versions not 'displayed') don't have a property to indicate it has RetroAchievements. So there's nothing to filter to.

Right below Search should be a combination (dropdown) box. Click the right side of it to get it to drop down 'the list'. On that list, scroll to and select Platform.

That would be like combining Nintendo Gameboy, Gameboy Color and Gameboy Advance into one platform.

Another way to 'update your ROMs' in LaunchBox is to edit the ../Data/Platforms/platform_name.xml file and do a Find/Replace to change all .cue to .chd. Just make sure LaunchBox is closed and done saving any data in the background, before editing.

Unfortunately, not an option. As you noted, the backglass server as well as VPX itself stores data in the Windows registry. That's a personal preference. You can just put all tables (and their dependencies) in the Tables folder. Personally, I think it's ugly. And if it's not yet, it will once you start accumulating more tables. I create subfolders in the Tables folder for each table. Then for tables that are in a series or have different versions, I'll create sub-subfolders. Example: Batman

I was hoping one of the developers would chime in. I doubt it has to do with images as they're showing. It's the text to the right of the image that's 'having issues'. You are using the original Default Theme. Correct? Not a modified theme? Have you tried using a different theme to confirm that 'the issue' is only with the Default Theme? The only other thing I can think of is that maybe a font size got changed. Try going to Tools, Options and resetting the defaults.

There's a plugin that'll do all that for you...

In the Metadata section.

Not saying there's not a possible bug, but it should show. This is viewing "All" with a 'filter' using the Default theme (same as you). Showing logo and Platform name.

That's what I'm using too. The only thing I can think of is: when using this controller, after loading KRULL, press TAB and verify that Input settings for P1 RIGHT STICK/xx are set like what's in the above screenshot. If the right-stick is still not throwing, at all, manually set (reset) those 4 directions to the right joystick. If after manually setting it and it still doesn't throw, then I really don't know why this is happening to you. As for PS controllers, I don't touch the stuff. So can't help there.

Using the default input settings, it's throwing ('shooting') correctly in all 8 directions for me. If moving UP (Left stick Up) and throwing RIGHT (Right stick Right), it throws to the right. If moving UP (Left stick Up) and throwing UP/RIGHT (Right stick Up-Right), it throws to the upper-right. If moving UP (Left stick Up) and throwing UP (Right stick Up), it throws up. etc. Just make sure you're being deliberate with your right stick movements. i.e. Make sure you're moving the stick straight UP and not slightly to the right of UP.

If you have a button on your panel assigned to a mouse left-click, use the trackball to move the cursor and double-tap the button over your BigBox shortcut on the desktop. My panel has 3 buttons for mouse clicks, but don't think that's very common. If you don't have a dedicated mouse left-click button on the cab, you could assign a shift function to one of the existing buttons for left-click. This might be the cleanest way and might actually be useful, in general. Pretty sure you can't assign a macro to button presses on encoders. An alternative 'macro' would be to create an AutoHotkey script that will start when you turn on the cab (launch at startup). The script can be made to detect a certain button press or button-combo press and start BigBox. What's in the script will depend on how your board is configured. Keyboard or Xinput mode. And of course, which button(-combo) you want to dedicate to starting BB.

One way I know of is: Depending on the Theme you're using, when viewing the games, go Left or Right with joystick (or arrow keys) and select the 'hamburger menu' (left of the letters, next to the search icon). In the popup, select Favorite and Is True. Apply.

There won't be any log files for that. What platform/emulator? Though there're several ports for 1941, I'll assume Arcade/MAME. Can you share some screenshots: Go to Tools, Manage, Emulators, select the emulator you’re using for MAME and provide a screenshot of the following sections: Details Associated Platforms Select one of your Arcade (MAME) games (i.e. 1942) and click Edit (or press Ctrl+E). Provide a screenshot of the following sections: Metadata Launching Emulation

Did some testing this morning and was able to recreate the Unhandled Exception error. My Setup: Controller Wireless Xbox 360 Cemu 2.0-65 Remember main window position un-checked Emulator settings (LaunchBox) Default Command-line Parameters "-f -g" (without quotes) Running Script: Esc::WinClose, ahk_exe {{{StartupEXE}}} Exit Script: blank (as in empty. Nothing there) LaunchBox and BigBox (mapped separately) Pause: Button6 (Back) What did work (No error in LaunchBox and BigBox) Exiting the with Escape (keyboard). Which is lame because who plays Wii-U with a keyboard? Exiting the game from the Pause Menu. Mapping the button-combo Exit Game (LaunchBox) and Close the Active Window (BigBox) to Button7 (Right Shoulder) + Button6 (Back) [note the order] Exits using the button-combo. (LB & BB) What didn't work (Unhandled Exception error) mapping a controller button-combo to exit If I mapped my controller Exit Game (LB) and Close the Active Window (BB) to Button6 (Back) + Button7 (Right Shoulder) [reversed from above], pressing them (in that order) it would go to the Game Pause Screen. (NOT exit the game). Select Exit from the Pause Menu would throw the error. Clicking any of the 3 buttons (via mouse) in the message box would close it and exit the game. Theory being, don't bind Exit Game and Close the Active Window with the Back ('Pause') button 1st. However this theory is thrown out when @Oniontears said he didn't have Close Active Window bound to anything. Note: Entering the Pause Menu 'normally' and then selecting Exit Game from there [still] worked in this scenario without issue. What made didn't work turn into did work (using Button6 + Button7 [in that order]) Disable the Game Pause Screen. But I was able to "brake it" by pressing Button6 + Button7+Button7 (hold 6 and double tap 7). Causing the Unhandled Exception error to appear. Last test ('experiment') Remove controller mapping for Exit Game (LB) and Close the Active Window (BB) altogether. (Which sucks because you most likely want those for all other emulators) Put in the Running Script: ; Needed to exit with Escape AND when exiting from Pause Esc::WinClose, ahk_exe {{{StartupEXE}}} ; Left Shoulder (5) THEN Right Shoulder (6) 1Joy6:: If GetkeyState("Joy5") WinClose, ahk_exe {{{StartupEXE}}} The Exit Script is still blank and the Game Pause Screen is enabled. This worked in both LB and BB. Button-combo, Escape and Exit Game from the Pause Menu. But the button combo is scary because if you're playing some intense game and 'smashing buttons', you'll likely exit the game. Take away: When mapping a button-combo to exit the game and it doesn't work, try reversing the combo. ..and you must press the buttons in 'that' order Same is probably true for a button-combo mapped for anything else (like Pause). If the combo works sometimes and error other, watch the caffeine intake and careful the double-tap. Get creative and map (or script) different button combos. Experiment a little. Try not to use the 'Pause' button when mapping the Exit Game combo. (or use with caution) Anything else you can discern from my ramblings. Observation: if the "Esc::" escape sequence is in the Running Script, the game will Exit from the Pause Menu's Exit Game even with the Exit Script section being blank. Conversely, if it's not in the Running Script (and Exit Script is still blank), it won't. Unless you add to the Exit Script "WinClose, ahk_exe {{{StartupEXE}}}" (without quotes).

Ya, all the suggestions given were geared towards stand-alone MAME. In the case of Arcade machines, RetroArch will "work" (as you eventually got it to [nice tracking down the issue, BTW]), but stand-alone MAME is what's strongly recommended.