AZUR3US

I played Ryujinx for roughly an hour and then closed the emulation. As soon as it had fully closed and focus returned to LaunchBox, LaunchBox froze. LaunchBox doesn't seem to freeze in the background while playing, though, only once the emulation is closed or something like that. My mouse cursor was still in the middle of the display, and it was still highlighting a game in the overview (blue border around the game/box) before LaunchBox finally hung. Tested on 14.0. I don't have an error code or crash report, only logs that LaunchBox created. Debug 2026-08-16 05-26-26 PM.log MediaEngine 2026-08-16 05-26-36 PM.worker.log MediaEngine Client 2026-08-16 05-26-36 PM.log

@JoeViking245 I took a look at LaunchBox 14.0 because I saw a video where the new features were presented https://youtu.be/b_L0atdHp-0?si=6WCdmGD53btjrzvo&t=527 Apparently, game time tracking should now also work when the emulator is no longer in focus. So I tested it with BezelLauncher to see if game time tracking works with BezelLauncher, but unfortunately, it doesn't. There still seems to be something wrong somewhere.

I had the same problem. LaunchBox froze and didn’t respond to anything. I even left it running for an hour to see if it would recover, but unfortunately it didn’t. I don’t have an error code or anything similar. I can’t pinpoint the exact cause, except that the problem always occurred after a longer gaming session (>1 hour). I’m currently only playing with Ryujinx. As a test, I ended multiple times the game after ~5 minutes, but so far the issue hasn’t occurred under those circumstances. I switched back to the latest stable version. I haven’t tested 14.0 yet.

I wouldn't say it's completely fixed yet, but we're very close to the ideal solution. If it can't be improved any further, though, then I'd say it's fine. 🙂 LaunchBox doesn't need to be restarted. It's enough to click "Save" in the main menu, and after that "Test" works as expected. You just need to know that the settings have to be saved first. 😅

I was going to message you that I'm still getting the same error with Beta 2, but then I spent some more time investigating since you wanted the logs. After checking the config, I noticed that the decimal values are actually being saved correctly, using "." instead of ",". On the second launch, it suddenly clicked "Test" without any errors, which left me a bit confused. The issue seems to be this: as long as the values haven't been written to the config by pressing "Save" in the main menu, they're apparently kept in some kind of temporary storage, where decimal numbers are still being treated with "," instead of ".". However, as soon as I press "Save" and the values are written to the config, everything is correct and "Test" works properly from then on. Beta 1 actually worked as well. I tested it again. It has the same bug as Beta 2, where the values have to be written to the config by pressing "Save" before everything loads correctly. By the way, if I've already saved the config and worked around the bug so that "Test" works correctly again, then changing the Scanline value to a new number immediately triggers the bug again. I have to go back to the main menu, press "Save" again so the values are written to the config, and only then does "Test" work properly once more. SetupLog 2026-08-05 17-05-52.txt BLSetup.xml log 2026-08-05 17-05-41.txt edit: If I edit the config manually and replace "," with "." in the decimal values, it works as well. This also worked with the previous release.

I tested it with three different emulators, each using a fresh configuration. The same error occurred every time. I thought you were forcing decimal numbers to always use a "." regardless of the language or it seems like it's not working. =/ BezelsLauncher still saves decimal numbers with a ","

I think that when I move the slider with the mouse, it only moves to whole-number values, so no decimal separator (comma or period) is needed, and therefore no decimal value is ever saved. When I use the keyboard arrow keys, however, the slider moves in increments of 0,1(0.1), so the value is saved as a decimal number, which is what causes the issue. I think decimal values should always be stored in a consistent format and should not depend on the system language or regional settings

Normally, I only use BezelLauncher for N64 games, which is why I only noticed this issue there. To test it further, I configured BezelLauncher for 3DS using Azahar. Unfortunately, the exact same issue occurs there as well. The game launch count is tracked correctly, but playtime is not. I normally use RetroArch for 3DS, and with RetroArch both playtime and launch count are tracked correctly. Is there any way to make playtime tracking work when using BezelLauncher? I also found another bug in BezelLauncher. It can be reproduced by using the keyboard arrow keys to move the slider instead of dragging it with the mouse. This causes decimal values to be generated and saved. Even if I use the arrow keys to navigate back to a whole number such as 1, 2, 3, 4, or 5 and then save, the result is the same. After that, whenever I click "Test", I consistently get an error similar to the one below. In BLSetup.xml, moving the Scanline slider with the keyboard arrow keys causes the following entry to be written: <ShaderRect>0,0,0,0,0,0</ShaderRect> This contains six values instead of four, which results in the error. I wanted to report the error to you exactly as it appeared in English, so I switched LaunchBox to English. Surprisingly, the issue was no longer reproducible... although my existing configuration still produced the same error. I eventually figured out why: in English, decimal numbers use a period, whereas in my case (German), decimal numbers use a comma. This appears to cause the values in ShaderRect to be parsed incorrectly, resulting in six values instead of four.

I assume I'm doing something wrong that's preventing playtime from being tracked. I would have expected to find other reports about this, or am I the only one who's bothered by this? I actually noticed this issue about a year ago as well. However, since I was playing less at the time, and not playing N64 games anymore (it's the only platform where I use BezelLauncher), I didn't look into it any further.

Hello, I couldn't find anything related to my issue. I'm using the latest beta version of LaunchBox as well as the latest version of BezelLauncher. I have BezelLauncher configured with both bezels and shaders for my N64 games. When I launch a game and later exit it, the playtime is not tracked. However, the number of times the game has been launched is recorded correctly. If I disable BezelLauncher for N64 games, playtime is tracked correctly again. I'm using Rosalie's Mupen GUI as my emulator for N64 games.

I’ve now found the cause of the problem. I started my main LaunchBox installation with a fresh "Settings.xml". After setting up everything I needed, I wanted to check if it was still working and it wasn’t. The config file was no longer being loaded in RetroArch. After some trial and error, I figured out that it’s related to the RetroAchievements login data. If you’re not using RA, "--appendconfig *.cfg" works just fine. As soon as valid login credentials are entered, it stops working

I’m having exactly the same issue. "--appendconfig" doesn’t work for me either, and I spent half of yesterday messing around with it… Using the command with "-c *.cfg" does work, but it ends up overwriting the entire RetroArch config, which obviously isn’t ideal. Today I tried something else. I installed LaunchBox (13.24) on a different hard drive and let it install RetroArch. Then I dropped a test.cfg into the RetroArch folder and ran "--appendconfig test.cfg" via the command prompt and surprisingly, it worked. After that, I pointed LaunchBox to my actual RetroArch folder as the emulator, and it still worked exactly as expected. For testing purposes, I then deleted "Settings.xml" from the Data folder and restarted LaunchBox, and suddenly "--appendconfig" also works in 13.25 Beta 3. No idea which LaunchBox setting was blocking the command from running

I resolved the issue by updating .NET. When you start ArchiveManager in a console, it gives you an error message about an outdated .NET version and provides a download link to the latest version of .NET.

Thank you very much for your support. ❤️ When I tried to run it in the console, it gave me the following output: It was not possible to find any compatible framework version The framework 'Microsoft.NETCore.App', version '9.0.0' was not found. - The following frameworks were found: 3.1.32 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] You can resolve the problem by installing the specified framework and/or SDK. The specified framework can be found at: - https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=9.0.0&arch=x64&rid=win10-x64 I followed the link and downloaded it. Now my console output looks like yours and ArchiveManager works for me as well.

When Launchbox isn't running, there is a "Temp" folder, "7z.dll", "7z.exe", and 3 txt-files in my ThirdParty/7-Zip folder. In the attached file, you can see the files that are present when Launchbox is running. When I want to start a game that needs to be extracted, a game.ini file will be created with the following content: [Game] GameId=767c24f8-e2a6-4281-9a5e-6a5a45a0e1de ArchivePath=F:\Spiele\Redump\Nintendo - GameCube (Europe)\Pikmin 2 (Europe) (En,Fr,De,Es,It).zip Emulator=Dolphin Platform=Nintendo GameCube Title=Pikmin 2 Version=(Europe) (En,Fr,De,Es,It) SelectedFile= DecompressedSize=0 KeepInCache=False EmulatorPlatformM3u=False MultiDisc=False I have tried a fresh installation of Launchbox, but I still get the same error message...

I'm on the latest Launchbox beta and when I use your modded plugin the following error occur: "7-Zip returned an error when trying to extract the archive." log file without any issue or hint... The latest version of ArchivManager works for me. events-2025-03-30.log

Hi and thank you for your anwser und sorry for the very late response... My updated sets was in a new folder, but on the same drive. I have pointed launchbox by platforms to the new folders and then I scanned for new roms and I thought, that launchbox cleans by that step the old entries, which it can't finds anymore, but no. I thought I could run "scan for deleted roms" that it now cleans out the missing files/pathes, but it deleted the entire games were the names have changed. After I rescan for new roms it was like a new entry for each game and my editied metadata/settings were lost

Hello, after a long time I have updated my Romsets and many filenames have changed. Now Launchbox can't find the roms of the games with changed names. I tried to re-import the sets, that Launchbox can recognize the changed names. I've also allowed to import dublicates. over "tools -> scan -> for added roms in any platforms/currently selected platform" I've tried also. with the duplicated roms I tried to use "tools -> file management -> consolidate roms for current platform" but all that doesn't solve my problem. Is there any way to scan for, without to edit the xml's by hand? I know, that I can delete a platform and start new, but I dont want to lose my settings...

Hi, I would like to see, when the playtime is editable to add my tracked playtimes. If I edit the <PlayTime> in a platform xml, launchbox crashes while startup. When I start any game through Launchbox, to see how Launchbox write the tracked time, the playtime is still zero, but the time in Launchbox was tracked.