Sbaby

I'm sorry to chime in again and say it like this, but unfortunately I'm also almost resigned to this issue. I've been experiencing it for several versions now, and I too frequently have to force close LaunchBox because it completely freezes with no chance of recovery. It's really frustrating. Additionally, I wouldn't even know how to replicate the problem, as it happens unpredictably and, unfortunately, occurs quite often.

Thank you so much for your message! It's always a pleasure to share experiences and I'm glad the information was helpful to you. Let me update you with the latest news: I have passed almost 90% of the new game The Legend of Zelda: Echoes of Wisdom and can draw some conclusions. Using Sudachi (which at the time of writing has reached version 1.0.11), the game works very well, with the only problem of audio problems in the world of nowhere. I read in the changelog that this problem will be fixed soon. As for Ryujinx (of which there is a new fork), I experienced minor problems with stuttering, especially during the initial loading of shaders, and an unstable framerate. However, to my surprise, I have noticed significant improvements through various patches/mods, including the essential [Stabilize FPS Normal Version v1.0.1]. In practice, I used Sudachi most of the time, except when I entered the nowhere worlds, where I preferred Ryujinx because of the more correct background audio. This alternation between emulators was possible without problems thanks to an AHK script that synchronizes my save files between the two emulators every time I start the game. With both emulators, the game runs much better than playing directly on the original Switch console, where the framerate drops are so severe as to become unbearable. Note: I apologize to everyone for sharing Windows experiences in an Android topic but I am dumb and had not read the Android membership group 😵‍💫

Thank you very much for sharing your experience. The same thing happens to me regardless of whether I click on other programs or not. I am attaching a video where you can see that on the first launch, Launchbox remains stuck for a long time. After 50 seconds, I decided to terminate the process via the Windows Task Manager. As you can see, I then relaunched Launchbox, and this time it started correctly in about 10 seconds, with an additional 5 seconds to finish loading the game data. lb_loading_crash.mp4

I’m not sure if it’s related to the fact that I switched from beta 2 to beta 4 and then back to beta 2, but now, when I launch LaunchBox, it often gets stuck on the small loading screen window. It gives the impression of an infinite loading process, but it never finishes. I have to open Windows Task Manager, forcibly end the LaunchBox process, and then restart it. On the second launch, it works fine. Has anyone else experienced a similar issue or have any suggestions on how to fix it? Thanks! 🙏

Thank you for the prompt support. In the meantime, I managed to successfully restore the beta 2 version by removing the native plugins and allowing them to be recreated automatically during installation. I believe the issue was related to the renaming of these plugins

Beta 2 was working perfectly, but after installing Beta 4 of LaunchBox, when I click on any game, an error appears. I tried reinstalling Beta 2, but on startup it gives plugin errors and no longer works. I then switched back to Beta 4, but I keep getting the same error, making the frontend unusable. What should I do?

I have some Retroarch PS1 games with save files only in .mcr format (not .srm). Despite this, LaunchBox cannot recognize them 🤔

was the first thing I told you to do, run the script with administrator privileges 😜👆

I don't use VirtualBox, so I'm not sure where you got that information. I use both the standalone and portable versions of Parsec on Windows 11 to connect to various machines, including both physical and virtual computers. I also use it on Android to connect to any computer. I had simply mentioned one of my more complex setups to show that Parsec works even in those cases, but in reality, I use it on several machines. As far as I'm concerned, Parsec works perfectly on all devices, so I'm not sure what issue you're facing. It works perfectly for me

I’ve never encountered the issue you're describing. My only suggestion is to try running the AHK script as an administrator. If this works, it's likely a permissions issue, and you can then figure out how to address it accordingly.

I purchased the game The Legend of Zelda: Echoes of Wisdom and on the original console it works worse than on the computer, I prefer to play it with the emulator. I really don't understand those who claim that emulators are illegal. I attach my game wherever I want. It's like asking me if I can't put shampoo in the oven, if I want I can do it without worrying about getting fines. It is Nintendo's job to make anti-piracy games.

I have a hyper-v virtual machine with video card sharing on a remote computer on which I use parsec and connect to daily.... Honestly I have never had to change anything, every night the machine reboots automatically via a BigBox plugin and parsec starts minimized in the systray without disturbing, are you sure you didn't use a portable version? Try reinstalling it in the default folder and use the “RUN WHEN MY COMPUTER STARTS” option.

Hi @Trihy Thanks for the info! Do you happen to know of any other emulator that can run Virtua Striker 1 well? I'm having trouble finding one that works smoothly, and since model2emu has been abandoned, I'm wondering if there's any hope for better emulation elsewhere

That's not true. BigBox doesn't manage additional apps for each game separately. You're confusing it with the classic options. I'm talking about the ADDITIONAL APPS managed by LaunchBox, which are only visible in BigBox in the game details section, and only if they've been assigned. Otherwise, they don't show up at all. Take a look at the screenshots and video in this topic, and you'll understand. Anyway : @JeffitSend us a screenshot of the menu you mean ...

I've been thoroughly testing the Sudachi emulator over the past few weeks, and I have to say the latest version (currently 1.07) is truly impressive. It works significantly better than its predecessor, Yuzu, and even Ryujinx. I managed to complete The Legend of Zelda: Link's Awakening in 4K at a steady 60 fps, with no performance drops or crashes. It's incredible—it runs smoother than a PC game and even better than the original game on the Switch. Of course you have to apply the right mods for some games, but they are easily found. I can't wait for the new chapter from developer Grezzo, The Legend of Zelda: Echoes of Wisdom, to be released on September 26th! 🥰 You can download the latest version here: https://sudachi.emuplace.app To answer your question, the emulator executable is named sudachi.exe, and the game ROM should be in .xci or .nsp format (although the latter is often used for game updates).

Thank you very much for your response and for your appreciation of the use cases I shared. I would just like to point out that I would not want too much emphasis placed on the password protection case, as the other two cases I mentioned, and the several other cases I did not mention, are equally important and deserve equal attention. Upon further reflection, I realize that, despite the length of my description, I may not have emphasized the main point enough: I believe there is a conceptual error in the handling of additional applications in BigBox. To make it clearer, I have prepared some pictures and considerations that can help you understand the problem and find a quick and easy solution. In summary: In case 1: The additional application should be visible and bootable, so in this case the current behavior is correct and should not be changed In cases 2, 3, and 4, however, it makes no sense for the application to be visible or selectable in BigBox, since it is already started automatically. In fact, it should not be possible to start it separately. It would be useful to develop a clear distinction between manual and automatic modes. In particular, if a user selects an additional application in automatic mode, he or she should not have the option to start it manually. I hope this additional “quick” information will help to better clarify the issue and I am always available to provide further details. I also updated the BitBucket ticket Thanks again for your time and the team's support! 🤗

I've been using Hypseus Singe for quite a while now, and I really like it, especially for its native support for bezels. The only issue I've noticed is that sometimes, randomly, when launching from LaunchBox or BigBox, the game doesn't load on the first try and goes back to the frontend. However, it starts successfully on the second attempt. I'm not sure if it's the same issue others are experiencing. It happens to me about once every 10 times, but otherwise, it works very well

Hi @JoeViking245 😉 I just wanted to clarify that I don't have any issues myself because I've configured all my emulators to use XInput, including PCSX2 and Xenia, exactly as you mentioned. I only stepped in to try and help the user, and if they manage, they could consider switching to XInput by disabling SDL2. Additionally, I wanted to share something I've experienced: when I leave SDL2 enabled, my controllers work fine when launching the emulators directly, but if I launch them through LaunchBox, some conflict arises and the game doesn’t run properly. I hope this information will be useful to others and to the Launchbox team as well, in any case I have no problem with it, at least in this context 😅

I confirm that I had a similar problem with the active configuration of SDL2 on an earlier version of PCSX2, now I have disabled the SDL2 in PCSX2 and I am using with xinput, for me nothing changes and so I don't know if this problem has been solved, however it would be useful to investigate this for a use of the new excellent SDL2 driver for controllers

Hi @AstroBob Thanks for your interest. First of all, it is important to distinguish between LaunchBox and BigBox. In LaunchBox, I think everything is perfect as it is, because it is more of a management system, while BigBox I see as a real gaming station, similar to a console, so controllable mainly by controller or integrated into an arcade cabinet. This means it has to be user-friendly and intuitive, even for those who are not very familiar with the system, such as children or other family members. I cannot always be the one to handle any problems that arise when someone accidentally starts an additional application that should not be selectable in BigBox. In LaunchBox there are no problems, but in BigBox the additional applications could be confusing, as a user might mistake them for alternate versions of a game. This could ruin the gaming experience and, in some cases, cause malfunctions, forcing me to take action. I think this is an important issue that deserves to be reviewed. Therefore, I am referring to specific cases where I would like to hide the application in BigBox, because it does not make sense to make it visible. BigBox has the ability to manage additional applications to start other versions of games, such as versions from other regions or revisions, and that is great. Additional applications also make sense in 80 percent of contexts, and it is fine for them to be visible in BigBox, but in certain special cases they should be neither visible nor selectable, because they could compromise the use of the frontend. In the first case I mentioned to you a while back, unfortunately I don't remember exactly which game were referring to, but it was probably a situation that required an automatic mouse click to start the game in full screen or to get the focus. I don't remember exactly, but the concept can be extended to many other situations, so I'll give you more examples. A classic example: the use of JoyToKey for controller management of some old and rare game that does not support joysticks, with two scripts: one to activate JoyToKey before starting the game and one to deactivate it when closing the game. If a child, seeing JoyToKey as an option in BigBox, started it manually without then starting the game, the controls would be defeated because there would be no way to properly deactivate JoyToKey. This would cause confusion and a negative navigation experience in Bigbox with wrong buttons. You might suggest that I integrate JoyToKey into an AHK script that also includes game launching, and you are right: for example, for DemulShooter games, I do it this way. Game execution for LaunchBox is done through an AHK script, not the EXE of the game, and this script handles everything. However, there are cases when it is preferable to use the additional applications, such as when you want to configure something only for certain games that use a specific emulator in LaunchBox. In these cases, you cannot set up an AHK as an executable, because you have to keep the extension associated with the emulator. So the best solution is to configure an additional pre-game and post-game application, but it does not make sense for these to be visible or selectable/startable via a choice in BigBox. Another reason why it is sometimes not ideal to use AHK as an executable is that BigBox struggles to handle it as a process, especially when it involves multiple processes, as is the case with Steam. This can compromise focus or pause management, but we are getting off the main topic here. Back to us: another example is a pre-game script that synchronizes saves between Switch emulators. This script, too, has no reason to be visible or bootable in BigBox, since its purpose is purely functional and related to starting the game. Another case concerns an additional application that starts for some adult MAME games and requires a password to be entered before startup. It makes no sense for this application to be visible as an option in BigBox, since it is not functional on its own. The password prompt is already handled perfectly via an AHK script set up as a pre-game application, which waits for the script to finish before starting the game. It works perfectly, so I don't see why it should be shown as a separate choice in BigBox, much less bootable on its own. You can watch a video in operation here : I could give many more examples, but the concept would remain the same: there are many situations where additional applications are critical to the gaming experience, but they should not be visible or manually accessible in BigBox, as this could be confusing and detract from the proper use of the system. I hope I have been clear on this point. In conclusion, I think there are two possible solutions: 1) Give the ability to hide specific applications in BigBox. 2) Keep the applications visible as they already are, but without the ability to start them manually.. I hope this information is helpful to better understand my use case and, if possible, to update the ticket on BitBucket.

I have never had these problems, but now it has been happening to me for a few days. Restarting Launchbox the videos are perfect, then randomly it can still happen that they go black, so I restart and ok

Regarding the common problem of having to click on the game for the badge to appear, I would also like to point out that although the auto-populate option is turned on, the game is not automatically added to the 'Games with saves' playlist until you click on the game and the badge appears. Only after you click on the game will the badge appear and then it will be correctly added to the playlist. Otherwise, the playlist will not populate

Thanks for the reply, unfortunately I don't see any audio related entries in the emulator.ini file

As far as I am concerned, it would seem to work but unfortunately for example for ps1 I have very few srm format saves from an old core, now I use the mcd format, in the retroarch folder for example I have both old and new Castlevania saves, the new ones are mcd but launchbox only sees me the old srm, could you please add support for the other extensions of the saves folders managed by retroarch? It would be nice that this way a user could see them well and manage them better. My retroarch\saves folder 👇 the last save I made was from 2024 👇 Launchbox automatically imported me only the old srm and savestate from 2019/2020, but not the new important saves in mcd format from 2024 👇