MysterNybble

Good point, underscore is another access key flag too for different kinds of forms. In that case, definitely use the same symbol from English :), hopefully we did it right 🤪

The ampersand is the mark for the access key: whichever letter follows it will become the access key. It doesn't need to follow English so C&reate using R, O&luştur using L, or Oluştu&r using R are all valid. The trick is that wherever this text is shown the access key is ideally unique amongst other elements in that menu/page which I know is not super obvious from just the language files which is probably why favoring the English access key feels simpler. We can probably do better here (not exactly sure how right now), but in short you can do whatever feels natural to your language and the only challenge is if the letter is reused.

I agree that LaunchBox should create the 3D box from one Box - Full image. I am not asking you to stop using Box - Full. Please keep the image in the Box - Full folder. Only uncheck Box - Full inside the Box - Front Priorities settings. When it is checked there, LaunchBox may use the complete image as the front face instead of processing it as a full cover. Then clear both Cache-LB and Cache-BB and test again with only the Box - Full image. Please tell me whether you performed both steps in 14.0.1 Beta 1 and whether the 3D box renders correctly: yes or no.

Can you try two things for me. Uncheck "Box - Full" from that box front priority list. Clear your image cache, either through the menu or just delete both Cache-BB and Cache-LB folders and let it regenerate. Let me know if these work for you!

Not sure you got my whole message: #1) your "Box - Front" image priorities #2) Screenshot of the image itself *in* windows explorer so we can see the thumbnail and where it's at and what it's called #3) Screenshot of that image in the media of the game, so we can see what image type it thinks it is?

I don't disagree :). Could you give me the screenshots, so I can help you out so we can make sure it works correctly?

This is, currently, how Big Box works. The reader is a separate application, and Big Box tries to pause/mute/etc. when it loses focuses. That said, this is a good idea since it is our own reader. I like the idea but going to keep it out of this hotfix but maybe for the next release. Might be best to submit to our feedback site as a feature request so we don't lose sight of it. Our quick testing showed this working. Can you confirm some things for us... #1) your "Box - Front" image priorities #2) Screenshot of the image itself *in* windows explorer so we can see the thumbnail and where it's at and what it's called #3) Screenshot of that image in the media of the game, so we can see what image type it thinks it is? ---- Appreciate it everyone!

I'd love to be able to help you out, but you seem to simultaneously being unable to install LaunchBox while not being able to shut it down (even though it isn't running) and you have some other program perhaps locking your files preventing you from doing anything. I'm not trying to be silly; I just don't know where best to start but we'll try 'em all. Please read this with a tone that I am trying to help and hopefully you can respond with a tone that you want help. If you are having trouble during install, when you download the setup and run it, what exactly happens? Screenshot, error messages, or windows event log messages would be useful. You say the installer is missing files? Which files, how do you know? Screenshot, error messages, or windows event log messages would be useful. If you are able to get it installed and it's "software locked up" when/where did it lock up? What screen is frozen? Screenshot, error messages, or windows event log messages would be useful. Or if you're having trouble deleting it, what exactly are you trying to delete and how are you deleting it? Which file does Windows report as being in use? Screenshot, error messages, or windows event log messages would be useful. If you're having trouble having a restart what problem persists? What does it mean for you to say "Launchbox decides to stop working", again, what exactly is happening (or not) when you click on what and how? Screenshot, error messages, or windows event log messages would be useful. Tangentially related but if LaunchBox is not in task manager, it is not holding a lock on file. It is something else. Perhaps anti-virus, or a backup tool, or a cloud sync thing, or ... just anything else. Microsoft PowerToys has a nice file lock checker thing that I use a lot in these situations.

Check your Updates folder in LaunchBox for older installs and if you don't have anything there you'll need to reach out to support via https://forums.launchbox-app.com/contact/ to get a download link for the older version.

In LaunchBox -> Tools -> Options and search for controller :), there's a checkbox you can turn off and a drop down to select the input (it has to be on/connected when you get to this screen). The memory dump analysis is a new trick in our bag of tricks, so if you get one, that could help

Was it the *same* game you played later? We are still working through challenges in detecting certain scripts/launchers so we think the game ended before it actually did (i.e. a pre-launcher launches the game and we don't see the game itself but only see the script or launcher). If the first game is consistent, let me know more about how that game is setup/what game it was if you could. We are trying to improve startup video laggy stuff still but glad to hear that the wheel feels great now :).

I just heard the zelda-opening-a-chest noise in my head, thank you for telling me this!

If you put LaunchBox into single controller mode, you can select the input you want, would that work? Inputs are riddled with oddities so if you need it to stay in All Controller mode I might need to work with you to identify what LaunchBox is seeing as far as 'controller input' to see why it's doing that.

We are working on these sorts of things but often times we can't recreate it and fixing things blind doesn't always turn out for the best. The best thing you can do it, when you notice this send us a few details: What you last saw: i.e: during the shutdown screen which screen it was stuck on, or the shutdown screen went away but it's still there LaunchBox Debug Logs Memory dumps: Perhaps the most useful for the elusive ones is a memory dump. From task manager you can right click on the exe and create memory dump which we can dive into to see what LaunchBox thinks it's working / why it might still be stuck. You can ignore the media engine process, that one will shutdown when LaunchBox itself does. LaunchBox has two processes running you might need to either identify the main one (memory usage is a strong indicator here) or just send us both These files can be large (they usually compress well though) and may contain private data so treat accordingly. Uploading to cloud drive (google, dropbox, etc.) and emailing or DMing me the link works well. I understand it is frustrating, but I really do want to fix these things for you and with enough or the right information usually I can :-P.

Hello everyone! Our very first (ever?) 3-digit release deserves its own beta. tl;dr: 14.0 was a great success, a few issues snuck in, this is a beta for a hotfix for many of them, please include logs and details when reporting issues, try to focus on the bugs listed below, and save general feedback, unrelated issues, or ideas for the next full release or use our feedback/bug report system. It is intentionally bug-fix only as a tidying up of some of the issues that have been reported and discovered since 14.0 was released (just a week ago as of this post, whew!). It spans a variety of areas across both LaunchBox and Big Box. We are hoping for a short beta cycle for this hotfix so we can get these fixes out to the masses. IMPORTANT! Please remember to include the following when providing your testing feedback: The program you are referring to that you have tested: LaunchBox or Big Box Your hardware specs and OS What you were doing in the app and how you were doing it Which theme you used The input you were using during your testing: controller, keyboard, or mouse List all community plugins that you have installed If you experience any crashes (LaunchBox or Big Box crashes to your desktop), we'll need the whole crash report, which includes Windows event logs (a lot of times it's multiple logs related to the same crash) and the mini memory dump that is stored in your Logs folder. The dumps may be large and include private data, so reach out if you want to share privately Your LaunchBox and/or Big Box debug logs Your feedback will be especially valuable if you were experiencing the issue in 14.0 and confirm you are no longer seeing it in this beta, so please let us know what you see. Here's what we could use your help testing: Beta 1 Storefront games: Repeatedly launch and exit storefront games from Big Box and LaunchBox, confirming the frontend returns without freezing or leaving the startup screen behind. Controller reliability: Rapidly tap and hold controls, reconnect controllers, and navigate Big Box Options, confirming there are no crashes, missed presses, repeated movement, or double activations. Please test both DirectInput and XInput devices if possible. Startup and pause screens: Repeatedly launch and exit games and open and close the pause screen, confirming each overlay disappears and keyboard and mouse input return normally. Big Box hybrid and 3D views: Change sorts, filters, searches, platforms, and categories, confirming the wheel, selected game, details, models, and game count remain synchronized. Big Box wall views and Jump To: Try a search with no matches and a descending Title sort, confirming the no-games message appears and Jump To lands on the correct game. Legacy theme videos: Browse games with videos using Old Default (Legacy) or other older themes, confirming the correct Game Details video loads and follows your video priorities. Startup with pending media: Restart LaunchBox with media work queued and change the Default Image Group, confirming startup no longer sticks at "Initializing process" and unavailable choices safely fall back to Boxes. Flip Box: Flip a box in the default Image Grid, then scroll, resize, or refresh images, confirming it flips correctly and does not unexpectedly return to the front. Add/Edit Application window: Open the window for applications, versions, documents, and links, confirming every option is visible or reachable by scrolling on smaller or scaled displays. Last Modified dates: Note a game's Last Modified value and select it while details load, confirming that viewing the game no longer changes the date. RetroAchievements: Check a recognized game with no published achievements, confirming it is no longer incorrectly marked as Mastered. TeknoParrot media: Download EmuMovies media for a dedicated TeknoParrot platform, confirming it now uses the Arcade_PC catalog without affecting regular Arcade or MAME platforms. Full Changelog: Beta 1 Fixed: A deadlock that could freeze LaunchBox and exhaust threads after launching and closing several storefront games Fixed: DirectInput polling and maintenance races that could cause native crashes, missed short inputs, or repeated held inputs during Big Box Options navigation Fixed: A pause-screen activation race that could leave LaunchBox or Big Box unresponsive to keyboard and mouse input Fixed: An unexpected error window could appear behind the startup or pause screen when a fade did not finish in time, leaving LaunchBox and Big Box looking frozen Fixed: A startup state mismatch that could leave LaunchBox stuck at "Initializing process" when pending media work could not start; invalid saved image groups now fall back to Boxes Fixed: Legacy Game Details videos failed to load in Old Default (Legacy) and matching legacy LaunchBox themes Fixed: Big Box hybrid game wheel repopulation issues that could leave stale, mismatched, or blank 3D model slots after sorting, filtering, or switching platforms Fixed: Big Box wall searches and filters with no matches left an empty view without the no-games placeholder Fixed: The Big Box A-Z index jumped to the wrong location when Title sorting was descending; those sorts now use the Jump To list Fixed: The Add/Edit Application window did not always grow enough to show all options; constrained screens now provide scrolling Fixed: Selecting a game updated its Last Modified date while recalculating derived media or achievement metadata Fixed: Games with no achievements available on RetroAchievements could be incorrectly marked as Mastered because of invalid completion progress Fixed: Flip Box did not work in the default fast Image Grid and could revert to front artwork during scrolling or image refreshes Fixed: Dedicated TeknoParrot platforms used the general Arcade catalog instead of EmuMovies' Arcade_PC catalog for media downloads Thanks for all of the help and detailed reports. We absolutely appreciate you and the help you provide in improving each release!