neil9000

Nah, i'm on 11 and it worked fine for me when i updated both Retroarch, and my cores.

Head to Tools/Options/Updates and check the box for beta's, then head to the hamburger menu/Help/Check for updates.

Interesting, there was a moderator who reported this in our mod server, but when i tested it all worked just fine. So thank's for the report, and hopefully once in the devs are back in there home offices on Monday it can be investigated a little further. Thank's for the report though, and this is why we beta test new features.

You certainly do not need to Re-install, if you cant clear/remap it with a controller or a keyboard, simply close Launchbox and head to Launchbox/Data in windows and delete the inputmappings.xml. Or if you are more savvy than that you could open the file in a text editor and manually add the controller button ID for that action.

This has already been thoroughly discussed in another thread, and is already fixed in the current beta, if you want to update to that. Otherwise you will need to wait until the next official release, that has no current ETA. The issue is when using to two different emulators with the same platform.

You need to tell Launchbox which Retroarch core you want to use for each system, some have defaults but thats all they are and can be edited. Go to tools/manage emulators/Retroarch and click the "Associated Platforms" tab, this is where you tell Launchbox what to use, so find the snes entry and double click the current core and select the one you downloaded in Retroarch from the list. Its also worth mentioning that in this list the platform name must EXACTLY match what you called the platform when you imported it, so if you just called it "SNES" for example you would need to edit the name to that in this same window. Also, the number one bit of advice i can give you is always get the games working in the emulator first, that helps us to troubleshoot, cause there is no point us troubleshooting Launchbox if the roms you have are bad and dont work.

Mame hi scores are available in the "Game Details" menu. It is also possible to set a button to bring them up at any time.

lol, Yeah same. Essentially a game is not credited to your account until you "connect" it upon first launch, thats a Microsoft thing, so nothing we can do to change that i'm afraid.

As already stated Launchbox is not looking for any specific file type, it will accept any file type. My Atari 2600 Roms are also .a26 files, and they import just fine. What emulator are you using for it, and have you checked what file types it supports?

In order for Windows Store/XBOX Gamepass games to be available in Microsofts API, the game must of been launched at least once. You know that annoying connection box that pops up every time you play a game for the first time? Yeah that, so unless the game has been linked to your account via that popup, then it doesn't appear in your library, therefore we can't import it.

Just got this error when trying to import a mame romset while some media was still downloading for another platform. Object reference not set to an instance of an object. App: LaunchBox Version: 12.2-beta-2 Type: System.NullReferenceException Site: System.Object CreateBatchFactory(System.Object) Source: Unbroken.LaunchBox at Unbroken.LaunchBox.Search.LocalDb.CreateBatchFactory(Object ) at Unbroken.LaunchBox.Search.LocalDb.GetMameFileResult(String filePath, Boolean useFolderNames, GameBase game) at Unbroken.LaunchBox.Windows.Processes.ImageDownloader.CalculateInvalidParameter(Func`1 item, Action`2 cust, Action`4 dir, Action`2 v2) at PageComparator.DestroyBatchAuthentication(Func`1 item, Action`2 cust, Action`4 dir, Action`2 v2, PageComparator ) at Unbroken.LaunchBox.Windows.Processes.ImageDownloader.ProcessQueue(Func`1 isCancelled, String activeImageGroup, Action`2 onIndeterminateUpdate, Action`4 onUpdateAction, Action`2 onGameImageDownloaded) at Unbroken.LaunchBox.Windows.Desktop.ImageDownloaderHelp.<>c.ExcludeAwareConnection() at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.CustomizeSessionContainer(Object ) at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.ExcludeInvalidCallback() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location where exception was thrown --- at System.Threading.ThreadHelper.ThreadStart() Recent Log: 11:42:49 Exception

Launchbox doesnt care what format your files are only the emulator does, so Launchbox wouldnt be giving you that error.

Unfortunately this means you are using a pirated Launchbox license. Please purchase a legitimate license, and also remove the currently used license to revert Launchbox to the free, working version.

Retroarch works differently, and is no less prown to errors. They both have strengths and weaknesses. They went there way, we went ours.

And when i say naming is important, i don't just mean us, anything that hits a database needs to be in a format that database understands. Try adding the middle Harry Potter film to KODI, with a file name like harry potter (3) (avi), it wont.

Region, or any other data other than the actual game name, should always be inside parenthesis, so for example Actraiser (USA) will be seen as Actraiser, and the USA as it was bracketed, is absorbed and logged, but removed from the UI itself. A game called Actraiser (USA) jp would be very different, as the jp would be included in the actual game name, and could confuse the scraper, and metadata as to the region. It's also of course possible that none of this is the problem and it may be a issue, just wanted to point out naming is very important.

Then with all due respect you are doing something wrong, it's a very simply process. Go to Tools/Update metadata and media wizard, check the boxes for the art you want and click OK.

Isn't that the location of the bug he pulls out with those tongs?

You download them from directly within Launchbox.

Your gonna need to be more specific than "messes up" that is of no help with troubleshooting at all. FYI though, updating Launchbox does not touch any of your data or media, so i'd say you have deeper issues, but again without specific details i wouldn't know where to start.

Clear logo's are available on both emumovies and our database, both are free.

Should "just work" as anything in the Launchbox folder is using relative paths, so drive letter doesn't matter.

Found this with a very quick google. "You can do it on the command line. Use -n to select the system menu and -C to set DefaultISO to the disc you want."

You can launch emu's from the game details screen.

Try going to your Launchbox/Metadata folder and deleting the metadata.xml while Launchbox is closed. Then open Launchbox and go to the hamburger menu, then help, and force update the metadata, and see if that solves your issue.