neil9000

That's not really a "error" its simply saying that the emulator you are trying to launch does not exist at the location it was when you imported it.

That looks like video artifacting, caused by a slow hard drive to me.

Make sure your "image type" at the top of the screen is set to the correct image type for snes.

I think they want to import these as a platform and scrape artwork like a rom. While you can import them fine (just add them like roms and choose a pdf reader as the emulator) you wont find any scrapers for this, your best bet would be screenshotting the front page of the pdf. People have done this for comic books for example.

Personally, option 2.

You can click the database ID in the edit window.

Both are in my platform just fine, just using default filters during import.

Yeah those are tied to the EA app and not Gamepass.

You really dont listen do you, i never said it was a power issue, just that requirements for programs increase over time, this was in reference to your quote that a 5 year old version written in a completely different language runs better. Again as as been stated many times in this thread now, that you choose to ignore every time, this unfortunately is a YOU issue, what you are experiencing is not normal, and not what all our other users experience. it has been stated many times now that this issue is likely due to another program or driver on your computer that is poorly coded and interacts negatively with Launchbox/Bigbox not a issue with Launchbox/Bigbox itself, if it were we would have tens of thousands of people also complaining, but obviously we don't.

Launchbox is a completely different program to what it was in 2018. Thats like saying windows 95 works fine on this hardware but Windows 11 uses more CPU, more RAM and takes up more HDD space than that, well yes of course it does, programs march on at the same pace as hardware, specs for any program will be higher than they were five years ago. Also Launchbox got a complete re-write at one point, so it literally is a different program now.

Dolphin absolutely has upscaling options, but id recommend not using the Retroarch core at all, it's far far worse than the standalone emulator.

Its whatever you yourself set, you can either set it in Launchbox/Bigbox and they will handle it, or set it in the emulator itself, nothing like that is pre configured as different people like different buttons for shortcuts.

Your controls in emulators have no relation to the settings in Launchbox or Bigbox, the settings for this in Launchbox/Bigbox are for those applications only. again it sounds very much like you are not in controller mode, you need to do that and im pretty sure Retroarch will then work correctly, at the moment its seeing a keyboard and mouse and not a controller.

Its likely B is set to escape too as a generic "back" button in K&M mode, so that would certainly close emulators with B if thats the case.

Easier way would be to install a fresh build and only add the systems you want and rescrape.

Well there has been no Launchbox update between when Yuzu worked for you and when it didn't, so yeah its not Launchbox as nothing has changed there, Yuzu on the other hand as you say updates pretty much every day. In fact the Yuzu update specifically says that "Yuzu is a experimental emulator and that things will break" while it updates.

Sounds like a bug in the latest yuzu update then.

From our discord.

Same as last time, this is not a Launchbox problem, it is a Retro Achievements API problem, nothing the Launchbox devs can do about this.

Well this IS how buggy things on your system would manifest, not every game or program is coded the same way, in fact they are VERY VERY different, so one bad program/driver absolutely can only effect selected programs. For example Launchbox could be the only program on your PC that uses .NET Core, and you have another buggy program that breaks .Net Core, therefore breaking Launchbox. These things are 100% possible, just saying i play games and they work means nothing, you need to actual help here with some actual troubleshooting of your own too, as all i have seen you saying is its a Launchbox issue, but if it was that simple every single person using Launchbox would also be complaining of the same issue, but this obviously is not the case, so the issue does indeed lay elsewhere, we just need to narrow down what that issue is.

You are on the Launchbox forums, so i assume you play retro games, are you saying you use the analog stick for things like Mario? For me personally the most important thing on something that is for playing retro games is the dpad, it its a bad dpad i avoid the product completely.

The default path is not the AppData folder. As i said though Launchbox is portable and if everything is in the Launchbox folder then yes paths are relative, you can just move the folder wherever you like, including other hard drives or PC's.

Launchbox is a portable app, meaning that everything it needs is in the Launchbox folder, it doesnt store anything in the AppData folder nor does it touch the registry.

Its worth noting the the database is open to all, its completely community driven, meaning you are more than welcome to make these changes yourself, you dont need staff to do anything. https://gamesdb.launchbox-app.com/