MAME black screen on game launches then resets back to main screen. Have tried but stuck

[OneooneO]

I downloaded and set up a 1.5 TB build ( Scottys Retro build ), and everything works fine except the arcade ( MAME ). I have tried to add another MAME system myself with a Rom set and MAME version I know works, but it's still the same. It's now doing my head in. Any help would be greatly appreciated. 

Edited 13 hours ago by OneooneO

[JoeViking245]

31 minutes ago, OneooneO said:

I downloaded and set up a 1.5 TB build ( Scottys Retro build ), and everything works fine except the arcade ( MAME ). I have tried to add another MAME system myself with a Rom set and MAME version I know works, but it's still the same. It's now doing my head in. Any help would be greatly appreciated. 

Rather than going back and forth with try-this, try-that, what-do-have-for-this, what-do-have-for-that... Try this plugin and see if it can shed any light.

 

[OneooneO]

Will do that now and get back to you asap. Thank you for the post and trying to help

[OneooneO]

It's done, but I can't troubleshoot as it is greyed out. I added screenshots to see if that helps you. I maybe being dumb so sorry but thank you for help

[JoeViking245]

Ahh, yeah.  It's not set up for MAME64.  It looks specifically for mame.exe. Per the description:

• Requires the games emulator to be mame.exe

You might could try renaming (temporally) your mame64.exe to mame.exe, then edit the emulator in LB changing the app path to mame.exe.  Then run the plugin.

I never tested it with MAME64, but it may still work (with the renaming) as it is a derivative of MAME.

[JoeViking245]

22 minutes ago, OneooneO said:

I added screenshots to see if that helps you.

Wait!  mame64.exe?  What version of MAME are you using?  That's an older version, isn't it?

[OneooneO]

0.251 ( year 2023 ) It is what came with the per build 

[JoeViking245]

3 minutes ago, OneooneO said:

0.251 ( year 2023 ) It is what came with the per build 

MAME official didn't.  (at least 0.251 on their site only has mame.exe) But that's OK.  Try the rename thing anyway. 😁

[OneooneO]

I don't know what to tell you, thats the version it says 😅. I did change the name and it worked so thank you. Here is the report on the first time.  Again, thank you as this has been driving me nuts 

88games.zip.txt

[JoeViking245]

3 minutes ago, OneooneO said:

Here is the report on the first time. 

Edit your MAME emulator in LaunchBox.  In the Default Command-line Parameters, add -rompath %romlocation%.  It should end up looking like:

-keyboardprovider dinput -rompath %romlocation%

Unless you only have one emulator setup for Arcade (e.g. RetroArch doesn't have the Associated Platform Arcade), you may want to go to the Associated Platforms section and check the box for Default Emulator.

 

Click OK to save and close.  Try playing the game(s) again.

[OneooneO]

You are a god among men! 85 % ish of them work now so THANK you so much. Some don't put two txt files. What am I missing so i can problem solve the rest myself and not have to bug you ? Again, thank you so much for your help

robocop.zip.txt winrun.zip.txt

[JoeViking245]

8 minutes ago, OneooneO said:

What am I missing so i can problem solve the rest myself and not have to bug you ?

Read the output on the screen?  

When you ran Check ROM(s), it showed you in red that some files are missing from within the zip(s) and what their names are.

This is most likely due to a mismatched ROM set and MAME executable.

Case-in-point:  Your Robocop ROM is for version 0.130 (or older).  The Winning Run ROM is for version 0.201 (or older).  (Don't ask how I found that out because it's a PITA. lol)

 

Solution: Get a ROM set that matches you MAME executable version (e.g. both are for version 0.251).  (That, I can not help you with)

Alternately, remove the game(s) from LaunchBox that won't play because of a mismatched set. (But that's no fun.)

 

Reading the onscreen output:  (e.g. Winning Run)

In the upper right, you'll see that a Device file is required for this game.  When running Check ROM(s), you'll see in the output 

Checking Device file...
sys2mcpu.bin CRC is good

But right above that, under Checking ROM file... was nvram is missing from the ROM winrun.zip.