AstroBob Posted December 5 Share Posted December 5 With LaunchBox serving as the launchpad for our games collection, we want to ensure that users are able to have the smoothest and optimal experience, regardless of their workflow or library size. That said, we realize there are some circumstances where LaunchBox and Big Box may not appear to be performing optimally. We want to lay out this detailed FAQ to hopefully shed some light on performance within LaunchBox & Big Box. ----------------------------------------------- How to use this thread 🧵 ----------------------------------------------- This thread is intended to educate and elaborate on performance within LaunchBox, along with providing potential troubleshooting steps and solutions to common problems. However, it is not intended to diagnose or address specific performance issues you may encounter. For assistance with individual performance problems, (please see the section on Reporting a performance-related Issue). We intend to keep this guide regularly updated to ensure it remains helpful and comprehensive. If you notice any topics we haven’t covered or feel certain points need further explanation, please don’t hesitate to share your feedback in the comments. While we understand frustrations can arise, we kindly ask that comments remain focused on solutions and productive suggestions. --------------------------------------------------------- Understanding Performance 🔋 --------------------------------------------------------- At its core, after 10 years of development, LaunchBox is certainly pushing the limits of its underlying technology. To explain it simply: the more games you have, the more data LaunchBox needs to load and handle simultaneously. This includes all the associated metadata, images, and other media files. Similarly, Big Box’s animation engine and its powerful theming capabilities, while providing lots of customization, also add complexity. If you’re using heavily detailed themes or large sets of media, it could impact performance. It’s also important to note that performance can be subjective. What one user might experience as a performance issue could vary greatly from another based on system specs, user configurations, or expectations. For example, a high refresh rate monitor or a particularly heavy theme may cause one user to notice the perception of lag that others might not. This variation means that performance is not always a one-size-fits-all issue and can depend on many individual factors. The LaunchBox team is continuously working on improving performance, especially for users with large libraries. We’re constantly refining how metadata is loaded and processed, and we’re looking into ways to optimize things like loading times and responsiveness. While a full rewrite might be necessary to fully resolve these limitations, each release brings iterative improvements, and we’re committed to making things as smooth as possible for all users. --------------------------------------------------------- Frequently Asked Questions 🙋 --------------------------------------------------------- In this section, we'll aim to cover some frequently asked performance-related questions and provide some clarity. Why do LaunchBox load times appear significantly longer in the most recent version compared to previous versions? Recent versions of LaunchBox have introduced a few additional tasks that happen during startup to improve functionality and user experience. One key element is the loading of our large metadata.xml file into RAM. This file houses the entire GamesDB database, containing comprehensive metadata for all games and image links, and it has grown significantly over time as our database has expanded. LaunchBox used to load this into RAM in the background, immediately after the startup screen, but certain features required us to move that into startup to make sure that users had the smoothest experience when LaunchBox appeared on the screen. By loading it into RAM, LaunchBox can instantly access game metadata, which speeds up tasks like related game recommendations, imports, and metadata & media downloads. The startup also includes automated processes, like checking storefronts for new games, verifying user authentication, and updating the game library automatically if new games are detected. This means that by the time you enter LaunchBox, a lot of behind-the-scenes setup is already completed, allowing you to dive in without needing to run those updates manually. However, if you’re not using features like related game recommendations or storefront imports, disabling these options can potentially reduce startup times (see the troubleshooting section below on how to do this) Why can LaunchBox consume CPU while it's open? While LaunchBox is running, it continuously performs background tasks designed to keep everything running smoothly and ensure a quick response time for your actions. These tasks might include tracking changes in your game library, verifying storefront connections, updating filters & badges, or scanning folders for new ROMs to add. By doing these tasks in the background, LaunchBox helps keep your experience seamless, so when you open a new game or add a title, the necessary metadata is already in place. Additionally, automated imports and metadata updates run periodically to ensure that your game library is current, especially if you’ve enabled storefront integration or automatic ROM imports. While these background tasks require some CPU, they’re essential for maintaining an up-to-date and responsive library and the system is designed to perform these tasks quietly. Does the storage location of LaunchBox affect performance? Yes, the storage location can impact performance: Solid-State Drives (SSD): Installing LaunchBox on an SSD is highly recommended, and can significantly improve load times and overall responsiveness. Network-Attached Storage (NAS): Running LaunchBox from a NAS can result in slower performance due to network latency. Installing LaunchBox on a local drive is recommended for optimal speed. Cloud-Based Storage Locations: These include local folders synced with services like Dropbox or Google Drive. While they have minimal impact on performance, storing LaunchBox in these locations is not recommended. If the sync service is active while LaunchBox is running, it can cause conflicts and lock files that LaunchBox needs to access. However, if the sync service is paused or disabled while using LaunchBox, this setup should work without issues. The above also applies if you’ve chosen to move the location of your games, emulators, and/or media to a separate location ------------------------------------ Troubleshooting 🤔 ------------------------------------ Next, we’ll explore some troubleshooting steps that may help improve performance. To make it easier to follow, we’ll break these down into three sections: LaunchBox, Big Box, and General Tips. Each section will cover specific adjustments and optimizations tailored to the unique aspects of each application. ---------------------------------------------- LaunchBox Troubleshooting: ---------------------------------------------- Turn Off Storefront Imports: Automated imports allow LaunchBox to scan your installed storefront games and add them to your library during startup and in the background after LaunchBox is open. This feature can lengthen start times & use CPU after start up. If you prefer to import your games manually, you can turn this off. To disable this feature: Go to Tools > Manage > Storefronts. Turn off Enable Automatic Imports on Startup. If you still want to import storefront games occasionally, you can do so manually based on the same Manage Storefronts configuration: Tools > Scan > For Storefront Games Turn Off Non-Local Related Games: The Related Games feature in LaunchBox and Big Box highlights games similar to the one you’re playing, including possible ports or related titles. This can be accessed through the Game Details bar in LaunchBox or the Game Details page in Big Box. By default, this feature includes games not in your library, allowing you to discover unowned titles. To provide these recommendations, LaunchBox loads a local copy of the games database into RAM (the metadata.xml file). If you don’t use this feature or prefer recommendations limited to games already in your library, you can turn off this setting: Go to Options > Related Games > Similar Games / Recommended Games / Possible Ports Turn off Include games not in my library. Turn off Metadata.xml from Loading into Memory During Startup If reducing the startup time of LaunchBox is your primary objective you can disable both Automatic Storefront Imports AND Non-Local Related Games (described above). This will then negate the need to load the Metadata.xml file into memory during start-up and quicken the time it takes for LaunchBox to open. If you use LaunchBox a lot and always want it ready to use, you can turn on the option to keep it in the system tray under Tools > Options > General > System Tray. Now when you go and try and open LaunchBox, it will be ready for you in a second! Optimizing Playlists for Performance Playlists in LaunchBox are calculated dynamically at runtime. While this process usually has minimal impact on startup times, having a large number of playlists or complex auto-playlists can increase processing demands. To maintain optimal performance, it’s a good idea to monitor the number of playlists in your library. Although LaunchBox is designed to handle extensive collections, users with hundreds of playlists per platform should be aware that each playlist requires additional processing at runtime. Focusing on creating purposeful, high-quality playlists rather than sheer quantity can help streamline operations and reduce startup times. Disable save management (Available in 13.18 beta 1) In version 13.16, LaunchBox introduced the ability to manage your save files and states automatically. This feature operates through background processes to keep your save data organized. While the CPU usage for these processes is manageable, we understand that not all users may require this functionality. As of 13.18 beta 1 you can find this setting under Tools > Options > General > Save Management, which will remove some of the background CPU usage required for LaunchBox to function. --------------------------------------- Big Box Troubleshooting: --------------------------------------- Big Box offers a high degree of customization, such as detailed themes, high-resolution images, and transition animations, all of which require processing power to render smoothly. Even on powerful PCs, complex themes or large libraries may lead to slower performance if they are heavily resource-intensive. To enhance performance in Big Box, try the following: Experiment with Different Themes Big Box’s powerful theming engine is one of its standout features, allowing you to make your collection look visually stunning. However, as with any program, themes need to be optimized to deliver the best performance, and while it is important for us to keep Big Box as optimized as possible, theme developers play as crucial a role when using a custom theme. Even on a high-powered PC, the combination of your library’s size, media, and how the theme processes them can sometimes lead to performance issues. If you’re experiencing performance issues in Big Box experimenting with themes can help you strike the perfect balance between visuals and performance. Here’s what we recommend: Use a Vetted Big Box Theme From the System Menu, go to Manage Themes. Here, you can browse and install themes that have been vetted and verified by our team for optimal performance. These themes are designed to look great while minimizing resource usage. Use the Default Theme While many vetted themes prioritize showcasing media with flashy effects and transitions, the default theme focuses on simplicity. If performance is your main concern, the default theme will deliver the smoothest experience, as it minimizes graphical demands without sacrificing usability. Tweak CoverFlow Quality: Wheels inside of Big Box can sometimes be visually impressive. Some themes choose to add many images per-game inside of one item, or choose to make the wheel take up the entire screen. When your computer has the power, they look stunning, but if you need some relief you could tweak down the image quality of the wheel itself to see if you get better results. To do so go into Options > Images > CoverFlow Image Quality, and adjust the setting to something lower. You may need to then clear your image cache by going to Options > Image Cache > Refresh All Images. Disable Wheel Easing: If you find that Big Box’s wheel can sometimes be a bit sluggish, it’s possible that the easeness Big Box uses to smooth out the transition between one game to another could be a bit much for your system to handle. You can test this theory out by going to Options > Views and unchecking Wheel Easing. Try it out and see if it helps. If not, it’s easy to turn it back on! Disable 3D Models in CoverFlow Views: Cover Flow Views can be one of Big Box’s most visually impressive features, allowing you to browse your collection with stunning box art and even “spin the box” using 3D models for a full view. While it’s a fan favorite, the 3D rendering required for these views can be demanding on certain systems. If you frequently use these views and you notice that your computer cannot handle rendering all the 3D Models, some of these views can revert back to the old CoverFlow style which ran lighter. You can turn off 3D Models in these views under Options > Views by unchecking Use 3D Models in CoverFlow Views. Turn Off Transition Effects: Disabling or adjusting transition animations can make menu navigation much smoother by reducing the demand on your system’s resources. To change or disable transitions: Open the System Menu in Big Box. Navigate to Options > Transitions. Here, you can customize the transitions used for various effects. While this depends on the theme you’re using, a general rule of thumb is: Fade/Quick Fade: These are the least taxing on your system and provide smooth transitions. Complex Transitions: Effects like slides, flips, and explosions look impressive but are more demanding. If transitions aren’t important to you, setting all transitions to Off will provide the best performance, especially on systems with limited resources. Adjust Big Box’s Frame Rate: Located under Options > General > Frame Rate, it is recommended to match the framerate to the monitor you are using. If your monitor runs at 60Hz, set the framerate to 60 FPS, but if your monitor runs at 120Hz, change the framerate to 120Hz. Note: the higher the framerate of your monitor the more your computer needs to do, which in turn does impact performance. If you have a low-powered machine, but a fancy 4k 144Hz monitor, you may benefit from downgrading your monitor or upgrading your machine. Check for freesync/gsync: Big Box is not a game. Seems straightforward enough, but using a game technology like freesync or gsync on an application like Big Box, could negatively impact your experience. Make sure you navigate to your freesync/gsync settings and force disable this technology from being used with Big Box. Ensure you are using your Dedicated GPU (if applicable): When things move in Big Box, your video card can play a big role in how smoothly those things move. If you’re using a machine with both integrated graphics and a dedicated GPU (e.g., a laptop with an eGPU or a hybrid system), ensure that Windows is set to prioritize the dedicated GPU for Big Box. Using integrated graphics instead can result in slower performance, lag, reduced visual quality, and/or driver-related bugs. To check or change this setting in Windows: 1. Open Settings and navigate to System > Display > Graphics Settings. 2. Find or add Big Box to the app list. 3. Set it to use the High-Performance GPU (dedicated graphics card). This adjustment ensures that Big Box takes full advantage of your system’s graphics capabilities, providing a smoother and more enjoyable experience. -------------------------------------------------------- General Troubleshooting Tips -------------------------------------------------------- Manage Media Content: Across both LaunchBox and Big Box, limiting the media you download can help keep things running lean and snappy. While it may be tempting to download “all the media,” if you don’t use a specific image type, it’s better to avoid downloading it altogether. This prevents your theme from processing media you don’t want to see, and reduces the amount of hard drive space required, which can lead to improved performance. To check the types of media you currently have, go to Tools > Audit. This tool provides a clear overview of your media files. Consider cleaning up any image types that aren’t utilized by your selected theme in LaunchBox or Big Box for a more efficient setup. Keep an eye on background resources: Both LaunchBox and Big Box rely on a combination of system resources to function smoothly. Background applications, open browser tabs, or other resource-intensive programs running simultaneously can negatively impact performance. To ensure a smoother experience, consider closing unnecessary programs while using either app. If you’re using a dedicated gaming machine, you may also want to explore guides on “debloating Windows” to remove unnecessary background processes. This can free up resources and optimize your system specifically for gaming and performance-heavy applications. Laptop / Handheld Performance Profiles: Many users run LaunchBox and Big Box on Windows handheld devices or laptops, which rely on power profiles to manage performance, especially when running on battery. While both apps can function on power-saving or lower-performance profiles, the complexity of your theme and the media in your library may require additional resources. Adjusting the power profile to a higher setting can ensure smoother operation by allocating sufficient system resources. ----------------------------------------------------------------------------- Reporting a performance-related Issue 📑 ----------------------------------------------------------------------------- If you’re experiencing a specific performance issue, please open a post in the Troubleshooting section of our forum. However, before posting, ensure you’ve followed the troubleshooting steps outlined in this guide, as they address the most common performance issues. To help us assist you effectively, follow these steps: Subject: Provide a brief description of your issue. Tag: Include the “performance issue” tag. Item Prefix: Change the prefix from “None” to “Performance Issue.” Diagnostics: Please include the requested diagnostics (see below) Please note, to ensure an efficient diagnosis, we kindly ask that you provide ALL of the diagnostics below, as we won’t be able to investigate properly without them. Files to provide Screen recording that clearly shows the issue Windows built-in utility (Snipping Utility) will easily let you do this Description of the issue Please include full details on how to reproduce the issue Can it be reliably reproduced? When did the issue start occurring? What is your expectation of how it is supposed to behave, VS the actual result Other Required Details LaunchBox Version Windows OS Version Number of games in your library What theme are you using (both Big Box & LaunchBox) PC hardware specs (GPU, CPU, RAM, Storage) Number of monitors + specs of each (resolution, GSync or Freesync enabled) Location of LaunchBox directory Is your LaunchBox directory fully portable? If no, the full file path location of anything outside of the LaunchBox directory (games, media folders etc) Are any third-party plugins installed? Have you tweaked any of the following with your LaunchBox instance: Symlinked any of your LaunchBox folders to another location Adjusted the .NET runtime configs Manually modified any .xml data files Any other configurations you think would be good to know about Be ready: We may ask you to send us your Data files (located in LaunchBox > Data) to try and reproduce the issue on our end ------------------------------------ Important Notes ⚠️ ------------------------------------ After investigating a performance report, we aim to categorize the issue into one of the following three categories: Widespread Issue The issue is reproducible with clear steps and affects a majority of users. User Data-Specific Issue The issue is reproducible but only occurs with specific user data or configurations unique to the report. User Environment Issue The issue is not reproducible for our team and is likely caused by factors such as user-specific hardware, software Limitations While we will make every effort to find a resolution, the wide variety of PC configurations and unique setups means we cannot guarantee a solution for every issue. As a small team, our resources are limited, and not all troubleshooting posts will lead to a definitive resolution. If we have investigated the issue to the best of our ability and cannot replicate it on our end, and the issue is categorized as User Data Specific or User Environment Specific, we may have to conclude our efforts. We appreciate your understanding in these situations and encourage users to continue to share insights with the community, as others may be able to offer helpful advice or solutions. 1 Quote Link to comment Share on other sites More sharing options...
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.