Silentnight Posted June 26, 2017 Share Posted June 26, 2017 (edited) Please watch the video carefully: Here you will see me confirm the mame path is correct by launching mame from LB via right click. Mame would not launch if there was an error. I then start the rom "Bezerk". Plays fine I shut it down. Then in LB the imported rom from the same destination when launched: gives the missing rom notification. I'm told this is an error to do with Mame not LB, in yet as you see here mame runs that rom fine. This happpens with any roms imported to LB bar "aliens". Which only loaded when I first used mames default rom folder in the parent directory. After that I set the destination for roms in mame back to the folder where all the others are, and copied aliens back in there. LB now loads that rom with no problem. If anyone can shed light on this, it would be most appreciated. * LB is set to run roms from destination and not copy over. It's also set to not extract roms, have spaces, etc. Edited June 26, 2017 by Silentnight Link to comment Share on other sites More sharing options...
Zombeaver Posted June 26, 2017 Share Posted June 26, 2017 Please please please please please just check your MAME.ini. Please. I'm seriously begging you. I'm not trolling, I'm not being mean, I'm 100% serious - please just check your MAME.ini and see what it has as the rompath. Please. Link to comment Share on other sites More sharing options...
Lordmonkus Posted June 26, 2017 Share Posted June 26, 2017 Something I thought of last night in another thread, when you imported your roms into Launchbox did you have Launchbox copy them into a sub folder of Launchbox or did you tell it to leave them where they were. Link to comment Share on other sites More sharing options...
Silentnight Posted June 26, 2017 Author Share Posted June 26, 2017 The roms are set to be left as is in LB. In regard to the ini file I think we are getting down to the problem. In the mame folder as you can see here: there is no single mame ini file. There is however a folder named so. Link to comment Share on other sites More sharing options...
Zombeaver Posted June 26, 2017 Share Posted June 26, 2017 Yep. It's in the folder. It's in the post I linked above. Link to comment Share on other sites More sharing options...
DOS76 Posted June 26, 2017 Share Posted June 26, 2017 sometimes the ini isn't generated until you load the UI without a game and save config or run the command -cc after the exe in the command line. Link to comment Share on other sites More sharing options...
Silentnight Posted June 26, 2017 Author Share Posted June 26, 2017 (edited) OK this is my rom path and a screen shot of where the roms are in folder, the directory setting in mame, along with path shown for rom in LB. So to be clear I have a folder named MAME and then inside Mame's parent folder and the mame roms I have are separate. I see no reason why LB would cause the rom missing error as shown in the above video with the evidence below, but it does while Mame works fine. Edited June 26, 2017 by Silentnight Link to comment Share on other sites More sharing options...
Zombeaver Posted June 26, 2017 Share Posted June 26, 2017 Everything looks good there assuming your games are in the folder named "ROMS" in that first screenshot. Beyond that I'd just like to see the "Emulator" tab for the game in LB, and then a screenshot of the corresponding emulator entry (you can click "Edit" from the "Emulator" tab in a library entry). Link to comment Share on other sites More sharing options...
Silentnight Posted June 26, 2017 Author Share Posted June 26, 2017 (edited) There's the emulator path, and games shown in folder. As I've said from the beginning, I'm not new to Mame only relatively new to LB. Early last year LB worked fine for me with no issue. I had 100 or so roms all working at the time. This could possibly be a windows 10 creators issue (like the crashing etc others are experiencing). I'm not on a beta build, my LB is the current default download build you have via email link. Edited June 26, 2017 by Silentnight Link to comment Share on other sites More sharing options...
Lordmonkus Posted June 26, 2017 Share Posted June 26, 2017 I know you posted them in the other thread last night but can you post images of your Edit Emulator window and Associated Platforms tab again. Specifically these: Ignore the -state 0 command line parameters in mine. Link to comment Share on other sites More sharing options...
Zombeaver Posted June 26, 2017 Share Posted June 26, 2017 I'm kindof at a loss at this point unless it actually is some Creator's Update thing (and I'm not sure why that'd have anything to do with it, but who knows). When I said that LB is essentially a collection of Windows shortcuts, I was being quite literal. I say that because you can, in fact, directly replicate LB behavior outside of LB simply with a Windows shortcut. For example: I made a Windows shortcut to MAME, and then simply added in the path to the game that I wanted to launch (in this case Berzerk) in quotes at the end. So the full path in the target field below is: C:\Users\cojones\Downloads\MAME\mame64.exe "C:\Users\cojones\Downloads\Test\berzerk.zip" In MAME I have the rom paths setup for both "C:\Users\cojones\Downloads\MAME\roms\" and "C:\Users\cojones\Downloads\Test\" I then made another shortcut for 1944, which is located in MAME\roms\: In this case the full target path is C:\Users\cojones\Downloads\MAME\mame64.exe "C:\Users\cojones\Downloads\MAME\roms\1944.zip"C:\Users\cojones\Downloads\MAME\roms\: C:\Users\cojones\Downloads\Test\: Both of these shortcuts work. And LB is literally doing no more or less than this. It is saying "Take this file and direct it at this other file." It has no deeper interaction with MAME (or any other emulator, for that matter, with the exception of DOSBox) than that. This is on Windows 7, so I can't speak to Windows 10, but all I can say is the behavior you're experiencing is not normal. Link to comment Share on other sites More sharing options...
Silentnight Posted June 26, 2017 Author Share Posted June 26, 2017 As requested. I'm not sure there's much more we can do at this point. Link to comment Share on other sites More sharing options...
Lordmonkus Posted June 26, 2017 Share Posted June 26, 2017 Ok, thanks for the screenshots and believe me, we are working on this issue and trying to work out what could possibly be the problem and we are all equally stumped at this point. Everything you are showing us appears to be correct and should work. If this is a bug on Launchbox it is certainly not one any of us have ever run into and any time anyone has had an issue it is always a rompath issue. Link to comment Share on other sites More sharing options...
Silentnight Posted June 26, 2017 Author Share Posted June 26, 2017 As you all have confirmed, this is most probably an issue outside of LB. If LB is mostly a chain of paths and shortcuts then windows is the middle man here and that's the issue. So a windows update gone wayward somewhere (which may or may not happen all the time) will be hard to pin down. I'm not in the position to do a ground zero of my OS as I use this for my business as well as gaming. It's a rig that's cost me a few grand to build so it's where I work as well as my media centre. So in sum you would need someone with my issue (which may/may not be hard to find) who is prepared to do a windows re-install. I'm not waiting for a solution from you guys, so don't worry. Just ensure this post doesn't disappear. Link to comment Share on other sites More sharing options...
Lordmonkus Posted June 26, 2017 Share Posted June 26, 2017 I really don't believe its a Creators Update because we have people using that without the issue you are having. The problems with the CU stem from video drivers and direct x requiring a reinstall. Link to comment Share on other sites More sharing options...
Silentnight Posted June 26, 2017 Author Share Posted June 26, 2017 (edited) I had read that on another thread and ensured I did a fresh install of the Nvidia driver (I'm on a 1080 ti) and direct x. I don't think it's Mame per say as i've tried the most recent builds UI and basic. Anyway I'm nuking LB for now. I'll try a later build of LB and Mame few weeks down the line for my personal use and see how I get on. Edited June 26, 2017 by Silentnight Link to comment Share on other sites More sharing options...
Lordmonkus Posted June 26, 2017 Share Posted June 26, 2017 The problems with the Creators Update though are in LB starting up or some other error related to DX or .NET. Yours is specifically a Mame not finding roms issue. At this point in time I am going to make a suggestion and obviously it is totally up to you whether or not you want to do it. Try out a command line version of Mame. I use the command line version myself because to me it so much faster to set up. All I do is generate an .ini file and change my rom path in it to where my roms are and it just works. Check it out if you want or don't. The guide has helped quite a few people get their Mame up and running. Link to comment Share on other sites More sharing options...
Zombeaver Posted June 26, 2017 Share Posted June 26, 2017 Alternately you could also try RA MAME. The majority of my MAME stuff I do via RA. That's kindof a whole other can of worms though... Link to comment Share on other sites More sharing options...
Silentnight Posted June 27, 2017 Author Share Posted June 27, 2017 (edited) Ok I've fixed it. A friend mentioned something to me and I checked it out. This again may just be my machine, but here is what I found to be the issue: The ini file on my machine for Mame is not recognised properly by LB in the Mame ini folder. I had to copy the ini file from the ini folder, and paste it in the main Mame directory. Once I did that LB launched the roms and the custom settings for Mame for screen size etc and clip art on screen all worked. It's like a trick question, simple when you think about it, but not readily obvious this would be an issue. So if anyone has any issues in future, ask them to ensure the main Mame directory has an ini file for LB to latch onto, and not have it just sat in it's own folder. Edited June 27, 2017 by Silentnight 1 Link to comment Share on other sites More sharing options...
Lordmonkus Posted June 27, 2017 Share Posted June 27, 2017 Well I am glad you got it sorted but the ini file isn't even looked at by Launchbox so that has nothing to do with Launchbox. Link to comment Share on other sites More sharing options...
Recommended Posts