*SOLVED* [Help Retropie 4.3] Some MAME2003 roms not working after update
-
Hey all,
I've got an issue on my retropie for v4.3. After updating, some roms in mame2003 that worked fine now crash on boot. They never use to before I updated. Theres about 4 or 5 so far but for this example I will use:
*Elevator Action Returns (elvact2u.zip)
*Vigilante (vigilant.zip)Yes the are from the right romset: MAME 0.78 (MAME 2003). The roms are not the issue.
Both of these roms work on a fresh 4.3 image, so I know it's either something to do with my setup (configurations etc.) or a setting in mame2003 or something. I have launched both roms with verbose logging enabled, and the results are below. Sorry for the large copy and paste.
Elevator Action Returns : https://pastebin.com/NFvQLB6b
Vigilante https://pastebin.com/x5Uhy8bT
I am guessing the issue is something to do with the bottom lines here:
/opt/retropie/supplementary/runcommand/runcommand.sh: line 1014: 3204 Segmentation fault SDL_VIDEO_EGL_DRIVER=/opt/vc/lib/libEGL.so SDL_VIDEO_GL_DRIVER=/opt/vc/lib/libGLESv2.so /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mame2003/mame2003_libretro.so --config
But I am not sure what to make of them. Both runcommand and Mame2003 are up to date.
Thanks in advance for any help!
-
one of @gamez-fan’s driver changes?
-
Well a stock 4.3 image works fine.
I've updated a bunch of times since though, so maybe? Can anyone else test?
I am reading this thread right now actually:
https://retropie.org.uk/forum/topic/13638/lr-mame2003-driver-improvement-and-backport/67I'm getting errors out the ass when I try to do a source install. I have uninstalled completely and done a fresh binary install now though. Will test.
-
@mrjordaaany a stock image wouldn’t have their latest updates.
i believe all these changes seem to be getting accepted untested so personally i wouldn’t update unless you’re prepared for it to break! i will try and test soon but not sure when.
-
Nope still not working on a fresh from binary install.
Vigilante is made by Irem and Elevator Action is made by Tatio. Other games by these devs work fine.
-
@dankcushions said in [Help Retropie 4.3] Some MAME2003 roms not working after update:
@mrjordaaany a stock image wouldn’t have their latest updates.
i believe all these changes seem to be getting accepted untested so personally i wouldn’t update unless you’re prepared for it to break! i will try and test soon but not sure when.
Yes the changes are untested although 99% of them should not affect anything other than the games and drivers in question eg i've worked on no source files connected to
vigilante or Elevator Action, it's mostly just adding or fixing up games that were not playable in MAME78 or were missing sound support, but i'll certainly look back over all my
commits to see if any of them might cause more general game breakage across the core. -
@gamez-fan if the compile is broken then it affects everyone no matter what games they play ;)
do you not have a raspberry pi to test compilations on? if not i believe it's possible to cross-compile for a pi/ARM target on a regular PC, but i haven't attempted that.
i would like to help test these things but to be honest it's too many changes for me to keep up.
-
@dankcushions said in [Help Retropie 4.3] Some MAME2003 roms not working after update:
@gamez-fan if the compile is broken then it affects everyone no matter what games they play ;)
do you not have a raspberry pi to test compilations on? if not i believe it's possible to cross-compile for a pi/ARM target on a regular PC, but i haven't attempted that.
i would like to help test these things but to be honest it's too many changes for me to keep up.
Sure of course if the overall build does not compile then every game will be broken per say, im looking over all of my previous commits currantly
to try and pindown the cause of the above problems, and yes as you suspected i dont have an Rpi or have even done a full compile of my
changes i was using an MAME76 Xbox source to compile each code change to make sure it's compatable with the MAME78 src as it's
more or less on a par with MAME76 anyway with regards to the code i have been tinkering with -
@gamez-fan Hey thanks for looking into this. Really great of you.
I have other examples too: Air Duel (arduel.zip) Strikers 1945 II and III as well (s1945ii.zip and s1945iii.zip). Alien3 (alien3.zip) used t o work fine too but now crashes not long after you start the game.
As said I've tried removing configs, copying across fresh roms etc. But testing them all against a fresh 4.3 image there is no issue with them.
-
@mrjordaaany said in [Help Retropie 4.3] Some MAME2003 roms not working after update:
@gamez-fan Hey thanks for looking into this. Really great of you.
I have other examples too: Air Duel (arduel.zip) Strikers 1945 II and III as well (s1945ii.zip and s1945iii.zip). Alien3 (alien3.zip) used t o work fine too but now crashes not long after you start the game.
As said I've tried removing configs, copying across fresh roms etc. But testing them all against a fresh 4.3 image there is no issue with them.
yeah some of the above games are from drivers i've worked on im going to propose that we roll back the MAME-2003 libretro core to before my
very first commit to fix the build and then i'll take the time to fully compile and test my changes as breaking lots of games while add the
extra one or two is not a road a want to go down. -
@gamez-fan Hey thanks, I really appreciate that :) So if mame2003 is rolled back, would simply updating it from RetroPie Setup fix it. Or is it best to unistall, then reinstall the mame2003 emulator?
-
@mrjordaaany said in [Help Retropie 4.3] Some MAME2003 roms not working after update:
@gamez-fan Hey thanks, I really appreciate that :) So if mame2003 is rolled back, would simply updating it from RetroPie Setup fix it. Or is it best to unistall, then reinstall the mame2003 emulator?
Im waiting for a response from the dev's but yes after the core is reverted you'll just have to download and reinstall the fixed version
-
@gamez-fan Sweet sounds good. Thank you.
-
Ok im been studying my commits and the code looks from my end 100% correct on the MAME side maybe the problems being reported
with certain games now not working might be an issue with the Libretro side of the sources which to be honest i dont have much experience
with.Lets take Gunbarich as an example i recently added that game to the psikyosh driver which is the same one which also supports Strikers 1945 II / III
were talking a little eeprom code for the game plus the Rom the inputs and finally the speedups all this code is isolated to Gunbarich thats to say
no other code games like Strikers 1945 use has been altered in any way shape or form so im at a loss as to why this could break any game that
was previously supported in that driver.But i have a hunch of what might be causing these problems maybe the addition of the dreamwld.c driver needs to be declared in more areas
of the source than just the makefile.?? and that might be throwing the emulater off when it has been built from the latest sources i dunno for
sure yet but @MrJordaaany since you can compile the latest sources would you like to test a change for me..?? i'll send you a arc with dreamwld.c
removed to see if that will sort the issues you have reported just simply delete dreamwld.c from the driver folder in your compiler options
i've already removed it from the main source. -
@gamez-fan once a libretro build environment is set up the first time, it is very easy to compile libretro cores for testing purposes.
Are you interested in setting up your environment? If you provide your operating system I'm glad to help you get it done quickly and painlessly. I think your project is very important so I'm motivated to help any way I can! :)
-
@gamez-fan I don't really know how to compile past using the 'install/upgrade from srouce' option under Retropie Setup. Is it not easier to roll back for now and do some testing before pushing another update?
I am more than happy to test though, I just need to know how to apply the update above. Is it as easy as deleting the dreamwld.c file from the drivers folder? Or do I have to be in some compile mode?
Cheers
-
It's ok fellas i'll build a dev environment and test the code changes myself but it wont be for a while as i dont have the time
right now but as i said i've proposed we just roll back the mainline mame-2003 source in the meantime to fix any problems
in the build.But being as im not the custodian of the project it's outta my hands as such i have raised an issues flag over at the git and
no one seems all that fussed TBH i guess maybe their waiting to see if more users have similar problems across all
the platforms that use this core before acting..?? -
@gamez-fan Dam sounds like the only way to fix my issues for now is to use a fresh 4.3 image.
Is there nothing I could maybe copy (file-wise) from a 4.3 fresh image of mame2003 into my current image to revert the changes?
If not im happy waiting while people test things.
Thanks for all your help!
-
TBH i was justing working with the MAME code in the mainline source i know nothing about what you mention above
with regards to images etc etc best i can do is drop a copy of the MAME-2003 libretro core which has all my commits
removed maybe someone can then compile it to help you create an image..?? -
@gamez-fan No problem. I see if I can compile something up then aye? Again thanks for your help :)
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.