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
Lightguns Arcade1Up Try the site in https mode Site News

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

  

Author Topic: Controls.dat project question  (Read 787 times)

0 Members and 1 Guest are viewing this topic.

Lilwolf

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 4945
  • Last login:July 31, 2022, 10:26:34 pm
Controls.dat project question
« on: March 27, 2005, 07:31:39 am »
Since I can't test joystick stuff.  The next item on my agenda (was going to be put off until the next version... but I'm pushing it forward) is to add controls.dat support to my frontend.

I was wondering. 

Would it make any sense for others to create a second controls.guess file (or something similar) that would fill in the controls.dat information from both nplayers.ini and mame listxml to fill in all the blank spaces?  nplayers.ini tells the number for physical players per game... Then mame for the number of inputs... just wouldn't have names per button. 

IE... Games that are not exactly known.  It could make a good guess on the rest?

I can personally get the information from many other sources in the frontend.  But in about the same time, I could  probably generate a secondary xml file in the controls.xml format. 

Last question here.  In the source file now, many games have labels to their inputs (look at setting defenders controls... Smart Bomb is mentioned, but not input 3)  Can we get this information anywhere?  Its not in the -listxml

Anyway... just a question