MysterNybble Posted yesterday at 09:15 AM Posted yesterday at 09:15 AM It's that time again 😝! There's quite a bit in this one, particularly around storefronts, plugins, and emulator configuration, along with another round of fixes across LaunchBox and Big Box. Unlike previous beta rounds I tried really hard to cram almost everything I wanted in this release in this beta so it's a big one, but hopefully follow up betas are just refinements. tl;dr; basically, everything changed but not in the way you might immediately notice. your existing storefront integrations are moving into plugins, MAME and RetroArch use the new emulator plugin settings support, lots more plugin related things, Big Box gets trackball/spinner support, and the usual dump of bug fixes and QoL improvements Prove to the world you can read by.... including 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 are using The type of input you were using during your testing: controller, keyboard, mouse, trackball, etc. List of community plugins that you have installed If you have a crash (LaunchBox or Big Box crashes to your desktop / close without notice), we'll need the whole crash report, which includes Windows event logs (a lot of times its 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 (which are on by default during beta now) HIGHLIGHTS The biggest change is how LaunchBox handles storefronts. Amazon, EA, Epic, GOG, Steam, Ubisoft, and Xbox are now plugins. They will appear in the Plugin Manager, can receive updates, and help us organize our codebase. We took great care to ensure your existing games, connections, and settings carry over automatically. This also opens up more possibilities for plugin developers, including additional storefronts, metadata and artwork sources, achievements, play time, game discovery, notifications, and expansion for the existing emulator plugins. For this first beta, though, a big part of the test is simply whether everything you already use continues behaving as expected as the API IS NOT FINALIZED AND WILL CHANGE - I AM NOT DONE MESSING WITH IT. There are some more immediately visible additions, too: new MAME and RetroArch settings, arcade trackball and spinner navigation in Big Box, and refreshed LaunchBox leaderboards. Please keep this thread focused on the 14.1 changes and anything that starts misbehaving after updating. General feature requests and unrelated issues can continue through our usual feedback and bug-report system. Here’s where we could especially use your help with Beta 1: Existing storefront libraries and accounts: Upgrade an existing installation and check that your accounts, games, badges, filters, and saved launch settings carry over. Check each store’s import setting, including None, Installed Games, and All Games. Turning off automatic importing should still leave your existing games available to launch. Storefront imports and artwork: Try both automatic startup imports and manual imports, including a fresh setup through the welcome wizard if you have a separate test installation. Confirm that the expected games appear, progress remains understandable, and artwork arrives. Large Steam libraries are particularly useful here: temporary rate limits should now trigger a wait and retry instead of immediately abandoning the affected work. Installing, launching, and returning from games: Test several stores in both LaunchBox and Big Box, including with the store’s own client initially closed. Check installation status, startup and shutdown screens, play time, and returning to the frontend after exiting. Try startup screens both enabled and disabled, and let us know if Play becomes unresponsive, the mouse cursor disappears, or another window unexpectedly stays in front. Plugin Manager and settings: Try updating a plugin, restarting, and confirming that its settings and accounts remain intact. Explore Configure and the new Options > Plugins section. Disable and re-enable a plugin across restarts, and check that the displayed status matches what actually happens. Repair should preserve the installed version when a matching release is available. MAME and RetroArch settings: Open Edit Emulator > Plugin Settings. For emulators you already had configured, “Let LaunchBox manage these settings” should initially be off, and games should launch as before. Turn it on to try the new options, including per-platform settings. Emulators newly installed by LaunchBox start with management enabled. MAME displays and inputs: Try monitor assignments, Borderless Fullscreen, screen effects, and the available light gun, trackball, and input-provider options. Borderless Fullscreen is especially worth testing with startup and pause screens. RetroArch configuration: Try screen effects, integer scaling, aspect ratio, fullscreen modes, run-ahead, rewind, and internal resolution where supported. Check that your existing custom command lines and RetroAchievements configuration still work. Trackballs and spinners: In Big Box Options > Mouse, enable Trackball/Spinner Navigation and try the Optimize For choices and sensitivity settings. Browse wheels, lists, walls, and Options. We’d particularly appreciate testing with dual spinners or mouse wheel spinners, and confirming that frontend navigation stops while a game has focus. Big Box navigation and game handoffs: Scroll quickly through artwork-heavy views, switch platforms, and let videos start and stop. Check taskbar hiding, Alt-Tab, multiple monitors, and returning from games. If you launch emulators through scripts or wrappers, confirm that play time and shutdown screens follow the actual game. Metadata, media, and editing: Try bulk downloads and Edit Game’s Download Images and Media dialog with the available sources. Stop and resume Bezel Project downloads, and try EmuMovies batches where some media is unavailable. When editing games, change titles or media and use Previous/Next, then confirm the changes saved and the artwork remains attached to the right game. Achievements and leaderboards: Check the refreshed LaunchBox Leaderboards card and the game/player leaderboard windows. If you change your RetroAchievements account, confirm that progress refreshes instead of retaining the previous account’s results. Plugin and theme developers: we’d also appreciate compatibility reports from your existing work. I wouldn't recommend trying to make new plugins during this beta with the new capabilities, but do as you will. Full Changelog: New Feature: Amazon, EA, Epic, GOG, Steam, Ubisoft, and Xbox support now comes from storefront plugins that are installed with LaunchBox and listed in the Plugin Manager, with shared account and import screens and support for additional storefront plugins; your existing accounts, import settings, and games carry over automatically New Feature: Big Box can now be navigated with an arcade trackball or spinners, with smooth wheel movement and separate sensitivity settings; turn on Enable Trackball/Spinner Navigation under Big Box Options > Mouse, which turns off Enable Mouse, and use Optimize For to choose trackball or spinner navigation, including support for dual spinners and mouse wheel spinners New Feature: Managed plugins can now be enabled or disabled from the Plugin Manager without uninstalling them; LaunchBox restarts to apply the change when you close the Plugin Manager, and disabled plugins are not loaded in LaunchBox or Big Box New Feature: Supported plugins can now be configured from the Plugin Manager using a new Configure button, including account connections, multiple settings forms, and localized validation messages New Feature: Plugin settings and account connections now appear under a new Plugins section in Options, grouped by what the plugin provides, with searchable settings and support for sharing an account across components in the same plugin New Feature: Emulator plugins can now add a Plugin Settings page to the Edit Emulator window, starting with MAME and RetroArch, with options for all platforms or per platform; "Let LaunchBox manage these settings" is off for emulators you set up yourself or added before this update, and on for emulators LaunchBox installs from now on New Feature: MAME settings include choosing monitors for one or two MAME windows, a Borderless Fullscreen mode that lets the pause and startup screens appear over the game, screen effects, light gun and trackball support, and input options, showing only what your MAME version supports New Feature: RetroArch settings include CRT, handheld LCD, NTSC, and scanline screen effects, integer scaling, aspect ratio, borderless or exclusive fullscreen, run-ahead, rewind, and internal resolution upscaling for 3D systems New Feature: Plugins can now supply game metadata and media alongside the LaunchBox Games Database and EmuMovies in import wizards, Download Metadata and Media, and Edit Game's Download Images and Media dialog, with an option in the bulk tool to prioritize a plugin's descriptive metadata New Feature: Added support for independent achievement plugins, allowing additional sources to provide achievement lists and progress for games with a matching storefront or RetroAchievements ID, shown in their own tabs in the LaunchBox and Big Box achievement popups New Feature: Added support for independent game activity plugins, allowing additional sources to supply play time and last-played information while preserving existing game statistics New Feature: Game discovery plugins can now help the Windows game importer recognize games and exclude non-game applications New Feature: Expanded the plugin SDK so emulator plugins can implement only the capabilities they need, such as installation, updates, BIOS setup, import options, launch preparation, achievements, and save management, instead of deriving from the EmulatorPlugin base class, which existing plugins can keep using; storefront and emulator integrations can also use new shared game launch, process tracking, and game installation or removal capabilities New Feature: Plugins can now publish localized LaunchBox notifications with action buttons and progress updates for long-running tasks New Feature: Plugin developers can now use dedicated data storage, a private files folder, and credential storage protected by Windows for the current PC, each scoped to their plugin New Feature: Big Box themes can now show RetroAchievements progress and estimated time to beat or master a game on screensaver views Improvement: The Plugin Manager now shows plugin loading failures, compatibility restrictions, and recent plugin errors to help identify plugins that need attention Improvement: Managed plugin packages now support more precise LaunchBox version requirements and checks for incomplete or altered downloads before installation or updates Improvement: The community leaderboards on the Game Details panel are now a single LaunchBox Leaderboards card with Weekly, Monthly, Yearly, and All-Time tabs, your own rank and score, a highlighted player row, and a Log In button that connects your Games Database account and enables MAME high score uploads Improvement: The game and player High Score Leaderboards windows have a new look with clearer tabs and score columns; game leaderboards also show the game's clear logo over a blurred background and include a View Game button that opens the game on the LaunchBox Games Database Improvement: Steam play time and last-played dates no longer overwrite longer play time or more recent dates recorded by LaunchBox Improvement: With startup screens turned off, LaunchBox and Big Box now prepare games in the background so the interface stays responsive while a game starts Improvement: Automatic storefront imports at startup now show which storefront is being scanned and the current step Improvement: Refreshing installed status at startup now skips storefronts with no games in your library, avoiding unnecessary storefront checks Improvement: Auto-populate playlist rules now use a single Achievements field with a source selector in place of separate achievement fields; existing playlists continue to work Improvement: Storefront names in filters, badges, and Manage Storefronts now match their plugins, such as Ubisoft Connect, Xbox, and EA app Improvement: The Audit window now has columns for every storefront, including Amazon Games and Xbox Improvement: The Options search box is now focused when the window opens, allowing you to start typing immediately Improvement: Manage Emulators and Edit Emulator open faster because emulator versions are no longer looked up twice when checking for updates Improvement: The Add/Edit Game window opens faster and shows images right away instead of appearing empty while they load Fixed: Repair in the Plugin Manager could replace a plugin with an older version; it now reinstalls the same version, explains when repair is not available, and offers a compatible version when the installed one does not support your LaunchBox version Fixed: LaunchBox could crash when filtering games by Progress or changing a game's Progress from the Game Details panel Fixed: Manual ROM imports could report games as successfully imported without adding them when "Force importing duplicate games" was enabled and combining ROMs was turned off Fixed: Xbox 360 imports could miss games after encountering an inaccessible folder; the scan now skips those folders and continues Fixed: Changing your RetroAchievements username did not refresh achievement progress throughout the library, leaving progress from the previous account until a manual scan Fixed: Using Previous or Next in Edit Game could leave images or videos missing or incorrectly named after changing a game's title; media changes now finish saving before moving to another game Fixed: Bezel Project downloads could repeatedly download the same repository and exhaust resources when interrupted by other media downloads; stopping and resuming now preserves unfinished games and cleans up interrupted downloads Fixed: Scrolling Big Box wheels quickly could stutter, leave artwork blank, or freeze Big Box for several seconds; artwork now loads more smoothly with fewer interruptions during navigation Fixed: Unresponsive storefront discovery or installed-state checks could hang startup or importing games; checks now stop waiting after 30 seconds and preserve existing installed status Fixed: An error message about a damaged data file could open behind the startup screen while games were loading, leaving LaunchBox looking frozen Fixed: Installing or updating LaunchBox could fail when a component folder was briefly in use by another program, such as antivirus software Fixed: Double-clicking a game or repeatedly pressing Enter or a controller button could launch the same game or emulator more than once in LaunchBox and Big Box; with startup screens off, LaunchBox now shows the busy cursor while the game starts Fixed: Epic Games metadata could skip filling in a missing developer when the game already had notes, or replace an existing developer when the game had no notes Fixed: LaunchBox and Big Box could remain behind other windows or only flash in the taskbar after a game exited, instead of returning to the foreground Fixed: LaunchBox could show out-of-date information after returning from a game, with the details video still paused and play time not updated; returning now restores the window, resumes the details video, and updates play time Fixed: Slow or unresponsive game processes could briefly stall LaunchBox and Big Box or delay detecting that a game had closed Fixed: Emulators started through a launcher or wrapper could lose their shutdown screen and accurate play time tracking when the game window belonged to a child process Fixed: A custom --appendconfig in a RetroArch command line was ignored when RetroAchievements login was enabled Fixed: Steam imports and metadata updates could report errors or leave artwork missing when Steam temporarily limited requests; LaunchBox now waits and retries automatically Fixed: Steam posters and banners failed to download for some games after Steam changed where it stores artwork; LaunchBox now looks up an alternate image location when the standard one is unavailable Fixed: Installing or uninstalling a Ubisoft game from LaunchBox could also ask Ubisoft Connect to launch it Fixed: Bulk EmuMovies media downloads could get stuck searching and downloading the same games repeatedly when a media file could not be found Fixed: In Edit Game's Download Images and Media dialog, EmuMovies music was preselected based on whether the game had a manual instead of music Fixed: Big Box could stop hiding the taskbar after a game was played, leaving it visible over Big Box Fixed: The game startup screen could appear in the taskbar and Alt-Tab while a game was running, or jump to the primary monitor when activated Fixed: Switching to Big Box with Alt-Tab while a game was running could show a black startup screen instead of Big Box Fixed: The Windows mouse cursor could stay hidden after a startup screen closed or after LaunchBox or Big Box exited Fixed: Big Box could crash sometime after leaving a screen that was playing videos Fixed: A notification that failed to display could leave a stray Notification Center entry, and notifications arriving together could show overlapping pop-ups Thanks for helping us test this one. Given the quantity of changes reports about things still working are just as useful as when they don't. If something does break, more details are more helpful. We could not do this without all of your help so thanks in advance for any help you provide. It absolutely helps improve every release. 1 1 Quote
AzgoRAth Posted yesterday at 11:02 AM Posted yesterday at 11:02 AM Hey guys. Thanks for new update. I think I figured out what was causing the issue with multiple monitors that I was having in the previous version. It was the *Use controller in Launchbox* feature where even though bigbox wasnt the main focus window, the LB controller part was still in control. After disabling "Use controller in Launchbox" options and clearing the controls, the problem looks to be fixed now.. Quote
Fursphere Posted yesterday at 02:48 PM Posted yesterday at 02:48 PM Trackball and Spinner support for wheel movement. The program you are referring to that you have tested: Big Box Your hardware specs and OS: Windows 11 What you were doing in the app and how you were doing it: Big Box Navigation Which theme you are using: Default The type of input you were using during your testing: controller, keyboard, mouse, trackball, etc. : Trackball and Spinner List of community plugins that you have installed: None Spinner support - *chefs kiss* - you guys nailed this one Trackball support - Close, but it feels weird. I'll attempt to explain. I had to crank the sensitivity up to 300% - 350% to get decent movement out of the trackball on my system. I suspect that's hardware related. Unlike spinner, trackball has both X and Y axis (duh). Looks like you enabled both. So at the 'main' bigbox menu (horizontal scroll). It has a "speed" left to right - you just get a feel for it. However, if you move the trackball in a slight diagonol motion, the "recent games list" get selected. 1) It can be tricky to get 'out' of this sub-menu with just the trackball. You have to move it all the way to the left. And then "UP" but its not instant. Like, you have to "PUSH" up more (keep rolling the trackball up longer than you'd expect) to get the selection to finally 'pop' out. 2) The speed of the sub-menu vs the main system menu is way off. Lets call main menu 100% (just a feel right?). When it drops to the recent game menu, it feels like it jumps to 300% - 400% speed. Its not consistent. 3) There is a similar issue (though not nearly as bad) when you enter a system menu, and "up down" becomes the title selection and "left right" becomes the alphabetical 'quick search' function - and any diagonal movement tends to switch modes unexpectedly. Nothing here is breaking obviously. It just feels 'off' with the trackball - non consistent. I would say giving the ability to selective 'disable' one or the other axis - but then you'd get goofy when you go from Horizontal to Vertical (main wheel vs. system/platform wheel). Unless you can have logic to detect which way the wheel spins, and dynamically change it? (and this would help the spinner too - since it could work in both modes with a single axis) Quote
AzgoRAth Posted yesterday at 05:01 PM Posted yesterday at 05:01 PM I found a bug in the latest beta. BB crashes when I try to open the achievement list for any game. Quote
MysterNybble Posted yesterday at 07:27 PM Author Posted yesterday at 07:27 PM 2 hours ago, AzgoRAth said: I found a bug in the latest beta. BB crashes when I try to open the achievement list for any game. Thanks, can you provide the details requested above? Crashes do have special instruction. Quote
AzgoRAth Posted yesterday at 10:13 PM Posted yesterday at 10:13 PM 2 hours ago, MysterNybble said: Thanks, can you provide the details requested above? Crashes do have special instruction. Program: Bigbox OS: Windows 11 Specs: ryzen 2700x, rtx 4070, 24gb ddr4 ram, 512gb Sata SSD Action when crash occurred: Opening Achievement list for any game in BigBox. Theme: Default Type of input: controller List of plugins: only the default ones that come with BBnative-v1-BigBox-20260927T220152549Z-p17580-t17872-C00000FD-03bac667-32b6-45fb-ade5-dfc45a98.dmpnative-v1-BigBox-20260927T220152549Z-p17580-t17872-C00000FD-03bac667-32b6-45fb-ade5-dfc45a98.dmp logs.evtx logs.zip Debug 2026-09-27 11-59-51 PM.log Quote
SqHd Posted 23 hours ago Posted 23 hours ago This is great! I like the work on Leaderboards. It's nice to see my score listed above for a particular game. But I couldn't find a tab with a summary of all of the games I've played with scores. Is something like that planned? It would very helpful since I can't remember all the games I've played in Mame for scores. Thanks for the excellent update! One minor potential bug is a few of the platforms are showing games as uninstalled (there is a blue "install" button instead of the green "play" one). Example systems: Arcade (Mame), PS3, PS4, Switch, TI-99 4a, WoW Action Max, I couldn't decipher a pattern based on rom type or emulator. The program you are referring to that you have tested: LaunchBox 14.1.0 Beta Your hardware specs and OS - Win 11, AMD APU, 16gb ram What you were doing in the app and how you were doing it - Just browsing games Which theme you are using - Default theme (latest version) The type of input you were using during your testing: controller, keyboard, mouse, trackball, etc. - keyboard / mouse List of community plugins that you have installed - Mame Softlist Importer 6.0.2, C64 Dreams Extras, eXoPlugin, eXoPluginMagazines Quote
dukdukgoos Posted 20 hours ago Posted 20 hours ago (edited) Could you explain a bit about the "Installed/Not Installed/Automatic" select box change from the previous checkbox (in the Edit Game dialog)? Edited 20 hours ago by dukdukgoos Quote
MysterNybble Posted 8 hours ago Author Posted 8 hours ago On 9/27/2026 at 6:02 AM, AzgoRAth said: Hey guys. Thanks for new update. I think I figured out what was causing the issue with multiple monitors that I was having in the previous version. It was the *Use controller in Launchbox* feature where even though bigbox wasnt the main focus window, the LB controller part was still in control. After disabling "Use controller in Launchbox" options and clearing the controls, the problem looks to be fixed now.. Glad you found a workaround though it's odd that setting as I wouldn't suspect that was the cause. Can you remind me what was happening on the other monitor and send a screenshot of the option you turned off, just to make sure I'm looking at the right thing? May still be a bug hiding in there... 17 hours ago, AzgoRAth said: Program: Bigbox OS: Windows 11 Specs: ryzen 2700x, rtx 4070, 24gb ddr4 ram, 512gb Sata SSD Action when crash occurred: Opening Achievement list for any game in BigBox. Theme: Default Type of input: controller List of plugins: only the default ones that come with BBnative-v1-BigBox-20260927T220152549Z-p17580-t17872-C00000FD-03bac667-32b6-45fb-ade5-dfc45a98.dmpnative-v1-BigBox-20260927T220152549Z-p17580-t17872-C00000FD-03bac667-32b6-45fb-ade5-dfc45a98.dmp logs.evtx 68 kB · 0 downloads logs.zip 10.85 MB · 0 downloads Debug 2026-09-27 11-59-51 PM.log 478.42 kB · 0 downloads Awesome this will help! I was able to reproduce on my side. I'll get this into Beta 2 when that's ready (hopefully by end of week). The only workaround I can offer is look at the achievements in LaunchBox for now 🤪 Quote
MysterNybble Posted 7 hours ago Author Posted 7 hours ago 15 hours ago, SqHd said: This is great! I like the work on Leaderboards. It's nice to see my score listed above for a particular game. But I couldn't find a tab with a summary of all of the games I've played with scores. Is something like that planned? It would very helpful since I can't remember all the games I've played in Mame for scores. Thanks for the excellent update! One minor potential bug is a few of the platforms are showing games as uninstalled (there is a blue "install" button instead of the green "play" one). Example systems: Arcade (Mame), PS3, PS4, Switch, TI-99 4a, WoW Action Max, I couldn't decipher a pattern based on rom type or emulator. The program you are referring to that you have tested: LaunchBox 14.1.0 Beta Your hardware specs and OS - Win 11, AMD APU, 16gb ram What you were doing in the app and how you were doing it - Just browsing games Which theme you are using - Default theme (latest version) The type of input you were using during your testing: controller, keyboard, mouse, trackball, etc. - keyboard / mouse List of community plugins that you have installed - Mame Softlist Importer 6.0.2, C64 Dreams Extras, eXoPlugin, eXoPluginMagazines You should be able to see a leaderboard summary, from a game's leaderboard try clicking your name. That should open a "player page" with all of them. The blue Install button simply means that a game is somehow marked Not Installed. If you Edit one of those games and look at the Installed dropdown it should show that. This hasn't changed much from how 14.0 was working for ROM games, was that what you were using? Do you still have access to your data prior to the beta (might be in your backup folder) to see if you compared to see what those values were before? Obviously, you can use Bulk Edit to fix all these games, but if something in 14.1 changed the value, I'll have to do some more digging. Also, do you remember what tool you used to import these games into LaunchBox, just in case that is usful. Let me know what you know! Quote
skizzosjt Posted 7 hours ago Posted 7 hours ago Steam games continue to report as "Installed" even if they are not installed. Their install status is not being detected automatically anymore. The "automatic" drop down value (used to be a checkbox) doesn't work properly. Been a problem for last couple releases I keep mentioning in the betas since 13.28 beta-6 Marking them as installed or uninstalled does at least force that value since as you can see from previous reporting even that didn't work for a couple releases. All Steam games were reporting installed no matter what value was entered and they were getting automatically updated to installed status. I've logged in and out of Steam within the frontend a few times now and confirm my API key is still working fine. Issue is on the frontend side Games are installed in the frontend and I have Steam in the background showing they are greyed out, NOT installed per Steam. Steam is correct, the frontend is incorrect. The game should be marked UNINSTALLED per how the feature is intended to work. I put in the proper value of automatic and have tried logging out and back in on both Steam, Steam within the frontend, and toggling the installed value to installed/uninstalled and back to automatic. Each time I return to automatic they go back to INSTALLED even if they are not installed. The program you are referring to that you have tested: LaunchBox Your hardware specs and OS - Windows 10 / Z390 Aorus Master MB / Intel i9-9900k / 32 GB DDR4 What you were doing in the app and how you were doing it - Browsing library Which theme you are using - Default The type of input you were using during your testing: controller, keyboard, mouse, trackball, etc. - KB + Mouse List of community plugins that you have installed I have removed these and tested without them as well. Issue persist even with ZERO plugins present. If you have a crash (LaunchBox or Big Box crashes to your desktop / close without notice), we'll need the whole crash report, which includes Windows event logs (a lot of times its 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 - Not a crash Your LaunchBox and/or Big Box debug logs (which are on by default during beta now) - File attached as an archive Logs.7z Quote
JoeViking245 Posted 7 hours ago Posted 7 hours ago 15 minutes ago, skizzosjt said: List of community plugins that you have installed Nice list! 1 Quote
MysterNybble Posted 7 hours ago Author Posted 7 hours ago 12 hours ago, dukdukgoos said: Could you explain a bit about the "Installed/Not Installed/Automatic" select box change from the previous checkbox (in the Edit Game dialog)? I think it was in 14.0 we added the third state 'Automatic' to help users control when LaunchBox is allowed to manage it, and when the user "knows better". It's currently used by storefronts (as they have the ability to install). There may be room for certain emulators or future features to use this which is why it's at the game level. Automatic - let LB manage it, underneath it asks the storefront if it's installed or not (though again, may use this in the future for other things than storefronts) Installed (former Installed checked) - ignore what LB thinks - just show play Not Installed (former Installed unchecked) - ignore what LB thinks - just show install I think we can improve the presentation of this but hopefully that helps! 1 Quote
MysterNybble Posted 7 hours ago Author Posted 7 hours ago 22 minutes ago, skizzosjt said: Steam games continue to report as "Installed" even if they are not installed. Their install status is not being detected automatically anymore. The "automatic" drop down value (used to be a checkbox) doesn't work properly. Been a problem for last couple releases I keep mentioning in the betas since 13.28 beta-6 Marking them as installed or uninstalled does at least force that value since as you can see from previous reporting even that didn't work for a couple releases. All Steam games were reporting installed no matter what value was entered and they were getting automatically updated to installed status. I've logged in and out of Steam within the frontend a few times now and confirm my API key is still working fine. Issue is on the frontend side Games are installed in the frontend and I have Steam in the background showing they are greyed out, NOT installed per Steam. Steam is correct, the frontend is incorrect. The game should be marked UNINSTALLED per how the feature is intended to work. I put in the proper value of automatic and have tried logging out and back in on both Steam, Steam within the frontend, and toggling the installed value to installed/uninstalled and back to automatic. Each time I return to automatic they go back to INSTALLED even if they are not installed. The program you are referring to that you have tested: LaunchBox Your hardware specs and OS - Windows 10 / Z390 Aorus Master MB / Intel i9-9900k / 32 GB DDR4 What you were doing in the app and how you were doing it - Browsing library Which theme you are using - Default The type of input you were using during your testing: controller, keyboard, mouse, trackball, etc. - KB + Mouse List of community plugins that you have installed I have removed these and tested without them as well. Issue persist even with ZERO plugins present. If you have a crash (LaunchBox or Big Box crashes to your desktop / close without notice), we'll need the whole crash report, which includes Windows event logs (a lot of times its 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 - Not a crash Your LaunchBox and/or Big Box debug logs (which are on by default during beta now) - File attached as an archive Logs.7z You are right to think this all changed in 13.28 Beta 6, so your timing makes sense with what you are seeing. We do track the 'last known status' instead of changing it to 'Not Installed'. The intention here is that people often use removeable media for their Steam games and unplugged drives shouldn't flip everything to Not Installed. It seems that comes with some side effects :-P. Can you look at something for me? In Steam itself go to Settings -> Storage and see if any drive/library listed there no longer exists / isn't currently connected. Open this file -> Steam\steamapps\libraryfolders.vdf -> and confirm all of those paths are valid. This will confirm op rule out my initial hunch, which is Steam thought there were installed in one place, but didn't clean up after itself. Quote
skizzosjt Posted 6 hours ago Posted 6 hours ago 10 minutes ago, MysterNybble said: The intention here is that people often use removeable media for their Steam games and unplugged drives shouldn't flip everything to Not Installed. That is actually what I want to happen. Depending on which PC I am at, or which disk(s) are connected, I want the install status to follow suit. My desire is for example, affected uninstalled games would flip to uninstalled if they are not found at boot of the frontend. Then maybe next time I boot the frontend the disks with these games are connected and therefore they should automatically flip to installed at boot of the frontend. 17 minutes ago, MysterNybble said: Can you look at something for me? In Steam itself go to Settings -> Storage and see if any drive/library listed there no longer exists / isn't currently connected. Open this file -> Steam\steamapps\libraryfolders.vdf -> and confirm all of those paths are valid. This will confirm op rule out my initial hunch, which is Steam thought there were installed in one place, but didn't clean up after itself. After review I think everything looks good on Steam's end, but I'll describe everything to make sure we are on the same page. I have several disks in use for Steam. Quick summary Main disk is always given drive letter E Additional disk is always given drive letter F I have TWO backup disks which are used for backup and storage of games that I don't want to play anytime soon. These two backup disks are always given drive letters X and Z All of these disks have their proper path in the "libraryfolders.vfd" but of course not all of them are connected. In this example, my backup disks X and Z are not connected and I would then have 30 games that are considered not installed because they are only on disks with drive letter X and/or Z These are all valid paths. If we need to be technical, then when disks with drive letter X and Z are not connected then technically that isn't a valid path in this exact moment in time.....but otherwise, it's a valid path. libraryfolders.vdf So these are the disks that I primarily keep connected. Nothing is stored on main OS C drive letter and all my games are on additional disks E and F Steam is doing OK detecting which games are installed and where they are installed at that. I'm not seeing a redflag within Steam's behavior. The frontend is no longer interpreting that info correctly is my suspicion. Quote
MysterNybble Posted 5 hours ago Author Posted 5 hours ago 35 minutes ago, skizzosjt said: That is actually what I want to happen. Depending on which PC I am at, or which disk(s) are connected, I want the install status to follow suit. My desire is for example, affected uninstalled games would flip to uninstalled if they are not found at boot of the frontend. Then maybe next time I boot the frontend the disks with these games are connected and therefore they should automatically flip to installed at boot of the frontend. After review I think everything looks good on Steam's end, but I'll describe everything to make sure we are on the same page. I have several disks in use for Steam. Quick summary Main disk is always given drive letter E Additional disk is always given drive letter F I have TWO backup disks which are used for backup and storage of games that I don't want to play anytime soon. These two backup disks are always given drive letters X and Z All of these disks have their proper path in the "libraryfolders.vfd" but of course not all of them are connected. In this example, my backup disks X and Z are not connected and I would then have 30 games that are considered not installed because they are only on disks with drive letter X and/or Z These are all valid paths. If we need to be technical, then when disks with drive letter X and Z are not connected then technically that isn't a valid path in this exact moment in time.....but otherwise, it's a valid path. libraryfolders.vdf 9.38 kB · 1 download So these are the disks that I primarily keep connected. Nothing is stored on main OS C drive letter and all my games are on additional disks E and F Steam is doing OK detecting which games are installed and where they are installed at that. I'm not seeing a redflag within Steam's behavior. The frontend is no longer interpreting that info correctly is my suspicion. You make sense and I think there is a gap in how we did it but my original thinking was contradictory to how you described it. In Steam when you try to Install a game that was on a drive that is currently inaccessible it does show this after you click Install. Steam, like us, knows the game should be there but isn't and thinks reinstalling is likely what you want to do. I know that it's more likely you don't want to install as you'd just plug your drive back in. In your defense, us showing Play is also incorrect - perhaps a "Missing" like status would be a nice overall solution. Let our Steam plugin tell us the game is missing but can be fixed via Install. So, you'd know the game should be there but isn't and still gives you Steams installer and you can always plug your drive back in. Quote
skizzosjt Posted 4 hours ago Posted 4 hours ago 25 minutes ago, MysterNybble said: Steam, like us, knows the game should be there but isn't and thinks reinstalling is likely what you want to do. I know that it's more likely you don't want to install as you'd just plug your drive back in. Yes I've seen this feature in Steam before. And you are correct. In my use case this install status feature in the frontend was a reminder which games are currently installed or uninstalled since I do move games around on disks and I don't always keep them all connected. Also was nice if I booted into the frontend and basically all my Steam games were marked uninstalled, that was an obvious "oops I forgot to power on the disk" reminder lol. My goal was to highlight the automatic updating behavior of the install/uninstalled status is not working as intended anymore and that is the important part to resolve in my opinion. Adding a new missing value would be extra credit from my perspective. I agree with your point on why "Missing" should technically be added but it's the automatic updating of the value that is the real pain point for me because the game's install and not install badges cannot be trusted to have the accurate value currently. Quote
DemmyTree Posted 3 hours ago Posted 3 hours ago Just want to confirm what is the binding for screensavers with retro achievements, i currently have the following (Apologies if spoilers doesn't collapse it) Spoiler <TextBlock Text="Achievements Earned" Foreground="#DAA520" FontFamily="LAUNCHBOX_THEME_FOLDER/Fonts/RedHatDisplay-Regular.ttf#Red Hat Display" FontSize="{Binding Converter={StaticResource ScaleConverter}, ConverterParameter='30'}" Margin="{Binding Converter={StaticResource ScaleConverter}, ConverterParameter='0,0,10,0'}" /> <TextBlock Text="{Binding Path = Game.RetroAchievementsEarnedAchievements}" Foreground="White" FontFamily="LAUNCHBOX_THEME_FOLDER/Fonts/RedHatDisplay-Regular.ttf#Red Hat Display" FontSize="{Binding Converter={StaticResource ScaleConverter}, ConverterParameter='30'}" Margin="{Binding Converter={StaticResource ScaleConverter}, ConverterParameter='0,0,10,0'}" /> <TextBlock Text="Out of" Foreground="#DAA520" FontFamily="LAUNCHBOX_THEME_FOLDER/Fonts/RedHatDisplay-Regular.ttf#Red Hat Display" FontSize="{Binding Converter={StaticResource ScaleConverter}, ConverterParameter='30'}" Margin="{Binding Converter={StaticResource ScaleConverter}, ConverterParameter='0,0,10,0'}" /> <TextBlock Text="{Binding Path = Game.RetroAchievementsTotalAchievements}" Foreground="White" FontFamily="LAUNCHBOX_THEME_FOLDER/Fonts/RedHatDisplay-Regular.ttf#Red Hat Display" FontSize="{Binding Converter={StaticResource ScaleConverter}, ConverterParameter='30'}" /> Quote
Vader Posted 2 hours ago Posted 2 hours ago Hi all I just installed 14.1 beta and noticed that the load times are still very slow. For me both Launchbox and Bigbox are taking about 48 seconds to load. I have already disabled auto imports etc. but this has not helped with load times. Also, wheel scrolling is still not smooth. I have attached a video and you can see the stuttering during the wheel scrolling. Thanks for all that you do. 20260928_161446.mp4 Quote
MysterNybble Posted 1 hour ago Author Posted 1 hour ago 3 hours ago, skizzosjt said: Yes I've seen this feature in Steam before. And you are correct. In my use case this install status feature in the frontend was a reminder which games are currently installed or uninstalled since I do move games around on disks and I don't always keep them all connected. Also was nice if I booted into the frontend and basically all my Steam games were marked uninstalled, that was an obvious "oops I forgot to power on the disk" reminder lol. My goal was to highlight the automatic updating behavior of the install/uninstalled status is not working as intended anymore and that is the important part to resolve in my opinion. Adding a new missing value would be extra credit from my perspective. I agree with your point on why "Missing" should technically be added but it's the automatic updating of the value that is the real pain point for me because the game's install and not install badges cannot be trusted to have the accurate value currently. Thanks, I got something in the works, so stay tuned for beta 2, should work well :). Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.