Out of Memory Error When Waking from Sleep

📝 Description Some users on LaunchBox 13.21 may encounter an “Out of Memory” error after waking their PC from sleep. This is a known issue related to hybrid sleep — a power state where the system first enters hibernation before going to sleep. 🔧 Technical Details The problem appears to stem from how the.NET Framework handles system sleep states. While the framework is expected to manage transitions smoothly, it’s currently failing to do so in this scenario, resulting in instability upon wake. 🛠️ Workaround The issue can potentially be avoided by disabling hybrid sleep. This usually involves turning off hibernation entirely. While results may vary, this workaround has helped some users avoid the error but is not a good long term solution — please use at your own discretion. 🚧 Status We are actively investigating possible workarounds within our codebase. However, the root of the issue lies within the.NET Framework, which complicates a direct fix. This issue did not delay the release of 13.21, but we are prioritizing a more stable long-term solution.

AstroBob 12 days ago

4

Known Issue

LaunchBox Save Management No Longer Recognizes Flycast Saves After Recent Change

Description: The Save Management features in LaunchBox are no longer working correctly with the Flycast core (Dreamcast emulator via RetroArch) due to a recent change made by Flycast developers. Details: Previously, Flycast saved files using the same name as the ROM file, which allowed LaunchBox to easily detect and associate save files with each game. However, as per this Flycast update (Discussion Link), saves are now named using the game’s internal GAME ID instead of the ROM filename. As a result, LaunchBox can no longer detect existing saves because the filenames no longer match the ROMs, breaking Save Management functionality for any titles using the updated Flycast core. Steps to Reproduce: Update Flycast core to the latest version with GAME ID save naming. Load a Dreamcast ROM using the updated core. Create a save file in-game. Check LaunchBox Save Management for the ROM — no save is detected, despite one existing on disk. Expected Behavior: LaunchBox should recognize save files associated with games, even if Flycast uses GAME IDs rather than ROM filenames. Additional Information: This change affects all users of the updated Flycast core through RetroArch and impacts Dreamcast game saves specifically.

AstroBob 14 days ago

Known Issue

SQLite Error : `database disk image is malformed' .

ISSUE SQLite Error 11: 'database disk image is malformed'. App: LaunchBox Version: 13.20 Theme: Big Details Type: Microsoft.Data.Sqlite.SqliteException Site: Void ThrowExceptionForRC(Int32, SQLitePCL.sqlite3) Source: Microsoft.Data.Sqlite at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db) at Microsoft.Data.Sqlite.SqliteDataRecord.Read() at System.Data.Common.DbDataReader.ReadAsync(CancellationToken cancellationToken) --- End of stack trace from previous location --- at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.AsyncEnumerator.MoveNextAsync() at Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ToHashSetAsync[TSource](IQueryable`1 source, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ToHashSetAsync[TSource](IQueryable`1 source, CancellationToken cancellationToken) at Unbroken.LaunchBox.LocalDb.GamesDb.GetAllGameIdsAsync(Nullable`1 cancelToken) at Unbroken.LaunchBox.LocalDb.GamesDb.GetAllGameIdsAsync(Nullable`1 cancelToken) at Unbroken.LaunchBox.Windows.Data.GameSuggester.GetSuggestions(GameBase game, Int32 max, Boolean allowSameDbId) at ServiceAdvisorError.ManageXmlCollection(Object, GameBase game, Int32 max, Boolean allowSameDbId, ServiceAdvisorError) at Unbroken.LaunchBox.Windows.Data.GameSuggester.GetSuggestions(Int32 max, Boolean allowSameDbId) at Unbroken.LaunchBox.Windows.Desktop.ViewModels.GameDetailsViewModel.StopMultipartDecorator() at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.ReflectMultipartMessage(Object) at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.ChangeStatelessParameter() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) Recent Log: 02:38:45 Exception SOLUTION Run the following tool: Tools > Download > Force Update Games Database Metadata

Brian Faeran 21 days ago

Known Issue

RetroAchievements Global Leaderboard missing info in BigBox

The user placement at the bottom of the RetroAchievements Global Leaderboard is not showing in BigBox. It shows correctly in LaunchBox. I noticed this in 13.21 beta. Screenshot from BigBox Screenshot from Launchbox

SqHd52 About 1 month ago

2

Known Issue

Launchbox destroed unwillingly the switch Libary

I have a very big Switch game Library of physical cards. To Backup them, I used my modded Switch. Since one year I bought the Mig Switch Card and so I started backing up the complete set of Files to use them with that Flash Card. A Complete Backup of the Fame contains 5 Files: Gamecard image (xci) Gamecard initial data Gamecard certificate Gamecard card id set Gamecard card uid To Run the games are only necessary the game itself (xci) the certificate (which is not game specific) and the initial data (which is specific to each game) So I put each set of Files in separate Folders and imported them into Launchbox. to day I checked the Files and had seen that LB had moved all Files to the Root Folder of the Console Game Folder, means you will never find out which files belong to which game any more. Here we need a feature to prevent LB to separating the files from each other.

rexxxx About 1 month ago

1

Back Command Unresponsive After Failed Search in Big Box

Summary When using the search shortcut in Big Box, if the search query returns no results, the back command fails to return the user to the previous section. This leaves the user stuck on the search screen unless they have an alternative shortcut mapped to navigate to another section. Affected Versions 13.20 Steps to Reproduce Open Big Box and navigate to any section Activate the search function using its mapped shortcut. Enter a search term that does not return any results. Attempt to use the mapped back command (e.g., a button on a controller or keyboard shortcut). Observe that the back command does nothing, leaving the user stuck on the search screen. Try entering a different search term that does return results and press the back command. Observe that in this case, the back command works correctly, returning the user to the previous section. Expected Behavior When performing a search, regardless of whether results are found or not, the back command should always function consistently. If no search results are found, pressing the back command should return the user to the previously active section, just as it does when results are present. Actual Behavior If search results exist, the back command correctly returns the user to the previous section. If no results exist, the back command does nothing, effectively trapping the user on the search screen. The only way to exit the search screen in this scenario is by using a mapped shortcut to a different section, which may not always be available. Reproducibility ✅ Consistently reproducible when searching for terms with no results. Workaround • Users with a direct navigation shortcut to another section (e.g., a mapped key to “Games” or “Platforms”) can bypass the issue. • If no such shortcut exists, users must restart Big Box to escape the search screen. Proposed Fix Ensure that the back command functions consistently, allowing users to return to their previous section even when a search yields no results.

AstroBob 2 months ago

Known Issue

SQLite Error 26: `file is not a database`.

SQLite Error 26: file is not a database. Details This error could occur if LaunchBox was in the middle of making changes to the local database SQLite file and some kind of force stop process happens to LaunchBox. The next time you open LaunchBox, you may get an error that is very similar to the above. Solution If you can make it into LaunchBox, run the following process: Tools > Download > Force Update Games Database Metadata…

Brian Faeran 3 months ago

Known Issue: Big Box Freezing due to playback engine compatibility

Description: Multiple users have reported that Big Box freezes after a a period of time, requiring the application to be force-quit. The issue appears inconsistent and difficult to reproduce, but several reports suggest a potential link to video playback settings (WMP vs. VLC). Observations from Reports: • The time before freezing varies wildly, ranging from 10–15 minutes, to hours, to days. • Some users report that WMP (Windows Media Player) does not freeze, while VLC seems more prone to freezing. • Some users report no crashes at all, even after extensive testing. Steps to Reproduce (Inconsistent): 1. Launch Big Box 2. Navigate through games, leave idle, or turn on attract mode 3. Monitor for freezing behavior 4. If using VLC, try switching to Windows Media Player (WMP) and compare behavior Expected Behavior: Big Box should remain responsive, regardless of the time elapsed or the number of videos played. Actual Behavior: • Big Box freezes and becomes unresponsive. • Requires force-quitting the application to recover. Workarounds & Potential Fixes: • Switch from VLC to WMP: Go to Big Box’s System Settings Options Videos. Change the Video Playback Engine from VLC to Windows Media Player. Make sure to restart Big Box for the changes to take effect • Monitor if the issue persists across different video players. 🚨 Please note: The settings to control the playback engine in Big Box and LaunchBox are different. Changing this setting in LaunchBox, will have no effect in Big Box Status: ✅ Resolved. With the release of 13.21, we’re considering this issue resolved. To close the loop, WMP is now the default video playback engine, and our installer has been updated to include the necessary codecs (K-Lite) to ensure everything works properly.We understand there are some concerns about moving away from VLC. We’ve provided a detailed explanation of the issue and why we made this decision in our article, which you can check out below: Understanding Video Playback for LaunchBox & Big Box in 13.21 and Beyond Now that WMP is the default playback engine, if you’re still experiencing freezing issues, we’ll assume you’re no longer using VLC. Please open a new report so we can diagnose the problem further. Thanks for bearing with us while we got this sorted out!

AstroBob 3 months ago

23

Known Issue

YouTube Video Streaming Not Working in LaunchBox for Android

Description: YouTube video streaming is currently not working in LaunchBox for Android. Instead of playing the video, users see a message stating that the video is downloading, but nothing actually plays. Steps to Reproduce: 1. Open LaunchBox for Android. 2. Follow these steps: • Menu > Options > Video Streaming → Enable Video Streaming. • Navigate to a game where a YouTube video should play. 3. Expected behavior: The video should stream directly from YouTube. 4. Actual behavior: A message appears indicating the video is downloading, but it never plays. Possible Cause: • YouTube has made backend changes that have broken LaunchBox’s video streaming functionality. Workaround: 🚫 No known workaround at this time. Locally downloaded videos from EmuMovies still function correctly. Status: 🔍 Under investigation. The team is looking into potential fixes. Updates will be provided when more information is available.

AstroBob 3 months ago

1

Known Issue

Known Issue: Vita3K ROM Imports Failing Due to Incorrect Path Handling

Description: An issue was identified in the code related to Vita3K ROM imports, where the importer was expecting a full path but received .\ instead. This has now been fixed and will be included in the next beta/release. Cause: It’s unclear if this is due to a default change in Vita3K’s config file, but many users have reported seeing .\ as the value instead of a full path. Workaround (Until Fix is Released): 1️⃣ Open File Explorer and navigate to your Vita3K installation folder. 2️⃣ Open config.yml in any text editor. 3️⃣ Find the line starting with: pref-path: 4️⃣ Replace .\ with the full path to your Vita3K folder. 5️⃣ Save the file. 6️⃣ Run ROM imports as usual. Status: ✅ Fixed in the next update.

AstroBob 3 months ago

1

Known Issue: Attempt to Hide Console Window on Startup/Shutdown” Causing Emulator Issues

Description: The “Attempt to hide console window on startup/shutdown” setting in LaunchBox is causing various issues with certain emulators, including Dolphin, Mesen, and Vita3K. Known Issues: 1️⃣ Dolphin Emulator: • Causes flickering when launching games. • Prevents games from launching in fullscreen, even when command-line parameters specify it. 2️⃣ Mesen Emulator: • Similar fullscreen launch issues as Dolphin. 3️⃣ Vita3K Emulator: • Completely prevents the emulator from launching any games when this setting is enabled. Workaround: If you’re experiencing any of these issues, try disabling the setting: 1. Go to Tools > Manage > Emulators. 2. Select your emulator (Dolphin, Mesen, or Vita3K). 3. Under the Details tab, find “Attempt to hide console window on startup/shutdown”. 4. Uncheck the box and try launching the game again. Status: This is a known issue under investigation. Unchecking the setting should resolve the problem in the meantime.

AstroBob 3 months ago

1

Known Issue: Managing Game Saves Not Functioning in LaunchBox 13.19

Description: In LaunchBox 13.19, there is a known issue affecting the Game Saves window. Users are unable to delete game saves, and attempting to back up or restore a save results in an error. Steps to Reproduce: 1. Open LaunchBox 13.19. 2. Navigate to a game with an existing save. 3. Click the trash icon to delete the save → Nothing happens. 4. Attempt to back up an active save → An error is displayed 5. Try to restore a backup save → Same error appears. Expected Behavior: • Deleting a save should remove it. • Backing up and restoring saves should function without errors. Actual Behavior: • Deleting a save is non-responsive. • Backup and restore actions trigger an error message, though backups seem to be created correctly. Workaround: 🚫 No known workaround at this time. Status: This issue is related to.NET 9.0 compatibility and will require a fix in a future update.

AstroBob 3 months ago

1

Known Issue: DOS Game Importer Crashes in LaunchBox 13.19

Description: The DOS importer wizard is currently broken in LaunchBox 13.19 due to compatibility issues with.NET 9.0. Attempting to use the wizard results in a crash. Steps to Reproduce: 1. Open LaunchBox 13.19. 2. Start the DOS game importer wizard. 3. The application crashes during the import process. Expected Behavior: The DOS importer should function correctly without causing crashes. Actual Behavior: LaunchBox crashes when using the DOS importer wizard. Workaround: 🚫 No current workaround is available. However, users can revert to version 13.18 by running the installer found in: 📂 LaunchBox\Updates Status: This issue will be addressed in a future beta update.

AstroBob 3 months ago

1

Known Issue: LaunchBox crashes on load after 13.19 update

Description: After updating to LaunchBox 13.19, users are experiencing crashes on startup. The issue is linked to third-party plugins that have not been updated for.NET 9.0, which is now required for compatibility. Steps to Reproduce: 1. Update to LaunchBox 13.19. 2. Attempt to launch the application. 3. If using outdated third-party plugins, the app crashes during the splash screen, displaying an error message. Expected Behavior: LaunchBox should load normally without crashing. Actual Behavior: LaunchBox crashes during startup, often displaying the error: (Inner Exception) “BinaryFormatter serialization and deserialization have been removed.” Known Problematic Plugins: • AddToGamesDB (Unsupported for years, should be removed) • OmegaSettings (Preinstalled on Extreme Home Arcade machines) Workaround: 1. Navigate to LaunchBox\Plugins. 2. Remove all third-party plugins. 3. Restart LaunchBox. 4. If the issue is resolved, reintroduce plugins one by one to identify the culprit. Resolution: Affected users must remove or wait for updates to outdated plugins. If a plugin is essential, users should reach out to the developer for a .NET 9.0 update. Additional Notes: More details and discussion: 🔗 Forum Post

AstroBob 3 months ago

2