Issues with the new MAME core

nickisonlinet commented 2 years ago

I've recently installed the new revamped MAME core (MAME4iOS 2022.0, MAME 0.239) and while it is a huge upgrade, i've encountered some really noticeable bugs throughout the new core.

A list of issues I've experienced so far:

core freezing (happens after a few button presses in some games, I've encountered the issue with Namco Galaxian hardware-powered games so far (Galaxian, King & Balloon). the app doesn't freeze completely however; i can still move some buttons but the core freezes overall)
minor audio splicing (splicing audio occasionally on all games)
crashing overall (happened on a random occasion while playing Galaga '88, don't exactly know how it happened)
lag when opening/closing the notification/control center
graphical errors in games that weren't present in earlier cores (i don't know exactly if this is a general mame core problem or an app problem, but just letting you guys know; occured in TwinBee Yahho during the opening sequences)

(hey thank you guys for pouring your hearts out for the iOS people; i've been using the original core for 2 years and i enjoyed every bit of using it. this new core is awesome and adds up to the expanded experience)

ToddLa commented 2 years ago

I have seen the latest MAME core freeze too, trying to track it done, might be related to audio......

ToddLa commented 2 years ago

graphical errors in games that weren't present in earlier cores

Can you run those games on MAME on a PC and see if same errors exist?

And/or give me the name of a specific romset that has a problem, with a screenshot??

nickisonlinet commented 2 years ago

I’ll try getting a PC screenshot of those with a comparison; I’ll get back to you in a few minutes!

On Fri, Feb 11, 2022 at 9:44 PM Todd Laney @.***> wrote:

graphical errors in games that weren't present in earlier cores

Can you run those games on MAME on a PC and see if same errors exist?

And/or give me the name of a specific romset that has a problem, with a screenshot??

— Reply to this email directly, view it on GitHub https://github.com/yoshisuga/MAME4iOS/issues/373#issuecomment-1036862331, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXXGHKJJQGQQQE4Z7KYVVLTU2WUQVANCNFSM5OFJSG2Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

nickisonlinet commented 2 years ago

Checked and huh, apparently it's an issue with the main core overall; not just an app problem. Must've been a bug generated within the later MAME updates.

If you guys do need it in some form: here's a comparison of the graphical issues; it's not too major but it is noticeable. I've included the specific romset in the image, but if you need it in text form: it's tbyahhoo [image: image.png] [image: image.png]

On Fri, Feb 11, 2022 at 9:51 PM nickisonlinet / Nick C. < @.***> wrote:

I’ll try getting a PC screenshot of those with a comparison; I’ll get back to you in a few minutes!

On Fri, Feb 11, 2022 at 9:44 PM Todd Laney @.***> wrote:

graphical errors in games that weren't present in earlier cores

Can you run those games on MAME on a PC and see if same errors exist?

And/or give me the name of a specific romset that has a problem, with a screenshot??

— Reply to this email directly, view it on GitHub https://github.com/yoshisuga/MAME4iOS/issues/373#issuecomment-1036862331, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXXGHKJJQGQQQE4Z7KYVVLTU2WUQVANCNFSM5OFJSG2Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

ToddLa commented 2 years ago

You should report the issue to mamedev, make sure you repro it on a PC for them, they will ignore you if you send a M4i screenshot.

nickisonlinet commented 2 years ago

Alrighty, I’ll take this to those guys; thank you for the help!!

On Tue, Feb 15, 2022 at 5:14 PM Todd Laney @.***> wrote:

You should report the issue to mamedev, make sure you repro it on a PC for them, they will ignore you if you send a M4i screenshot.

— Reply to this email directly, view it on GitHub https://github.com/yoshisuga/MAME4iOS/issues/373#issuecomment-1040746842, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXXGHKLEAOLDHIBSMB334PDU3KXZJANCNFSM5OFJSG2Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

yoshisuga commented 2 years ago

Hi @nickisonlinet , thanks for taking the time to report the issue and for your kind words!

MAME is a constantly moving large target so there will be issues like these that will crop up from time to time.

We provide a binary for the older 0.139 version and still support it for this reason.

I'll close this issue as they appear to be mostly due to the MAME core itself.

yoshisuga / MAME4iOS

Issues with the new MAME core #373