JoeViking245

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.

Um... that looks kind of like a RetroArch config file. Not [stand-alone] MAME. Where exactly did you find it?

The 'good' screenshot you show is text vs images (Clear Logos). So if it was bad, then there'd really be issues. You illuded towards that you tried the Default theme. That was going to be my next suggestion (and the one recommended to do this type of debugging with). If your Display settings are set to 100% and the 'Recommended' resolution, I'm inclined to lean towards it being a video-card-type issue. RE: the recommended resolution thing, I recall on my new LG tv that when I first hooked my cab up to it, the recommended setting was something other than 1920x1080. Without paying attention to what it was that 'it suggested', I switched it to 1920x1080. Might be something else to look at. What are your computer specs (including video card) that you have hooked to the TV? I presume you're connecting via HDMI.?. Does the PC you're using have its own monitor you can test on? Does it show the same results?

With your non-merged set, you have all the ROM files in one folder. Don't you? They should be. And if obtained from a 'reputable' source, file names should be good. Galaga (parent ROM 'galaga.zip' [Namco Rev. B]) does also require 2 device files 'namco51.zip' and 'namco54.zip'. But even the clones (right-click, play version...) require at least namco51. Most clones require both. Those 2 device files should [already] be in the same folder with all the MAME ROMs. In one folder. If you switch to a merged set, the device files [the files within namco51.zip and namco54.zip] will be inside galaga.zip. As well as files for the 6 clones.

Also, for your Default Command-line Parameters, try adding -rompath %romlocation% after -keyboardprovider dinput and see if that helps. -keyboardprovider dinput -rompath %romlocation%

Thanks! That works. Well, if you do a little backtracking. Using MAME revision 0.226 mame64 m5 -ram 36k drops

Saw an example on their GitHub site showing to use -e Then point to the eboot.bin file. fpPS4.exe -e "D:\LaunchBox\Games\PS4\undertaleextract\Pvini-CUSA09415-Undertale\CUSA09415\eboot.bin" Other parameters found:

Nah, it's still there. Un-check the box. Or set everything (or just some) to None.

What do you have your display scaling set to (Windows Display Settings)? If you set it 100%, does it still show the clear logos partially blacked (blocked) out? Is the display resolution set to [whatever's] recommended? (working on process of elimination)

Glad you got it to work! At least with one controller. I only have an original 360 controller (wireless), so can't attest to the other. It looks like the Power A is a corded controller. So it may be related to what @skizzosjt was mentioning regarding the joy number (not to be confused with the Button #). That is, it might be being seen as Joy controller #2, or #4 or something other than 1Joy. So "1Joy6" may need to be "2Joy6" or "4Joy6".

MAME ROMs don't have any required associated mp4 files with them. If your ROMs folder for MAME contains .mp4 files, I might question your ROMs source. And yes, you can remove .mp4 files located in with your MAME ROMs without affecting the games. That said, videos that you're seeing in LaunchBox would (should) be located in your ..\LaunchBox\Videos\[name of platform]\ folder.

Well, looking at this last post, I might suggest keeping the cat from walking on the keyboard. Missing the screenshot of the Details section. Though not sure It's going to help much. The screen that's popping up is triggered (by default) by pressing Shift+F7. Not sure if it can be triggered by turning on AutoSave, especially when loading a game (vs exiting). My next thought was maybe you have a key stuck on the keyboard. But you'd have to have 2 stuck unless you remapped the default key press(es). Also, it'd trigger when loading from MAME itself. If that doesn't lead you to any thoughts of possibly something you changed or may have done, you could ty doing a fresh install of MAME. Beyond that, I'm out of ideas.

(Should be able to take a screenshot of the message by pressing "Print Screen", then [here] when typing your message, press Ctrl+V to paste the image) I'm still not sure what the 'box with save state' is that's opening when you launch a game. Does it say anything other than 'save state'? Does it give you options to select a save state to load? Or is it something you just have to click to close? Or does it automatically close on its own? Sorry. Again, I've just never seen anything related to 'save state' open when launching a game. My next question was going to be if you could edit your MAME emulator (in LaunchBox) and share a screenshot of the Details section and one of the Running Script section. If you have the Edit Emulator window open, you can take a screenshot of just that window by pressing Alt+PrintScreen. And then press Ctrl+V in your message reply. You know, they say a picture's worth a thousand words.