Software Support > controls.dat
controls.xml outdated
arzoo:
--- Quote from: Space Fractal on September 07, 2008, 05:32:01 am ---headkaze: does any fe actuelly use colors.ini? If Yes you need to still have a seperated version to fit these fe.... But a joined version would been very fine.
--- End quote ---
I believe that only headkaze's apps and LEDBlinky use colors.ini. I'm more than happy to mod LEDBlinky to use a single source for controls and colors! :)
SirPoonga:
--- Quote from: headkaze on September 07, 2008, 02:14:50 am ---SirPoonga: I thought the website was closed down because of lack of public support ??? I didn't realise it was only down temporarily. I was looking at taking over the project with an offline version maintained using the new software I'm writing. Seeing how it's been so long since the last update perhaps we should try this approach? I'm also adding in colors.ini to the file so that will mean it will conflict with the online version. People are only going to want to support the one format.
So I feel like I'm stuck here not knowing what to do. I was pretty much thinking it was going to have to go this way to keep the project going. So what now? How much data is there that has been added to the website ready to be added to a new version? If there is nothing then I'll just take the current version and start from there. Are you happy for me to continue on with this SirPoonga? I was hoping u_rebelscum was going to have a go at doing a large update using the software or do you want to try out my program yourself?
--- End quote ---
First, I don't know why the website is down. I was logged in a couple weeks ago.
Second, how does colors.ini conflict with it. Isn't it a seperate file?
Like I said, I can add someone as an admin to controls.dat if they want to review submissions. It's actually quite easy. I do two things, I check the resource to see if it is valid and I can read the labels on the control panel. Then I check mame to make sure all of the controls mame says is listed. Make changes if needed and accept it.
Since the site is down I can't answer many questions because I haven't looked at the code an database in sometime.
I could add a verified checkbox when accepting a submission which will then add a verified attribute.
I could add in some code to import data. I could take the output of your program and add new entries, just flag them as not verified.
--- Quote from: Space Fractal on September 07, 2008, 05:32:01 am ---Only Mario Bros is they Play Choice game use one button, all other use 2 buttons (based on games that is on klov.com). Just look on the help screen, what the buttons does. These games is based on NES hardware which have 2 buttons.
--- End quote ---
You missed my point. I believe the UseService in controls.dat indicated games that use the service buttons. These are the buttons that allow you to switch games. See the lixtxml output from the game, service is yes
<input players="2" buttons="2" coins="2" service="yes">
<control type="joy8way"/>
</input>
If I remember correctly that is what this is for. But they don;t list how many service buttons and what they are for. I think we had to look at the mame source code to figure that out. I don;t have a controls.xml right now. What is the playch10 entry?
There are games people have complained to me about that they only have one button. What the manufacture did was put a button on the right and left of the joystick and wired them as separate buttons. So technically the game has two buttons that do the same thing.
My point of that post is you have to realize controls.dat may not be as out of date as some people think. Yeah, asteroids finally is proper and only lists buttons. That will need updating. But some things people complain about are not inaccurate.
Space Fractal:
I just looked in the file controls.ini:
1. The service buttons is listed in the controls.ini (which I use) as separate buttons (as SERVICEx= entry), but is not counted as a in-game button. But since you can't switch a game in Mame (which only emulate one game inserted as I known), they are not really useable anyway. So I think its pretty correct. I do see all games should got listed, so they got better label?
2. I see also many entry listed number of buttons used in the PCB and NOT the game its self? I think that wrong, I see mirrored buttons should not count (as these games would been playable with a one joystick + one button panels). Examples is:
- Galaga '88 (the file contain PCB have 3 inputs and the control panel used a 8 way joystick, but the game itself really only use a 2-way Joystick with one button).
- Beels & Whistles (both buttons does the same = no need to list as a 2 button game).
- Air Buster (both buttons does the same = no need to list as a 2 button game).
So its still have been some inaccurate and should been corrected....
To the last the Headkaze utility is a good one to check all entries in a great user interface. I think clones could been marked as "use parent", if the controls is the same?
TheShanMan:
--- Quote from: SirPoonga on September 07, 2008, 12:29:39 pm ---My point of that post is you have to realize controls.dat may not be as out of date as some people think. Yeah, asteroids finally is proper and only lists buttons. That will need updating. But some things people complain about are not inaccurate.
--- End quote ---
If you're including my comments about inaccuracy there, what I have noticed is the miscellaneous field sometimes has outdated information. I don't recall off the top of my head what the examples are, but if you want to know so it can be corrected, I could try to find those.
headkaze:
SigPoonga: Okay if your still going to be running the project, then I think I should make sure my app will work alongside the online project. So say someone uses my software and adds a whole bunch of entries, will you merge that Controls.xml into yours or do you want me to add the ability to import/merge an external Controls.xml? I think you will find my software very helpful, so I think I will add importing anyway. Also I propose we combine colors.ini and add a "Status" tags. I say the Status can be Verified="1" or Verified="0". I can also add the ability to work with that as well.
If a label doesn't have a color entry I think the tag should not be in the xml.
So here is an entry, note the added "Status" tag and "Color" attribute for labels:
--- Code: ---<Game RomName="1942" GameName="1942 (set 1)" NumPlayers="2" Alternating="1" Mirrored="1" UsesService="0" Tilt="0" Cocktail="1">
<Status Verified="1" />
<MiscDetails />
<Player Number="1" NumButtons="2">
<Controls>
<Control Name="8-way Joystick">
<Constant Name="joy8way" />
</Control>
</Controls>
<Labels>
<Label Name="P1_BUTTON1" Value="Fire" Color="Red" />
<Label Name="P1_BUTTON2" Value="Loop" Color="White" />
<Label Name="P1_JOYSTICK_UP" Value="Up" Color="Red" />
<Label Name="P1_JOYSTICK_DOWN" Value="Down" Color="Red" />
<Label Name="P1_JOYSTICK_LEFT" Value="Left" Color="Red" />
<Label Name="P1_JOYSTICK_RIGHT" Value="Right" Color="Red" />
</Labels>
</Player>
</Game>
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version