Retro808

Make sure when you extract the theme from the zip in it contained in a folder titled as the theme is title. So once extracted the theme should appear in your Windows folder like this: \Launchbox\Themes\[Theme Folder Name] When you open the theme folder you should see the theme files. Make sure it did not get extracted into a secondary folder. Go back into BB and go to Settings page then >Options >Vies and see what theme is listed there. If it is not the one you want change it from this screen and see if it worked. As long as you extract the files from the archive properly there is no need to unblock the properties.

This is incorrect, just adding a link to the patch file in the emulation tab of the game in LB will not patch the rom. LB is not capable of patching roms on the fly as was already mentioned in a prior post. The game original game rom must be patched by an external program then that new patched rom file needs to be imported or a you can use the plugin that was mentioned to streamline the patching and importing process.

You are not being disrespectful at all and it is understandable to be somewhat frustrated if things are not functioning correclty. However, stating the frontend does not work is inaccurate. Not working for you, sure, but that is a set-up issue not a program issue. Not sure which videos you are watching, but many can be and are outdated so how they might show to set things up could have changed. Even on our Youtube channel things have changed since many videos were made. If you do not want any help figuring out what is wrong with your set-up no worries. Whenever you are ready, my initial request for information still stands. We can definitely get you sorted.

LB and BB work fine. Issues like this typically mean you likely have a setting wrong. Give an example of a platform you imported and the emulator you are using. Screen captures of you LB emulator settings would help. Show the main details page and the Associated platforms page.

Please do not revive threads that are years old. With the influx of new users we seem to have more people reviving dead threads.

No, the full set importer does not do that, reason is it actually does not import files. It just generates a working list of roms. So you would need to just manually delete the folder with the old roms to get them off your drive storage.

Are you talking about the roms? If you download a new rom set and remove the old ones then of course nothing doubles. Then you just need to do as I mentioned in the first post to update your LB build to the new rom set. The easiest way to ensure it works is put the CHD inside your main rom folder for Mame. If you follow how Mame wants CHD filed by default then it is no fuss no muss. One caveat is if you had LB set up Mame for you than LB has some custom command line configs to make it less of a need to do this. Personally, I just file them how Mame likes to see them for consistency's sake.

Have you mapped the controllers in the emulators? LB/BB do not have any interaction with in game control set-up so you need to make sure controllers are mapped in the emulator directly.

If you used the Mame Full Set import option all you need to do is rerun it against your .270 roms. No need to delete anything. Just select the Full Set import option and point it to your new rom set.

Just tested and no issues from within the Xemu exe updating. You might have to download directly from the emulator site. LB does not have anything to do with that. It is not one of the emulator we manage with update notifications.

I fixed your post. Not sure where you copied the text from but it came over all white. Under 20K in games is not too big a count to bog down LB. What would matter is having a large number of auto-populated playlists. On startup LB has to process those lists. However, once in the UI it should not affect anything. Do you get any sort of errors when this occurs or does LB just close out? Do you have logs turned on in your LB settings? If yes, post one of the latest log files. If not, we recommend turning it on.

LB does have logic to deprioritize things like beta, protoype, etc. Assuming your roms use naming convention like No-intro and has beta in brackets (Beta). What version LB are you on? Can you provide an example: Platform and Game and also how the file is named. I am going to assume no-intro.

Well if it works in 113 and not in 268 this goes back to what I mention about roms sets matching the Mame.exe version. Between Mame.exe version 113 and Mame.exe version .268 something changed in Mame that makes that version of rom you have no longer playable in a more recent versions of Mame. It is not uncommon for a change in Mame to occur and a rom no longer work right. Looks like if you want to keep playing that game in cocktail mode you may need to keep a Mame 113 version in your LB build and point that game to that version of Mame.

Not sure on the exact steps you took to do the initial import, but I just tested a new load of Mame .268 roms against Mame version .268 using the LB Full Mame Rom Set importer and there was no issue with the speed hack rom being imported. The only option from the default I changed was to uncheck the "Skip Hacked" option.

Does that game play correctly in version 113? If not then it may be a setting that needs adjusting or just it does not play correctly in cocktail mode. Unfortunately I am not familiar with the game enough to know and I have not set up anything to test games in cocktail mode.

Just to reiterate, I cannot truly confirm why it is not working in cocktail mode, only that one reason could be your rom is too old to work with newer Mame. One easy way to test is download MAme version 113 and see if it works in the old version. It is always best to use roms from a set matching (or at least very close to) the Mame version to ensure the best compatibility. If you plan to run Mame 268 I recommend downloading a more current rom set from Pleasure Dome. I cannot link to roms due to forum rules, but the thread below can help guide you.

I am not sure on the error, but your categories are not showing because you have LB set to “Platform” view. Where it shows “Piattaforma” in the area above the platform names change that box to “Platform Category”.

Not 100% sure why it would not work in cocktail mode. I do not have a cocktail cab to test with it. However, on issue may the rom could have been updated since v113. Your roms are from a set created in 2007 it is not almost 18 years old. It is possible a better dump was made and with changed to the Mame.exe you may need a newer rom. It is always recommended to use rom from a rom set matching the version of Mame you are using. So you may need to update your roms to a version from the Mame 268 set.

Did you rename your main Launchbox folder? When LB runs the installer is names the root folder Launchbox. So typically your games would get copied to \Launchbox\Games\Sega Megadrive\. I notice in your Windows folder image you have yours named LaunchboxLG. Doubt that would cause an issue, but it is the only thing odd I see in your images/steps. Just tested following your steps and it moved the games to my Launchbox\Games\Sega Megadrive folder without issue.

You can see the most updated response on a Linux version here:

I would suspect then something during the Retroarch update. Are your screenshots and save states normally located within the Retroach folder? As mention LB does not touch any of those files when an update occurs. It definitely would not touch save states since that is not even a function of the program.

LB updates do not touch any media files or game import data. So it would not delete any of those. Also LB does not have anything to do with save states, that is an emulator specific file. There is a new feature to help manage launching game save states, but again updates do not touch actual files. Are the save states and screen shots stored in your \Launchbox folder structure or are both of those stored in emulator folders?

Can either of you provide the full error you are getting. Being able to see the stack trace could provide an insight.

Yeah definitely seeing the same. Its not 100% consistent. Maybe 1 or 2 out of 10 times it works correctly but majority of times it does exactly what your video shows.

Ahhh. I see the glitch now. I was focusing on the color swap. What verison LB are you running?