bob_the_blob2

Looks like @JoeViking245 has indeed come to the rescue here, he just released this: Tested it out and can say it works great!

Thanks @sandcracker21, that definately helps to narrow things down. I think the biggest lead right now is that it's happening across ALL emulators with that controller. That means it's probably not something to do with Dolphin specifically, but the way the controller is interacting through Big Box (assuming launching emulators outside of Big Box doesn't exhibit the issue). 1) I know you mentioned this, but are you sure you don't have anything mapped to the `Exit` command under Big Box `Options > Controller Mappings` 2) Did you say this happen just in Big Box, or when launching games through LaunchBox as well? 3) Out of interest, can you verify that the controller is registering the correct input when using something like Gamepad Tester 4) Is it only emulators this happens with? I.e if you add any old app to Launch Box, does it close that one down too? Finally, the exit script is also something to verify, but we're slowly narrowing it down

Hey @strigoimare, this sounds similar to an issue I saw that we were discussing here: However, over there we were seeing the issue when opening Big Box via LaunchBox, but opening the Big Box exe directly was working fine. Whereas you say in your report that it's actually LaunchBox that is crashing, is that right? The reason the error persists after updating Dolphin manually is that I believe the problematic file is related to Dolphin plugin for LaunchBox (which is what is used to manage the installation, and is separate from Dolphin itself ). However, for me though, if I went to the plugin manager and clicked the `repair` option, the error went away. Does that work for you? Keep me posted!

Hey @starfiretbt I'll try and help you out here! If you right-click on the duplicate game and choose edit > delete, after confirming the deletion if it's associated with a ROM it will ask you if you want to remove the ROM file from your hard drive as well. You can simply select `NO` and the ROM will remain on disk. The reason it likely imported the duplicate in the first place is that you have `Options > General > Automated Imports` turned on. If you prefer to import your games manually you can turn that off, but it sounds like you want to keep this on, so we can try and see why it imported this duplicate. As you said, an easy way to check this is usually to compare the paths in the `Launching` section of the game, very strange that it's showing an entire folder. What platform is this for? And what is the extension of the original ROM compared to what the duplicate tried to import? Once you delete the duplicate it shouldn't try to auto-reimport it unless you run a manual scan. Hope that helps, let me know how you get on.

Hey @sandcracker21 It sounds like your issue could be due to several factors. I'll try to help you figure it out. 1) it's possible that your GameCube controller is registering a tap and a long press as different inputs. The original GameCube controller is analog, meaning a fully pressed button can be registered differently from a partially pressed one. This might explain why the issue only occurs when you hold down the L button, if your controller behaves like a standard GameCube controller. 2) some controllers map their inputs to keyboard inputs. I've experienced issues where a controller input triggers a function mapped to a key input. To check this, do you have any keyboard shortcuts mapped in Dolphin for the `STOP` or `EXIT` functions? If so, try removing those shortcuts temporarily and see if the problem persists. This might not be the cause since the issue doesn't occur when launching Dolphin normally, but it's worth ruling out. 3) are you running Steam in the background? It might sound strange, but I've had problems where Steam's controller mapping for desktop use causes double inputs in Big Box. Try closing Steam to see if the issue still happens. 4) if you go to Manage Emulators > Dolphin > Edit Emulator > Exit Script in LaunchBox Do you have anything configured there? 5) Does this happen for other emulators launched via Big Box (with the same controller)? I'm not sure if any of that will help but hopefully might help to rule out a few things. Let me know how you get on.

@Penlab I saw this and realised it may be the solution to a problem I'd been having for ages. I had the same issue with platforms like Famicom Disk System, Nintendo Satelaview and Sega Naomi. Low and behold, it's as you said, they were getting scraped as systems different to what RA categorises them as. Thanks so much for uncovering this! For you though, apart from Neo Geo Pocket are you still seeing other games that have achievements not showing correctly, or it's all good for you now?

Is this still not working for you guys? For me, after repairing the affected plugin via the plugin manager I was able to launch BigBox with no problem and it hasn't happened to me since. Was curious if it's the same for you are continuing to get that error.

@Truest1 I had this issue too, it seems to be an issue with LaunchBox having a lock on one of the plugin files introduced in the new plugin manager. Are you opening BigBox via the LaunchBox menu, or are you opening the BigBox.exe directly? For me, opening the BigBox.exe worked but trying to open BigBox through LaunchBox showed the error. The error shows the file it has an issue with is for your Dolphin plugin. In the new plugin manager, if you choose the `Repair` option for Dolphin. Does that help? Also, what sort of device are you running BigBox / Launchbox on?

@skizzosjt thank you so much, this is exactly what I needed! I hadn't thought of it that way, using the RetroArch exe as the Application path, but that worked perfectly. You've made my day! Thanks again

Hi Folks, I'm trying to add additional apps that launch in a different emulator to the main game. The use-case here is for Gamecube games that allowed you to download bitesize games to the GBA's memory using the GBA link cable. I have these games in .gba format and want to set them up as additional apps for the main Gamecube entry. So in my Gamecube Launchbox entry, I create my additional apps and fill out the application path to the .gba ROM. However when I check the `Use Emulator` option and choose RetroArch, it doesn't load, which I assume is because I'm not specifying which core to use. However when `Use Emulator` is checked, the option to add an application command line parameters is greyed out, I'm assuming because it expects the additional app to use the same emulator as the default app (which in this case is Dolphin). I know I can just load these through Dolphin, but the reason I'm trying to launch them with RetroArch is that some of them support Retroachievements. So I tried leaving `Use Emulator` unchecked and use the Application Command Line Parameter instead, but couldn't quite get this to work. So far I've got But I don't know how to pass in the rom file located in the Application Path. Any ideas what I'm missing? Or suggests for a better way to achieve this? Thanks in advance 😄

As of November this year, Retroachievements introduced new functionality to the site that marks games as "Beaten" when a certain series of progression achievements are met. Beaten Games Leaderboard · RetroAchievements It would be amazing to be able to filter by this information in Launchbox, similar to how we have filters for things like "supports", "some earned", "all earned" etc for achievements. It would be ace to have "beaten" as a filter option included here that as well, so that we can auto-generate lists of games that are beaten / yet to be beaten. Would love to hear if others would find this useful

Hi Folks, when using the scan for roms in any platform option i'm having issues with .cue/.bin files. Normally when I run this process the wizard picks up both the .cue & .bin files. What I normally do is just delete the .bin files from the importer and let it import the .cue This normally works fine, however there are some specific games that will continuously appear in wizard (minus the .cue file, but the .bin files will still show up) even if they are already imported. This doesn't affect all games, only certain ones, Does anyone have any ideas why these games continue to show up, and how can I get rid of them from continuously showing up in the import wizard?