Retro808

I believe one of the new features in 7.11 is the ability to bulk edit rom paths.

First thing I would recommend is to make sure both Mame and Launchbox are pointing to the same Rom directory. Open Mame and check to see where you have it pointing to your roms then in Launchbox make sure it is pointing to that same drive. If when you imported your roms you had Launchbox move them that could cause an issue. Do your roms work in Mame outside of Launchbox?

It is likely because the feature really is not working and not supported much anymore. This previous post mentions the same.

I do not believe so. Sounds for navigation are across the board. I do not see any menu option to use certain sounds for certain platforms. Maybe it could be possible with a plug-in?

No worries. I appreciate the help.

Thanks @eatkinola No luck. Replaced the .dll with the one you linked and unblocked it. Now in the same scenario I get a new error

Thanks @eatkinola I am using v0.96a. In the Platform List views I can change to two views. Wheel 1 and Wheel 2. Wheel 1 view style is the one I get the crash with and it is only when I go to my Playlist. If I select any other platform I get no error. It is the first image below. In the second image that Platform view style I can access my Playlist without the crash.

I am having an issue with playlists when using Platform Wheel 1. In this view I get a crash and the attached bug report. However, if I change the Platform Wheel 2 I do not get the crash. I have changed views several times and each time I use Platform Wheel View 1 and go to my Playlist it crashes. Arcade, Handheld, Console all work in this view. Lovin' this theme by the way!

License duh. LOL. Well to me it's like a membership into an awesome community!

@brave apache When you buy the premium membership for Launchbox there is a code/link in your purchase email for the discount to Emumovies.

Yeah this feature really is not supported much if any.

If you are going to use Launchbox to house the images you need a file of some sort so it knows what to download for. You do not need the rom file you can just create a text file and save it as the name of the game. Without something at least like a text file Launchbox will not know what it needs to download. Then import the text file as if it were a rom and LB will search for metadata.

Glad you at least got some things figured out and back towards a working system.

@Einherjar Try a fresh install of the 1.6.7 RA only do not install it in the existing folder. Make a new folder and setup RA there then test. If it works you now know the older folder something went bad. If the new RA in the new folder does not work time for the needle search.

I figured you did already test but thought to ask so it was mentioned. Not sure what it could be. I had a case where MameUI 0.186 and newer would not open any Mame roms from Launchbox but would open fine as standalone. If I used any version before 0.186 LB had no issues. I could never figure it out. It was just MameUI versions. If I used command line version of Mame 0.186 it worked fine. Have you tried and older version of Retroarch? You did mention you are on 1.6.7.

You mentioned a Mame issue you had before and that Mame would only work as a standalone or if Launchbox was run without Steam. But run Steam and Launchbox would not open the Mame roms. Will LB run those cd based games without using steam? Just asking as I did not see it mentioned and from reading your issue with Mame, Steam was the problem back then.

You can also use Amazon Pay. Looks like there is also a bitcoin option on the purchase page as well.

When you change image files make sure you go into settings for BigBox and refresh your image cache. Otherwise it will just keep showing the last image it cached.

Yep. I did several different loads checking and unchecking different things. I would pretty much get different results on the metadata hits.

Yeah, not to consistant is it. My only real issue was it not catching LB Database names. All the roms loaded, so no strange issues like you two had, it found Wiki meta, just would not find LB Database meta. I had to edit each game and delete the wiki ID then rerun search for metatdata again. On a couple I had to delete the name down to just like House or Dead in order for it to pull any LB data.

Strange. Added DOA games on the second machine as well and they imported clean. When you imported where you on Launchbox v 7.11? There were improvements made related to LB DB searches in 7.11. The machine I tested on is on 7.11. Maybe I will test on an older version.

Prior to your post I only had House of the Dead imported. So I went ahead an tested importing HOD again along with 2, 3, and 4. In both instances Launchbox imported them all. The only issue I had was for HOD 3 and 4 it found only the Wikipedia meta. So I deleted the Wikipedia ID on them and searched for metadata and it found the Launchbox Database title as "House of the Dead 3 (Arcade)" and "House of the Dead 4 (Arcade)". So LB did import them but only found the WIki info on the initial import. Are your roms from a full Mame rom set? How is the rom named for your House of the Dead?

No worries. You got it sorted and that's all that counts.

In BigBox settings you have to make sure you have either a key or controller button mapped to "switch view" option. This will allow you to switch views in the theme you are using. Each of the platforms can then have a different style view.

I have seen a few posts in the past with people having issues with multiple PS4 controllers. The issue seemed to be how Windows randomly sets internal IDs for the controllers and that causing bindings to get mixed up. In those posts solutions were not given so I know it is not much. Just wanted to share I remember seeing others have a similar issue. I can not find the post (it was from another forum I think), but someone had mentioned when opening and closing an emulator is when the ID would change, so one time something like Retroarch would see a controller as Joy 1 then when closed and opened again it would be Joy 2. Similar Issue here and here.