Dr_Bunsen

So I've read all the posts here and seen at least one person have the same problem as me, but didn't see a solution. I have the latest Mayflash Dolphinbar with genuine Wii motes and Touchmote 1.0 beta 15 loaded in Windows 10. I'm trying to get some MAME .205 lightgun games to work. I find that the X-Y control of the cross-hairs works in Mode 2, but A and B buttons return the same code so cannot be mapped separately in MAME. This is a shame as my gun case has two triggers, one for A, the other for B. In mode 4, re-mapping the wii mote buttons works in Touchmote and I can assign A and B buttons separately in MAME, but the X-Y control is not picked up at all by MAME. This seems strange, as I can see the Windows cursor moving around just fine with the Wii mote in mode 4 when in Mame mapping dialogue but it is not recognized by Mame. Any ideas what I can do to get X-Y analogs to work in mode 4, as I assume I need to be in mode 4 for supporting two guns, which I want to try and do next?

Thanks, I didn't know I could use 7-zip like that to make the folders. I usually use command line to individually unzip lots of files as follows: "C:\Program Files\7-Zip\7z.exe" e *.zip. Great tip, saved me lots of time!

Thanks for the tip, I've unzipped the CHDs, but they weren't originally zipped in directories, so I guess will need to create all 160 directories manually. ?

So I've originally had my own curated set of Mame .194 files working in Launchbox ok. However I decided to update to .205 using the entire romset including the working CHDs. Since I have around 160 CHDs, it would be better if I didn't have to create an individual directory for each CHD within the roms directory like I did with my previous setup (where I only had half a dozen or so CHDs). I included my CHD directory where I have all my zipped CHDs in the list of Mame rom directories, but that didn't work. Am I stuck with having to manually create 160 or so additional directories within my roms directory for CHDs?

@andrea_ita I had the same problem with Dragons Lair Remastered (not running in Daphne) and unchecked "Enable Game Startup Screen". Then the game displayed ok. Maybe this will work with Daphne too. Oddly, Space Ace Remastered did not have this problem and worked fine with default startup screen options. There's clearly something odd with the startup screen implementation.

@neil9000 Ok, thanks, that's a shame. I'd hoped the import did something like clrmamepro. Will have to go back to that tool and remind myself how it works ?. Or maybe just leave the whole set intact, I guess I have enough space on the HDD. Are there any penalties in Launchbox/Bigbox speed for having 35,000 roms instead of a filtered file list of about 10% of this?

@neil9000 Thanks for your reply. What I'd like to do is have the Launchbox Mame importer copy the roms that are selected by the Launchbox filter onto my 1TB HDD, so ending up with a romset of good games without the mechanical/Mahjong etc etc. I thought the Mame romset import worked like the regular rom import where you can leave the files where they are, or copy them to the Launchbox games folder. I want to copy the files, since they are currently on an external HDD, but I only want the files that meet the Mame filter criteria, and I want them to go to the 1TB HDD and not the default Launchbox games folder on the SSD.

I'd like some advice on a specific issue with the way a full Mame romset should be imported on my computer. I have a small SSD with launchbox on it and another 1TB HDD in the computer where the game roms are stored. I have a full Mame 0.202 romset which is 65GB even without CHDs on an external HDD and I'd like to run the Launchbox Mame full set import tool to filter just the useable stuff onto my 1TB HDD. What actually occurs when I try to import the romset with the Launchbox filter is that it populates my SSD since that's where Launchbox itself is installed. There isn't enough room on the SSD to complete the import and then move the roms and run the batch change for location. How do I change the import tool rom destination to my 1TB HDD instead of the default Launchbox folder to stop it filling up my SSD?

Thanks for your replies and help, I gave up in the end trying to get MameUI64 to work with Demon Front and Launchbox. I installed standard Mame 64 and am using this just to run Demon Front currently, which turns out to work ok with Launchbox/Bigbox. This issue has prompted me to update to the latest Mame and rompack and ditch MameUI64, which I will do some time in the future.

@Retro808 Thanks, I followed the tutorial for Mame from Lordmonkus as I've only had Launchbox a couple of months, so I did move the Mame.ini from the ini folder in MameUI64 to the main folder. I just confirmed actually that dmnfrnt doesn't work using command line MameUI64, so I guess that's where the problem is. I don't understand why it would work from the UI interface though. Everything else works fine in command line.

@Lordmonkus Thanks for your reply. Yes the mame.ini is in the main folder with the Mame executable. It seems like this isn't a Mame problem as the game works fine in stand-alone MameUI64.

Demon Front is the only game not working in my arcade setup and I've run out of ideas, so I'm wondering if anyone can help. Using dmnfrnt.7z Mame 0.188 rom, with pgm.7z bios in the games folder. Demon Front works fine in MameUI64, however, in Launchbox/Bigbox the game does not startup and I get MameUI64 error stating it cannot find the files. I have around 1500 games fully operational with the same setup of MameUI64 and Launchbox/Bigbox so I can't figure out what's wrong.

@Nabizzles Thanks, I'll give that a go!

ePSXe works fine stand alone, but opening a game in Launchbox results in * Error can't open sound handler. (try -nosound). I don't even get the PSX boot screen. Using command line parameters -nogui -slowboot -loadbin These command line parameters work fine from within a DOS window. ePSXe is set up with Pete's OpenGL2 GPU core 2.0.9 and ePSXe SPU core 2.0.0. I've searched this forum and someone else had the same problem back in 2016, but it wasn't fixed.