Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news


  

Author Topic: From MAMEdev: Attn frontend developers: machine flags in XML  (Read 462 times)

0 Members and 1 Guest are viewing this topic.

Stiletto

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 21
  • MAME me.
Quote from: Vas Crabb
We're hitting the limitations of the driver element and its attributes in MAME's -listxml output.  To allow for inheritance, better deal with systems with configurable slots, and make handling of machines and devices more uniform, this element is being deemphasised, and some of its attributes are deprecated, to be removed in a future release.

The following attributes of the driver element are deprecated and will be removed in a future release (they will be maintained for at least two releases before being removed): color, sound, graphic, protection.  The other attributes are not scheduled for removal at this point.

A new feature element is being introduced to provide more detailed information on unemulated and imperfectly emulated features.  This element is applicable to both systems and devices, unlike the driver element that is only applicable to systems.  The feature element has three attributes:
  • type - required, indicates the feature of the system/device that has emulation issues; possible values at present: protection, palette, graphics, sound, controls, keyboard, mouse, microphone, camera, disk, printer, lan, wan
  • status - implied, indicates the emulation status of the feature for the device itself; possible values: unemulated, imperfect
  • overall - implied, indicates the emulation status of the feature inherited from subdevices; possible values: unemulated, imperfect

The status attribute only be present if the device itself indicates emulation issues for a feature.  The overall attribute will only be present if more severe emulation issues are indicated by subdevices than by the device itself.  For example
Code: [Select]
<feature type="keyboard" status="imperfect"/> <!-- device indicates that its keyboard emulation is imperfect -->
<feature type="mouse" status="unemulated"/> <!-- device indicates that mouse is unemulated -->
<feature type="graphics" overall="imperfect"/> <!-- at least one subdevice indicates that graphics emulation is imperfect -->
<feature type="palette" overall="unemulated"/> <!-- at least one subdevice indicates that colour palette is unemulated -->
<feature type="sound" status="imperfect" overall="unemulated"/> <!-- device indicates that its sound emulation is imperfect, at least one subdevice indicates that sound is unemulated -->

Right now you can see this with the votrax device.  The aussieby system inherits imperfect sound from its votrax device.  The c64_speakeasy slot card inherits imperfect sound from its votrax device.  If you launch a c64 with a c64_speakeasy card in a compatible slot, MAME will warn about imperfect sound.

If you provide a UI for slot device selection, you may want to provide indication of emulation issues declared by slot devices.

Right now, there is no equivalent for the emulation and savestate attributes for devices (NOT_WORKING and SUPPORTS_SAVE flags).  This will come at some point in the future.

Source: http://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Board=news&Number=368244

Howard_Casto

  • Idiot Police
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 15672
  • Your Post's Soul is MINE!!! .......Again??
    • The Dragon King
Re: From MAMEdev: Attn frontend developers: machine flags in XML
« Reply #1 on: July 27, 2017, 04:19:47 pm »
Yup.  Told you guys the day you switched over that xml sucks and you'd hit a wall.  A switch to ini files or a straight up database format might make more sense now that mame's game/machine list is so gigantic. 

Tafoid

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 173
  • Emulation Devotee
    • MAMELOAD TNG (Front-End)
Re: From MAMEdev: Attn frontend developers: machine flags in XML
« Reply #2 on: July 29, 2017, 05:37:07 pm »
Yup.  Told you guys the day you switched over that xml sucks and you'd hit a wall.  A switch to ini files or a straight up database format might make more sense now that mame's game/machine list is so gigantic.

A little heads up from a project leader to help front-end deals with upcoming changes and the messenger gets it figuratively shoved back in his face in a very "Thanks, but no thanks" way.  Crazy stuff.
Anyway, hopefully those who have a legitimate use for the information will take it to heart.

Haze

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1069
  • I want to build my own arcade controls!
    • MAME Development Blog
Re: From MAMEdev: Attn frontend developers: machine flags in XML
« Reply #3 on: July 29, 2017, 07:00:01 pm »
Yup.  Told you guys the day you switched over that xml sucks and you'd hit a wall.  A switch to ini files or a straight up database format might make more sense now that mame's game/machine list is so gigantic.

Are you smoking crack or something? This has nothing to do with xml sucking, nor is it something that would be easier with 'ini files' 

It's simply about devices getting their own sets of flags because we have a lot of systems where you can configure different devices meaning the global flag is no longer sufficient so people need to consider the status of the device too.  It also allows finer control over where in a system emulation issues are flagged. eg. if we know the emulation of a certain sound chip is buggy / incomplete we can tag it at that level and have the drivers inherit that.

The concept of each game / machine only having it's own set of flags is just something that has been around since the early days of MAME (yes, before XML was used for output) and is now going away in favour of something better (which XML makes nice and convenient to represent in the output as it happens)
« Last Edit: July 29, 2017, 07:04:07 pm by Haze »

Howard_Casto

  • Idiot Police
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 15672
  • Your Post's Soul is MINE!!! .......Again??
    • The Dragon King
Re: From MAMEdev: Attn frontend developers: machine flags in XML
« Reply #4 on: July 29, 2017, 10:17:29 pm »
I get it now.  Instead of a singular set of status flags for a game you can now do it at the component level, potentially allowing for even more bloat in an already bloated xml file and inaccuracies due to the fact that individual games won't necessarily be checked anymore.  That isn't worse or anything.  I do appreciate the heads up, don't get me wrong, but have you guys looked at the full xml lately?  Takes forever to parse it's so big. 

Haze

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1069
  • I want to build my own arcade controls!
    • MAME Development Blog
Re: From MAMEdev: Attn frontend developers: machine flags in XML
« Reply #5 on: July 30, 2017, 06:19:47 am »
I'd say we had different ideas of forever, or maybe your parser sucks.

If you were to attempt to brute-force a CPS2 key without the key-cracker that would take forever, literally, we're talking longer than the universe has been around so reducing that to a couple of days / hours depending on the situation was worthwhile.

If you're talking about taking a couple of seconds to parse an XML file that you can then cache the bits you care about if you so please, no, that isn't forever.

  
 

Sitemap 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31