faeran

Custom themes are designed in the way that the author of the theme intended, so depending on how the theme was coded, it would determine how the default Windows DPI settings affect it. Most themes tend to get built to ignore DPI settings so that the theme can display the same way regardless of resolution or DPI settings. The second screenshot you posted is actually not text being cut off, but it's an image used in the wheel that gets auto-generated and then cached for when you do not have a clear logo image for a specific game. My guess is that after you changed your DPI back, you may simply need to clear your cached images so it can regenerate one at the correct DPI setting. The setting is found under Options > Image Cache

Don't forget, as I mentioned before, to leave the depth alone at 1, and increase the height and width until you reach your desired size.

You have to play with the height and the width, not just the depth.

What you are noticing here is the system working as intended, as the 3D model adapts to the size of the spine. However, you do have the ability to override this logic by editing the specific platform, going into the 3D Model Settings tab, and setting up an override for the platform. There you can force a particular size. If there's a game that goes against a platform's standards, you also have the ability to set a specific size on a per-game basis under a game's Edit window, under its 3D Model Settings.

For anyone reading this thread in the future, as C-Beats eluded to, if you want a surefire way of checking if a platform image exists, go into LaunchBox, right click one of your platforms and edit the platform (or go to Tools > Manage > Platforms and enter into one of the platforms from there). On the right side of that window lists all available images that LaunchBox can read for that platform, and you have full control to add, edit, or delete platform images from there. No need to dive into any folders or memorize any platform names

At the moment the only device that I believe has NAS support is some of the Nvidia shield TV models. This is more to do with the fact that Android doesn't have universal network share support built into the operating system. So, if you think about it, if we built support to read network shares into LaunchBox, and then try and send the file path to the emulator, they'd basically return an error not understanding where that path is. In saying that, I wouldn't necessarily rule out some type of network share support in the future, but it wouldn't be nearly as smooth as if Android itself started supporting network shares.

Beta 4 is out that helps with overall stability of the app, and helps with downloading game media that is visible on the screen when using the automatic media download feature. This is our last major push before we can finally release this stability release and move onto the next major features on our list. Changelog: The automatic media download feature will now download media for games that are visible on your screen Fixed the media download indicator appearing incorrectly in some situations Fixed potential crashes in filter sections like "Recently Played"

Thanks. We'll have this improved in the next beta. However, it'll be a balancing act between performance and media downloading. For best performance, it's always recommended to use the Download All Missing Media option in the top right menu.

What is the error message that you receive when you try and upload the image? Also, are you able to provide one example image here for us to take a look at?

Beta 3 is out with the immediate fixes for crashes related to the statistic syncing feature, along with a fix for touch screen inputs with some default game views. Changelog: Improved stability when navigating game lists while game statistics syncing is enabled and while downloading game media Resolved issue preventing touch interactions on some game views (introduced in beta 2) We are still in the process of fixing up a number of issues, crashes, and smoothing out a number of other processes. We should have another beta with those fixes in the next day or so. Once that is done, we are looking to make this live in short order.

Think you were confusing the statistic sync crash with the touch screen issue. Beta 3 is out that fixes the touch screen issue you were seeing. Sorry to hear. If you did want to send me a PM with any specific feedback, I'd be happy to hear it.

We think we've narrowed down this particular crash. For anyone that reads this and is crashing during beta 2, turn off cloud game statistics syncing and see if that helps.

Can you try something. Go into your LaunchBox\Data folder, move the Settings.xml file to somewhere outside of the LaunchBox folder temporarily, then open up LaunchBox and see if there's any difference. Also, don't forgot to provide all the information within this post, which will be helpful to narrow it down.

Sounds like you may be using a specific image type in your coverflow instead of using an image group. There's a few different ways you can fix this in your code. PM me if you'd like to learn.

Actually, I think we figured out what is going on, and it's related to touch inputs. We'll have that fixed in the next update. Thanks for the report.

If I'm reading this right, this is not something we've seen before. Are you able to provide some information on your situation, like which platforms you see it on, the theme and view you are using,, whether you are using the video streaming feature, whether you have media already downloaded or not for those games, and map out the steps you are doing and what exactly is happening.

Beta 2 is out with the following changes: Improved video handling for Custom Themes that remove the background or foreground video elements, automatically playing a video regardless of the user's View setting The media download process has been optimized for smoother performance, helping devices with limited resources Streaming videos will now automatically pause when your internet connection drops Added media indicators to all default views, so you'll always know when images or videos are being downloaded behind the scenes For Theme Developers: We've added new bindings that will give you more control over showing users when background media downloads are happening. Head over to the Documentation.pdf file in your Themes folder to learn more about these new bindings. Fixed a potential crash while downloading game media, especially on devices with lower resources Fixed crashes relating to the platform saving process Fixed an issue where a screenshot may not have displayed under certain conditions Fixed rare issue where where downloaded images on the games page wouldn't always display correctly until the view was refreshed Fixed an issue where a video's audio might play unexpectedly However, be aware that we still have a bit of a nasty crash on low powered devices that we are actively looking into. If you do experience consistent crashing, let us know which device you are using, what exactly you did to cause the crash, which platforms you see it on, the view you are using when it crashes, whether or not you have images downloaded already or not, and whether you are using the video streaming feature.

First thing you would have wanted to do is check the default theme and see if you were experiencing the same thing as your custom theme. That would rule out any kind of theme related issues with plugins or anything like that. I did a quick check with a number of themes, including yours, but I am not seeing any issues on the latest versions. It's possible that with you jumping from such an old version to the latest versions, some user configuration might have needed to be done somewhere. It's hard to say for sure though.

Not quite the section for this, however, at the moment this is not possible. What you could do is set up a hotkey that would bring you to the Game Discovery Center, and another one to bring you back to the Platform Categories section. Essentially, Big Box is set up with a lot of root sections, you seem to use the Platform Categories section, others might use the Platform section, or playlists section. Game Discovery center is another section independent from all other sections. It's possible we may revisit this in the future to provide some further customization, but there's going to be some challenges there, and I'm sure we won't be able to handle all mix and match situations, but at some point we'll give it a go.

Based on the OP, there's a lot of information missing on where he actually is and what theme he's using to really give any kind of conclusion on what's happening there.

This scenario looks to be working as intended. ChunkRock.mp4 has no relation to either the title of the game, nor the ROM file. Here's another example. Staying in the Commodore Amiga realm, let's say you have imported two games: SpellBound! Spell Bound and I download a video and place it in the video folder, and it's called: SpellBound.mp4 Or maybe I called it: Spell Bound.mp4 Which file associates with which game? Basically, as soon as you go too far with fuzzy matching by guessing if a file has spaces or not, or add any other guesses to the mix, it's easy for the whole system to create false positives. Now in saying all of this, this whole system we are talking about is for fallback purposes. It's always recommended to use the LaunchBox standard naming convention, which in your case would be Chunk Rock-01.mp4. Better yet, users should be using the Edit Game window to associate videos to their game, the system will then choose the best performant way of associating that media to the game.

Can you provide the following information from one of the games you feel isn't working as intended. Screenshot of: Edit Game's General page Edit Game's Launching page The location of the image and/or video and its name

Version 13.13 - Released May 13, 2024 Full Changelog: https://www.launchbox-app.com/about/changelog New Feature: LaunchBox can now automatically download and install the Dolphin emulator during the import or auto-import workflows New Feature: PCSX2 emulator can now be automatically downloaded and installed directly within LaunchBox New Feature: Download, update, and reinstall supported emulators (including RetroArch, Dolphin, and PCSX2) conveniently from within their dedicated Add/Edit Emulator window New Feature: A new "Dependency Files" section is now available for supported emulators within their emulator window allowing you to more easily manage these essential files. Supported emulators include: RetroArch, PCSX2 New Feature: You will now receive a prompt, with potential solutions, when you try to play a game that requires missing dependency files Improvement: The Manage Emulator window now displays emulator versions and update availability for supported emulators Improvement: The default Dolphin command line now automatically includes full screen mode and disables exit confirmation prompts Improvement: Microsoft Xbox xbe hard drive files now integrate better with our auto-import feature Improvement: The advanced search functionality has been expanded to include the following new filters: Broken, Complete, Favorite, Hide, Installed, Notes, PlayMode, Portable, Rating, Region, Series Improvement: Several file extensions have been added to the ROM import blacklist, improving accuracy and reducing the chance of including unwanted files Improvement: "View 3D Box Model" option is now available in the game context menu Improvement: Updated the MAME metadata file that's included with LaunchBox Improvement: The ROM Import Wizard now leverages the new dependency files logic Improvement: All Storefront IDs are now accurately displayed in the combine games drop-down window Improvement: The PCSX2 command line now automatically updates the fullscreen switch when pointed to the QT version Fixed: Wiki/Video URLs correctly update when using "Search for Metadata" from the Edit Game window Fixed: Resolved an issue where GOG games already imported were sometimes re-imported as additional applications Fixed: Auto rom scanning now accurately detects folders in some situations Fixed: The custom field sidebar filter now functions correctly in all circumstances Fixed: Big Box memory leaks have been addressed, allowing it to run smoother and for extended periods Fixed: Searching for games with colons (':') should now yield expected results Fixed: Various potential null reference errors that could occur within LaunchBox have been squashed Fixed: The manual scan for added games no longer gets stuck during the initialization process Fixed: Updating MAME now correctly installs the new version to the same folder (introduced in 13.12) Fixed: Import stability improved for scenarios involving merging new and existing games Fixed: An uncommon issue that could occur during Epic Games imports Fixed: An issue where the set media limit wasn't enforced during imports or metadata and media downloads Fixed: The version badge now displays correctly when combining two GOG games Fixed: A bug where images could incorrectly be linked to more than one game with similar names Fixed: The Amazon Games install flag now sets correctly on startup Version 13.14 - Released May 16, 2024 Improvement: Added a final file matching step for loose media files. This will attempt to better match loosely identified media with games without causing incorrect matches. Fixed: Resolved an issue where the last page of the ROM Import wizard would be skipped in certain scenarios Fixed: Addressed an issue where a Dolphin update would install to an unintended folder Fixed: Updated our internal Dependency Files database with various fixes Fixed: Ensured the Dependency files indicator light accurately reflects the status of files within specific subfolders Fixed: Resolved an issue where using the Dependency files feature to browse for a file could lock the file if you tried to select one already in the correct location Fixed: Resolved an issue with an emulator's configuration information under certain conditions when the emulator is first downloaded Fixed: Improved PCSX2's ability to identify the bios folder location in all scenarios Fixed: Addressed a rare occurrence where the Dependency file lookup would fail when users played a game

The standard way media file matching has worked is by matching the title of the game and switching special characters to underscores and adding numbers at the end. So Bonk's Adventure would turn into Bonk_s Adventure-01.mp4 and if you had a second video for that game it would be Bonk_s Adventure-02.mp4. Whenever in doubt, it's always recommended to use our in-app tools to associate your media files, like through the Edit Game window. We also have fallback logic where you can match it to your ROM filename. So if your ROM file is Bonk's Adventure (Europe).zip, then you could have your video file named Bonk's Adventure (Europe).mp4. It's a bit less performant but does the job. We fixed a bug that was being overly aggressive, more so than its original intent (which was file name matching), which was causing media to associate with games it shouldn't have been. The side-effect of that was for people that might have been loose with their naming of their media, there was a possibility you saw a benefit of media also matching with the correct game (when it shouldn't have based on the logic). We are evaluating if there's a 3rd step that we could add that would help in these situations that would hopefully not re-introduce false matches. In saying that, it is highly recommended to use our in-app tools to rename your media to our standard if you can, as it provides the best association with the best performance. The Edit Game window or the Image Pack importer are good ways to do this. Thanks., We were able to reproduce this, and should hopefully have a fix in the next update. Basically what you are seeing is how the matching system works. There are homebrew games coming out all the time (one of the ones you mentioned is from 2023), which eventually makes their way to ROM sets, but haven't quite made their way to our database. Once they are in the database, and the metadata file gets updated to include them, they will end up matching better. We found a potential issue that I think you may have fallen into, which deals with specifically configured PCSX2's when using our updater. This will be fixed in the next update. Thanks. We fixed all the parts that we could. A lot of what we started with was RetroArch's information, and then built on top of that to try and fill in the gaps that they were missing. The good news is that since we did that (instead of just parsing RetroArch's data), it was easy for us to correct a lot of these, which will be included in the next update. At first glace, these potentially look like user configuration type issues. I would open new threads for troubleshooting.

Would be pretty simple to create a custom view with the data points you would want to see. This video should still be relevant for helping with that.