Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.Login to AccountCreate an Account

Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Set working state for machines with unemulated protection

haynor666

Posted 02 February 2017 - 06:17 PM

haynor666

Member

Members+

58 posts

Gender:Male

Location:Tarnobrzeg, Poland

MAMEUI32 diifers in several ways from Arcade32. One of those changes is how machines with unemulated protection are visible on list. In MAMEUI32 those games are presented as working but in Arcade32 as not working. When in source I can change this behaviour to match MAMEUI32 standard?

haynor666

Posted 11 June 2017 - 09:02 PM

After closer inspect I must say that machines with unemulated protection in many cases should not be treated as not working.

Examples:

Salamander 2 (from mameinfo - "4th May 2003: Acho A. Tang submitted a major improvement to the Konami GX driver, improving the graphics emulation and emulating the ESC protection in Salamander 2, Dragoon Might and Tokimeki Memorial Puzzle-dama, making them all playable.")

Wink (from mameinfo - "0.104u8: Added clone Wink (set 2). Highwayman, Nicola Salmoria and Pierpaolo Prazzoli fixed Wink - Game now playable. Fixed most of the remaining issues in Wink, though there is still some unemulated protection.")

Flaming 7 (from mameinfo - "- 0.176: Reverse-engineer protection to bypass the requested serial number - Games now playable. The iButton device still needs to be hooked. Promoted these games to working with their correspondent flags.")

mamesick

Posted 12 June 2017 - 06:35 AM

mamesick

Member

Members+

61 posts

Again, we (or better, ARCADE) use the same behaviour of MAME core. UNEMULATED_PROTECTION is displayed with a red disclaimer as it happens for NOT_WORKING and MECHANICAL flags. Also, see this portion of code:

// if there's a NOT WORKING, UNEMULATED PROTECTION or GAME MECHANICAL warning, make it stronger
if (m_machine.system().flags & (MACHINE_FATAL_FLAGS))
{
// add the strings for these warnings
if (m_machine.system().flags & MACHINE_UNEMULATED_PROTECTION) {
buf << _("The machine has protection which isn't fully emulated.\n");
}
if (m_machine.system().flags & MACHINE_NOT_WORKING) {
buf << _("\nTHIS MACHINE DOESN'T WORK. The emulation for this machine is not yet complete. "
"There is nothing you can do to fix this problem except wait for the developers to improve the emulation.\n");
}
if (m_machine.system().flags & MACHINE_MECHANICAL) {
buf << _("\nCertain elements of this machine cannot be emulated as it requires actual physical interaction or consists of mechanical devices. "
"It is not possible to fully play this machine.\n");
}

The fact that there are games with UNEMULATED_PROTECTION that in reality "works" it's not our problem, this kind of issue should be reported at MAMEDev. Ninja Emaki, your example, shows a red disclaimer at startup even if it doesn't show the NOT_WORKING message.

So what to do with UNEMULATED_PROTECTION? Working or Not Working? There are tons of cases like the ones you posted.... but as I said, we are aligned with MAME core. RED disclaimer is critical emulation message and we consider it as NOT_WORKING. It should be up to Developers clear and fix this issue.

haynor666

Posted 12 June 2017 - 05:43 PM

haynor666

Member

Members+

58 posts

Gender:Male

Location:Tarnobrzeg, Poland

I wrote message to Tafoid about this. If this will not be resolved I'll open disscussion at mameworld forum. From 267 sets markd as not working and unemulated protection 104 sets are only unemulated protection so quite a lot.