Software Support > controls.dat
controls.xml outdated
headkaze:
--- Quote from: NOP on September 04, 2008, 09:49:26 am ---We really need a web geek. Anyone?
--- End quote ---
I think it would be relatively easy to write an app to do this. In fact for a while I have been thinking of writing an app similar to ColorsIni which helped me automate the process of entering color data for games. I see a few benefits for writing an app to help with this, as it could use the default control info generated from Mame. It could have all the controls in comboboxes to choose from and it could also show the CP image while you scroll through games to help identify the labels for the game, also you could have the ability to launch Mame to actually test the controls as well as copying & pasting controls from game to game. Since Controls.Dat is designed to only have parent ROMs a program could also filter out the clones.
The reason why I think a local app would be better is from my experience you will have more chance finding one person who will be dedicated enough to go through and update the data accurately and reliably (and someone who knows Mame controls well of course). The time and effort involved in managing a website to accept entries from anyone in my opinion will not work very well (and infact is what SirPoonga has said already). And it's not because it's a hard thing to do, writing a html form that will post data somewhere is easy to do, it's finding people to enter the data that's the hard part. When I wrote ColorsIni noone wanted to help at the time so I spent about 4 hours straight (destroying a mouse in the process) and got it done myself. So I think the best way to get this done is to write a program to automate the process and I think ColorsIni would be a good start.
If we can find a dedicated person willing to do it then it might be worth writing the app to help do it.
u_rebelscum:
Like the idea of the app.
--- Quote from: headkaze on September 04, 2008, 10:11:53 am ---...Since Controls.Dat is designed to only have parent ROMs...
--- End quote ---
IIRC, controls.dat assumed that clones had the same inputs as parents, but was able to do clones that had different inputs than parents. A couple examples with clone different than parent: cabal (TB vs bootleg joystick & extra button), harddrivin (analog shifter vs "compact" cab's digital shifter).
edit: looks like clones w/ different inputs was in the todo list?
--- Quote ---...If we can find a dedicated person willing to do it then it might be worth writing the app to help do it.
--- End quote ---
Dedicated and IMO "truth" oriented. I like control.dat's "must be verified" rule. Some people less "truth" oriented wanted to fill in unverified button names with generic ones. While I don't mind place holders like that, place holders often get used as if they are real data.
I'm very interested, but I doubt I'm dedicated enough to keep it going for the required years. :-\
SirPoonga:
--- Quote from: TheShanMan on September 03, 2008, 06:39:44 pm ---I submitted spy hunter like a month ago and the submission still shows as pending.
--- End quote ---
I see it. However, you have no proof.
One goal of controls.dat is to have accurate information so we require documentation. A picture of the control panel, the manual, something.
Anyone can update the entries. It just needs to be reviewed for accuracy.
HowardC and I have not left the scene or abandoned the project. It's more like community left the project. Since people haven't been submitting data it hasn't been worth the effort to maintain.
I also haven't had the time lately. My weekends have been busy for the last two months.
--- Quote ---edit: looks like clones w/ different inputs was in the todo list?
--- End quote ---
Yeah, again, with a sudden drop off of community help I haven't had the motivation to add new features. Controls.dat is designed to support the entire mame rom set. It's the website that doesn't support clones right now.
If someone wants host it and take over talk to me. The data is stored in a mysql database. I could easily export the data and send it along. Now, finding the source for the site will take a bit, though I could always login and ftp it back.
Though I have been thinking about using the site to learn Silverlight with. I think a slick Silverlihgt interface would be cool.
TheShanMan:
Not exactly sure what you need, since control panel pictures are readily available. I think a good definition of "proof" needs to be available there. Here's one cp pic: http://www.mameworld.net/maws/img/cpanel/spyhunt.png. Is that enough?
SirPoonga:
--- Quote from: TheShanMan on September 04, 2008, 03:47:56 pm ---Not exactly sure what you need, since control panel pictures are readily available. I think a good definition of "proof" needs to be available there. Here's one cp pic: http://www.mameworld.net/maws/img/cpanel/spyhunt.png. Is that enough?
--- End quote ---
The FAQ should explain the submitting process. Unfortunately the site is down now...
Proof is anything that is readable (control panel pic, manual) that tells you what the button should be labeled as or it's action. For example, the thumb buttons on the spy hunter yoke do not have labels. We still need to know what it does. Now, it is a popular game, you might say duh it's the fire button. The problem, we found, is what people think is common knowledge about what a button does in a game is not necessarily the correct label. The goal of controls.dat is to be as accurate as it can be so you can label the controls mame says the game has.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version