ojed4r

@faeran Hi! Thank you for taking the time to test it out. I've used two different PCs and the bug happens in both. After you extracted the ROM and shut down BigBox, did you check task manager to see if there were any extra background processes? This is a video I made where I show how to trigger the bug, it has to be a very small ROM, a couple of MBs. At the end of the video you can see that BigBox is still open in the background using task manager, even if I shut it down. v13.21(smallrom).mp4.47f305f3821948538e1f00d9edf44847.mp4

@deathshakespeare Thanks for keeping this plugin updated. You think the issues with the beta could be related to .NET? On the new changelog there seems to be a .NET 10.0 update. Every time they update that component something gets broken along the way, like the bug I've been experiencing since v13.19, as that was the first version that had the .NET 9.0 update. Would love to have this essential feature be available through LB and not having to worry about bugs or compatibility issues. I hope that the plugin manages to work for the next update. Thank you so much for your work!

@Fursphere I can confirm this is not an issue of the plugin, the plugin got updated and works fine on the latest version. On the forum post I shared, I made a video showing that the bug happens without the plugin. It's definitely a LaunchBox issue. On v13.18 this bug doesn't occur.

Hello everyone! First of all, I want to thank you for all the updates, features and improvements that you've implemented to LaunchBox all these years. I've been a LaunchBox user for half a decade now and is still my frontend of choice. I notice that one of the new features for v13.28 is: "New Feature: Added a new shutdown progress window that shows what LaunchBox or Big Box is doing while closing, with a force-close option if shutdown hangs" I was wondering, will this feature close all LaunchBox/BigBox processes running in the background as well? I ask this because there has been a bug since v13.19 that has made me unable to update and has to do with LB archive extractor. The bug can be triggered this way: If you extract any zipped game that is just a couple of MBs in size while having startup screens enabled, BigBox creates a second instance once you launch the game, and even if you shut down LB completely, the program stays open in the background. I go more in depth regarding this bug in the following forum post: Since I have 90% of my roms archived and I like the startup screens, I had to stay on v13.18 since. I just wanted to inform you about this issue and see if it could be fixed for the next update. I feel that the new feature I mentioned earlier could be the solution and finally get rid of this bug. Thank you and keep up the great work.

Sorry to hear that, man. It's disheartening to see people who belittle all the hours of research and effort you invest into a project, as if everything is done in a few clicks. I've also experienced that personally. The work you've done for this community is invaluable. Take all the time you need and don't stress out. Keep it up!

Ok, I finally got the time to test @deathshakespeare updated plugin on v13.27 and see if the bug I mentioned earlier could be fixed. Unfortunately, the bug still happens even with the "Close Extra LaunchBox/BigBox processes" option enabled. I even tried to tinker with adding a startup screen delay and enabling shutdown screens but it keeps happening. It's definitely a LaunchBox issue. Besides that, I didn't have any other major issues with the plugin, it works fine on v13.27 with the games I tested it with. While reading the future changelog for v13.28, I see that there will be a new feature that maybe will get rid of this bug: "New Feature: Added a new shutdown progress window that shows what LaunchBox or Big Box is doing while closing, with a force-close option if shutdown hangs" @faeran @JoeViking245 @AstroBob Maybe they are looking into it?

Ok, I will check it out when I have the time. Thank you so much for the help!

Man you're our hero! This new setting definitely could help to avoid that bug. Can I test this on v13.26 or it has to be on Beta 2? I want to check if maybe the bug was fixed on the latest stable release.

First of all, huge thanks to @deathshakespeare for updating this essential plugin. I haven't had the chance to test this updated version since I've been stuck with v13.18 due to a bug introduced on v13.19 and that hasn't been fix AFAIK, could be related to the .NET 9.0 update. Basically, if you extract a zipped ROM small in size (a couple of MBs) while you have startup screens enabled, LB creates a second instance once you launch the game, and even if you shut down LB completely, the program stays open in the background. I go more in depth regarding this issue in the following forum post: I appreciate if anyone can check if this bug keeps occurring with the updated plugin. To test it, just enable startup screens on BigBox and run a zipped ROM small in size like the one I used in the video, then, close LaunchBox and check if an instance of the program is active using task manager. Looking forward to hear any updates. Thanks!

@faeran Hi! Thanks for replying to my post and listening to our feedback. However, I can confirm that this is not an issue related to the Archive Cache Manager plugin made by @fraganator His plugin got a .NET 9.0 update and I did the testing with and without the plugin and this bug happens regardless on all versions since v13.19. I immensely appreciate if you can do further testing and help fix this issue that prevents me from updating. Still, thank you so much for hearing me out. Best!

Hello everyone! First of all, I want to thank you for all the updates, features and improvements that you've implemented to LaunchBox all these years. I've been a LaunchBox user for half a decade now and is still my frontend of choice. Nevertheless, and I'm not sure if this is the right place to post this, there has been a bug since v13.19 that has made me unable to update and has to do with LB archive extractor. Long story short, if you extract any zipped game that is less than 100mb while having startup screens enabled, LB creates a second instance once you launch the game, and even if you shut down LB completely, the program stays open in the background. I go more in depth regarding this issue in the following forum post where I demonstrate that this issue wasn't present on v13.18. Probably related to the .NET 9.0 update? https://forums.launchbox-app.com/topic/35010-archive-cache-manager/page/12/#findComment-489632 Since I have 90% of my roms archived and I like the startup screens, I had to stay on v13.18 since. I just wanted to inform you about this issue and see if it could be fixed for the next update. Thank you and keep up the great work.

Same here. The API is probably down

@snaphat Did any of the admins replied to the bug report you made on the feedback forum?

@snaphat So, I wanted to do some testing and see if that bug regarding small size archives could also be replicated on my end, and turns out that YOU WERE RIGHT! I installed v13.21 without the ArchiveCacheManager plugin and if I run a small zipped game with startup screens enabled, the progress bar won't show up. Then, I shut down BigBox and the program hangs as I have to close it via task manager. Can confirm this in the following video were I did the test with a Master System game (a <1mb ROM): v13.21 (small rom).mp4 In the next video, I did the same test but I tried a PS1 game instead (a >100 mb ROM) and this time the progress bar displays and BigBox shuts down properly: v13.21 (large rom).mp4 This is definitely a LaunchBox issue present in all versions since 13.19. In the last video I will show you, I go through the same test I did on the first video but this time on v13.18, the last version where I didn't encounter this bug: v13.18.mp4 And as you can see, I opened the same Master System game as the first video and the startup screen worked without issues and BigBox shut down properly. Perhaps something should've happened during the .NET 9.0 conversion that broke startup screens for small archives.

@snaphat Thank you for taking the time to test it out. It is odd since I had different results on v13.21 in that when I ran a zipped game for the first time (the ROM wasn't cached yet) the progress bar displays and BigBox doesn't hang when closing it. Then, when I ran the game again (this time it should be already cached by the plugin) the bar fails to load and the program hangs when closing it. This led me to think that the issue was the plugin since if you don't use the plugin at all and run archives on LB, the program keeps the ROM on a temp folder and deletes it once you close the game. And did you tried any other emulators besides retroarch?