mame2016: compiled with updated bgfx and bx

Menion

Ok, so I can confirm that my branch compile and the generated mame2016 works :)
Tested on retropie 4.4 and Rpi?3

Darksavior

Mine was around under 4 Hours on a stock pi3b+. Though, are there any reasons to use it? It's a mixed bag of completely unplayable because it's so slow to playable.

Menion

It is not fully true. It is usefull for unsupported or badly supported roms in FBA/MAME2003

jlopezvl

I have made then change say in first post in the function sources_lr-mame2016()
After this only must go to retropie setup and install from experimental packages?
HOw can update first bgfx and bx?

mitu

@jlopezvl said in mame2016: compiled with updated bgfx and bx:

After this only must go to retropie setup and install from experimental packages?

Yes, that should be enough.

jlopezvl

@mitu It worked …. Compiled and working ok … Thanks ….
NOw it Will superb if someone adapt some later versión to retropié … I'll get to compile mame standard but goes slow … not like lr-mame2014 and lr-mame2016 … Maybe some lr-mame2018?

BuZz

Not been following this thread completely but if there is a patch, please do send it upstream to the GitHub for the libretro core.

Barcrest

Mame2003-Plus seems a more workable solution in terms of speed. Nice to see that this works but the speed is the main issue.

toto2000

I also compiled it. It took 5 hours and a half. I tried Akai Katana, a 2010 shoot'em'up by Cave. Runs ok, menus are slow + have choppy sound, but in game, the animation is much better and the game is somehow playable, while being too slow and slowing down when too many bullets are on screen. Games runs at about half speed without tweaking it with frameskip etc. Sound is bad (glitches).

Maybe it would be interesting so have a list of games that run well while not being supported by all other mame/fba emus. We can find some of them on drewtalks YT channel and on few other videos...

markwkidd

@BuZz said in mame2016: compiled with updated bgfx and bx:

Not been following this thread completely but if there is a patch, please do send it upstream to the GitHub for the libretro core.

I'm quoting this request to reemphasize that if there is a patch, please submit it as a PR :)

Menion

I have sent the PR. The patch is a kind of "quick and dirty" I am not sure how much can fit into a good libretro baseline (please see the commits comments)