Retro808

In LB go to >Tools >Manage Emualtors and edit your Mame. Change the Mame exe path to the exe of a completely different emulator and then close the Manage Emulators window. Once done, edit Mame again and change it back to the actual Mame exe file and close out the Manage Emulators. Should get you back and running. We have brought this up to the devs in our beta thread.

Ah, apologies that is for importing by files type or folder. For the full set just make sure the option for "Import Clones as Additional" is checked. It is on by default.

If you want all the versions make sure during import you choose the option to “Combine Roms with Matching Titles”. This will combine the versions into one game listing. Also check the one for “Force Duplicates” to be safe.

@RULLUR @Wanderer189 Can you both try the steps below. This fixed the issue for me as well as @OhBoy

Did you have to reboot LB or were you able to just make the changes back and forth without shutting down?

Try resetting the emulator .exe path. I got that error with Citra and to be honest I do not remember exactly what I did, but I remember reselecting the path was one of the last things I did and the error went away. Again, not saying that was the fix, but worth a try. Edited: Just got the error with PS3. Changed the exe path to a completely different emulator and saved it and exited the Manage Emulators screen. Then went back in a edited it back to the correct exe path and no error. If that did not work try closing LB after you make the first change. Then reopen LB and edit it back to the correct .exe path.

That's incorrect. I test constantly for LB going back and forth between betas and prior versions. I never delete any installer even if newer than the one I am running and LB never tries to reinstall it until I make it do so. Been that way for years I have been using LB and testing betas. If you have Check for Updates on it will ask you if you want to install, but it does not automatically do it. The Background option will. Which is why that has to be off.

Can you provide an image of what you are seeing? You are logging in with the ID you use to log into Epic with correct?

@4monty The beta does not need to be deleted. Just need to make sure to uncheck the box for "Automatically Download Updates in Background". No matter how many installers you have in your updates folder you can revert to any version and use it without LB trying to update to a more current one in your folder if you have that unchecked.

Not sure what version you are on. However, the issue seems to be a timeout issue if you are also downloading from Emumovies. If memory serves me correct I believe there is a 15 minute or so timeout involving EmuMovies API. So until something is figured out the work around is to either uncheck downloading media from Emumovies or run it in chunks of say 500 games at a time. This is likely because you only had one game selected. You have to select all the games you want to download the media for. That option is not a general one that runs the downloader for all games if you select it. So you either go to a specific platform and select all the games or you can be in the All Games view and choose you full library.

Also if you have videos we know some .flv file types has caused issues when in BB is in attract mode. So I would remove those.

@keithhov I would test removing the entire folder of one image type and test. So maybe remove the marquee image folders (do not delete just move out of LB amd them test. If it crashes put the marquee images back and move the clear logos out and test. This way you can tell which image types might be the culprit. I run this same theme on one build and it has no issues on new LB build. Attract mode has been known to have issues when a user’s build has a bad video file or image file. So likely issue is a bad image as you mentioned.

Easiest thing to do is open Mame directly and map that same button/key combo in Mame. I believe it will ne fore the option “Cancel UI”

To add the license is easy. Take the license.xml file you were sent in the email when you purchased the license and drop it into your \Launchbox folder.

Launch the game and then hit tab to go to the Mame settings menu. Choose the option for Inputs This Machine and see if by chance the bindings for those option are different than what you set.

Retroarch you can. LB does not care what the rom extension is, but if you try to import non-arcade roms using Mame as the emulator it will not work. Especially things like NES games. Can you share pics of your Associated Platforms tab for Mame in LB Manage Emulators. You may be missing the platform name and command lines needed to run consoles. If you should happen to be using software list for those consoles there is a plugin made by one of our forum members that will work. Did these roms come from the CoinOps you were using?

I am sure it is some stupid Windows thing. Just to confirm though, all my builds over the years have been Windows 10 with both Nvidia and Ryzen cards. The pc I have used for the past 4 years for all my testing its update history shows a May 2020 update had been done and never had this issue. I have always set the second screen above, unless I was building a Virtual Pin cabinet. So I am curious as to the cause some users have this issue. I have definitely experienced the scaling issues you mentioned though.

Double check in BigBox mapping option that you have your exit combo set for the option listed as "Close Active Window"

This is interesting. My 3 cabinets work regardless of marquee screen position. Good to know this worked for @Benjc. Another option to try when troubleshooting anyone with a similar issue.

I did not think it would, but at least we confirmed. Yeah, it looks like BB is not even seeing the screen is there as usually the marquee would be black if nothing was showing an cover that lovely color you used. What model is that marquee screen?

@Benjc can you try this xaml. Just place it in the CoinOps themes \Views folder and see if anything shows up. This is just edited to work with cut screen that some users had the marquee image showing cut off. Can you share a pic of what your screens look like when in a BigBox theme before testing this xaml? GameMarqueeView.xaml

LB actually does not need a marquee view xaml. All themes that may not have the PlatformMarqueeView.xaml or GameMarqueeView.xaml present in the views should still show marquees due to how BigBox is coded. So you have the same marquee screen type as the OP and it is the same resolution? If you remove those xaml files the marquee does not show for you?

Can you try setting the marquee to a 720 resolution @ 60Hz and see if any change? @C-Beats I doubt he is using a custom marquee view unless he created one. there are not any theme's posted that have custom marquee xaml's.

Probably Emumovies. I do not see it in the media from the LaunchBox Game DB.

Since we seem to have not properly comprehended my request to let it rest and I have been respectful I think enough is enough. Time to lock thread. @KoritsuKyu Glad it is a viable option for you for now. Any issues related to this topic that might come up please start a new thread.