Known Issue: 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 19 days ago
Known Issue
Known Issue: 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 19 days ago
Known Issue
Open To Community
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 About 1 month ago
Open To Community
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 About 1 month ago
Investigation
Known Issue: Big Box Freezing
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: 🛠 Issue under investigation. Further testing is needed to determine whether VLC playback is the primary cause or if there are additional factors.
AstroBob About 1 month ago
Known Issue
Investigation
Known Issue: Big Box Freezing
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: 🛠 Issue under investigation. Further testing is needed to determine whether VLC playback is the primary cause or if there are additional factors.
AstroBob About 1 month ago
Known Issue
In Progress
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 About 1 month ago
Known Issue
In Progress
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 About 1 month ago
Known Issue
Completed
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 About 1 month ago
Completed
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 About 1 month ago
Completed
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 About 1 month ago
Completed
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 About 1 month ago
Completed
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 About 1 month ago
Completed
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 About 1 month ago
Completed
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 About 1 month ago
Completed
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 About 1 month ago
Open To Community
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 About 1 month ago
Open To Community
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 About 1 month ago