neil9000

Yeah, MAME roms should never be extracted.

Do your manage emulator screens look like these? Also did you previously try to use a different emulator and then switch to the standard MAME?

Its fine. Its often a step overlooked by newcomers. Launchbox needs to know which core to tell Retroarch to load with the game, as you can see a lot of these are pre populated in that screen, but if you want to use a different core you need to click in the core cell and use the dropdown to change to the core you want. Also if the platform you want to use isnt listed at all, then scroll to the bottom of that tab and double click in the empty cell to add whatever platform you like.

Have you told Launchbox to use those cores in tools/manage emulators/retroarch/associated platforms?

Hi and welcome to the community. Those games are probably combined to one entry, if you have (USA) (JAP) and (EUR) versions of the same game they are combined into one entry in Launchbox. You can right click a game and if there is more than one version you can pick which one to launch. So if you have 100 games all with the three regions you will have 300 files (100x3) but they will be imported to Launchbox under the same name so you will only have the 100 entry's but there will be 300 files there, each game will have 3 files attached to it.

The way the scraper works currently is that it ignores anything in brackets, so for example "Wave Race 64 (USA) (Rev B)" the (USA) and the (Rev B) are ignored and just the game name "Wave Race 64" is used by the scraper. So as long as your roms arent stupidly named then they will match and import just fine, i could probably count on one hand the games that failed to match to the database when using No Intro sets. The No Intro naming scheme is what is used as a base for the scraper already so that set should have no issue importing. Hacks and prototypes are a different issue as obviously they are not official games so they are always going to be somewhat difficult to match with media. To be honest the way it is currently done is probably the best and most user friendly way to handle it, we dont want to have users have to mess with .dats at all really, a user should just be able to add a folder/files and let Launchbox sort it all with out the need for 3rd party solutions.

You can try re-installing over the top of your current install. Just go to your Launchbox/Updates folder and either re-install the latest beta or the latest official release directly over the top of your current install. I cant say as to wether this will fix your issue as i dont understand what is currently causing the issue, but re-installing over the top wont harm anything.

Yeah that is not a error i have seen before so Jason will have to advise there, i tagged him in my previous post so when he is around he will see it. I originally thought you were both having the same issue as they are both in the same thread, @Nabizzles issue is a different one and is caused by the Insider builds, myself and another moderator have both seen that issue ourselves. Your issue is unrelated to that and as i say not one i have seen before, its not actually saying one of your .xml files is corrupted as far as i can see, it looks like a deeper issue to this code noob. Also it isnt specifically saying Launchbox.xml as that doesn't exist, it used to a long time ago but hasn't for a long time, so Launchbox should never be looking for that file at this point.

Actually looking at the error message from the OP, it looks like these are different issues. @Jason Carr any ideas on the error here?

This is a known issue with Windows 10 insider builds, Microsoft is changing the way Explorer works and they clearly have some bugs. For the time being you can simply drag and drop the files onto Launchbox and it will start the import wizard as normal.

The next beta should be within the next day or two i would think. If you want to downgrade just go to your Launchbox/updates folder and install the latest official release directly over the top of your current install. You wont lose anything unless you have used the new nesting features as they wont be in the version you downgrade to.

Im guessing this is a scaling issue, which is due to be fixed in the next beta i believe. The default boxes show just fine for me.

Yeah all the 8/16/32 bit stuff rely's on the CPU for the most part. However Dolphin and PCSX2 can definitely make use of a dedicated GPU, the N64 and PSX emulators can as well for upscaling duty's.

This can all be done in Bigbox. Bigbox is already using the same framework as Launchbox Next, Launchbox Next was built to bring the Launchbox interface into line with Bigbox and to aid development in the future.

But if you really want to do that just delete your current platform and run the importer again, this time uncheck all the media downloads as you say you have it all.

Well the problem with doing that is you will end up with thousands of games that dont work in any emulator.

I am on a 55inch TV as well and am about 2 metres from the TV as well. I know that Windows says 300% (Recommended) but thats way to big for my liking, its close to 720p at that high scaling, which looks really bad to me. I found 150% was my sweet spot and as i said 200% is the equivalent to 1080p, so you are effectively running at around 720p on a 4K TV, but whatever works for you i guess. Also i should add if you right click the desktop and go to view you can make the desktop icons bigger without adjusting the scaling.

Well 300% scaling is absolutely huge, any reason why you need it that large? even 200% scaling is equal to 1080p on a 4K monitor. I personally have my scaling at 150%.

This is how mine looks.

Are yo planning to package this up into its own theme, or is it going to be a pack that you copy/paste and overwrite a current version of unified? Im really liking the look of these and look forward to a release either way.

I believe that most people will be using 1920x1080 so its likely set to a minimum for that resolution, which of course will use a lot less real estate at that resolution than what you are using. I believe it was limited because either the sidebar wasnt showing if it had been set to narrow or was overlapping the game view so you couldnt actually see your games, i forget exactly but is was breaking for people with standard resolutions so was limited so people didnt break there setups.

Are you saving a controller profile in dolphin? If so thats possibly the issue you dont actually need to save a profile, just set your controls and those will always be loaded, if you save a specific controller profile you will have to specify that profile to be loaded when launching games from Launchbox, but im not sure how to do that personally, my advice would be to delete any profiles set the controller up then just exit the controller setup screen, then those controls should be used always.

Yeah currently the metadata used is for 0.201, but as @Lordmonkus said if you have a old set you are better off using the old importer, you will still get the new metadata but only the roms you have will actually be imported. The new importer is strictly for fullsets, and the most recent one at that, its not "technically" importing your roms there as you are expected to have a fullset so every game marked as working in 0.201 is added to Launchbox. So that is why you would of had games that you dont actually have, that game must of been dumped and marked as working since the romset version you have, so was added as its expected you have a current full romset for the MAME full romset importer.

Yeah pretty much, Jason bases his dev time on what is most requested by the community, and what gets the most votes in the community polls. I cant say i have seen anyone else asking for this particular feature to be added so its likely not high on the list simply because you seem to be the only person asking for it, and as Jason said it was on a poll and know one really cared or voted for it so dev time was spent on the features people actually wanted at the time.