Jump to content
LaunchBox Community Forums

Recommended Posts

Posted

Can you run mame using the mame.64.exe located in your install folder ?

If you can do that, select "Available" from the left hand column and then in the middle you should see a whole list of games, pick one and double click it to see if it loads.

It will look something like this:5a5fb4a35407e_2018-01-1715_38_54-MAME_NoDriverLoaded___empty.thumb.png.b8a12d569e94de1e2160a98962b1570e.png5a5fb4bb1cf05_2018-01-1715_39_19-MAME_88Games88games.thumb.png.302b86807a8d42d411414cabfb21de30.png

 

Posted (edited)

Nope I’m getting a directx9 error which I missed as CMD was so fast. I’m thinking it could be that issue amd ran into recently with their new drivers so I’m updating them now. Fingers crossed.

Edited by FishMonkey
Posted (edited)

OK I can't figure out why I'm getting this error. I have tried installing direct x from https://www.microsoft.com/en-gb/download/details.aspx?id=35 & https://www.microsoft.com/en-gb/download/details.aspx?id=8109. I also rolled back to amd crimson 17.11.4 which is know to work fine with direct x9.

This is the exact error I'm getting. I'm absolutely stumped as to what's causing this or finding a workaround;

Unable to create the Direct3D device (8876086C)
Unable to initialize Direct3D.
Unable to complete window creation

EDIT; After tweaking the ini it turns out I only get this error in fullscreen mode. Switching to opengl or bgfx fixed this issue. Now to decide what is best to use.

Edited by FishMonkey
  • 1 month later...
Posted (edited)

i made some headway. I have it running from cmd line, but not from LB. I tried logging errors but the error file is always blank. I can't get the cmd window to stay open after launching from LB, but I can see that it can't find the ROM.
Not sure why that is. I tried to do a rom path change to no avail.

UPDATE: I read the noobs post. I guess I have to add the LB rom folder to the ini. I didn't have to do that with RA, guess that's why I was confused.

Edited by dbinott
Posted

Hmm, sounds like a missing rom error, load up the command line window and navigate to your Mame folder the run the the command 

mame64.exe romname

Replace romname with the name of the zip file minus the extension. If there are errors it will tell you what it is, what file it's looking for and where it is looking for it.

Posted

Did you get the problem resolved ?

Sometimes if using a mismatched romset and Mame version there is an update requiring a rom update as well because certain files within a rom zip file gets updated or added. A good example of this was back when the Capcom CPS2 games got updated with a .key file, everything about the games rom zip file was the same but there was a .key file added and if your rom wasn't updated it would crash with the newer Mame build.

Posted

Ok good to hear, yeah the stand alone Mame requires the rom path or rom paths since you can set more than one. And if you do encounter a problem with a game not loading you can use the method I described above to troubleshoot the issue and see what rom might be missing.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...