Software Support > controls.dat
controls.xml outdated
TheShanMan:
Glad I'm not the only one defending the need for more informative labels! I would be fine with the action attribute approach or just a perpetually unverified status (though the former would have the advantage of allowing a game like super mario bros to retain the verified status while still having helpful labels). I don't care too much as long as there is a practical way to accomplish the goal of useful labels.
Space Fractal:
if controls.xml is just capture most of the info from mame, that isn't really useable of this file.
I thought this file was for a better label for the games than these MAME use and also correct the joystick actually used in the game (which in some games example incorrectly show as 8way joystick, but a 2way joystick can been used, and then incorrectly got filtered out).
I also agree Fakelabel is a good idea, but I prefer name it Action instead, which is what they really are. Of course this should only been needed of these games that need that. I also doesn't like just labeled A and B in Super Mario when CPViewer or such application is used. '
I want REAL informative names too and corrected joystick type used, and corrected number of buttons in a actuel game (example Super Mario only use one button).
This would also been very good when LCD are used, because you can't really use MiscDetails at all.
So in the long, I agree with the action label idea and would not hurt any compatible at all.
u_rebelscum:
--- Quote from: SirPoonga on September 23, 2008, 11:04:01 am ---I could see there being a label and an action attribute. For most games they will be the same. The entry form could automatically fill in action with the label when it is typed in. Context sensitive buttons might be interesting.
--- End quote ---
I like the Action attribute far better than my first go. Better name and connotation, separates user game actions from labels, gets a way to verify that a game had no labels into the DB, addresses the complaint of poor labels while avoiding the need to watch through 2 minutes of the game to find out what the button labeled "A" does in the game, and leaves the real label alone. Also, this would make a way, for example, for 2-3 button neogeo games to show that button 4 is not used in that game, even though it has a label.
As you said, context sensitive buttons might be interesting. Make it an optional multi-element? (Cons: harder to parse, more complicated, for only a small percentage of all the games, what about multibutton actions?; Pros: covers multi-action and content specific actions)
<Labels>
<Label Name="P1_BUTTON1" Value="Action">
<Action Name="Swing" />
<Action Name="Pitch" />
</Label>
<Label Name="P1_BUTTON2" Value="B" />
<Label Name="P1_BUTTON3" Value="C">
<Action Name="Unknown" />
</Label>
<Label Name="P1_BUTTON3" Value="D">
<Action Name="Unused" />
</Label>
</Labels>
vs
... <Label Name="P1_BUTTON1" Value="Action" Action="Swing/Pitch" />...
Probably overkill, but hey, tossing it out there.
I know the misc already might contain the info, but from a database point of view, comment fields are not the best way to store data that can be standardized. Hard to query, no way to sort, hard to parse, hard to selectively display, and in the 1943kai case, have to humanly apply button specific info to the correct buttons. By standardizing with the action attribute, the info is easier to use and is thus more helpful.
TheShanMan:
--- Quote from: Space Fractal on September 23, 2008, 02:39:47 pm ---(example Super Mario only use one button)
--- End quote ---
Wrong. It uses 2. And it took me a while to discover that also! That is partly why I've come to feel so strongly about this issue. For probably the first 2 dozen times I played the game, I thought only 1 button did anything, but that's only because the other button only does something in special circumstances (e.g. shoot a fireball when you get that flower or whatever it is that seemingly does nothing but give you 1000 pts). If controls.xml provided useful information, then I would have known all along that it isn't a dead button.
Kind of the same story with excitebike - I knew I wasn't playing it properly because I would overheat all the time, so I kind of gave up on the game for a while. Then I researched the game a bit and discovered that the other button lets you accelerate slower, without overheating. The 2 buttons are "turbo" and "accelerate". If only those labels were present on my CPWizard image from the start!
Again, glad to have a lot of people basically reinforcing what I'm calling for! Maybe all this response will cause Howard to reconsider his position. ;D
Space Fractal:
It juts what it cleared stated on the top screen for that game as B button was not used.... that all.
multi-element would clearly break compatible with older viewers and frontends that use it, but is not updated anymore. So that is not good, since you NEED allways have it backwards compatible.
Instead you could do something a much simple alternative:
--- Code: --- <Labels>
<Label Name="P1_BUTTON1" Value="A" Action="Swing, Pitch" />
</Labels>
--- End code ---
unknown labels is not needed if not used. otherwise it just waste a space. Older frontends would use Value and newer use the Action label if found (and might take aware of the comma, but not required).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version