| Main > Main Forum |
| Buddabing's LED controller |
| << < (62/69) > >> |
| SirPoonga:
--- Quote from: Chris on June 15, 2005, 04:54:15 pm --- --- Quote from: gl.tter on June 15, 2005, 04:45:28 pm ---It also doesn't make sense to add the light layout to controls.dat, because different light drivers will offer different lighting related options that can't all be accomodated in a generic layout format. --- End quote --- The only thing I thought should have been in controls.dat was the original colors of the buttons, so someone using three LEDs could use the lighting board with clear buttons to reproduce the original button colors. Thus, when a NeoGeo game says to press the red button for a particular action, or when NBA Maximum Hangtime says that the Turbo button is white, you can actually use the correct colored button on the panel. --Chris --- End quote --- Budda brought this up. I don't think it is a good idea for controls.dat. A very small percentage of the games had specific colors. The majority of the games in mame are kits or conversions. It would be a good idea as a side project. It will also be hard to verify if the colors for a particular game are correct. You can't tell from a pic because it might be a conversion or buttons might have been swapped. |
| gl.tter:
--- Quote from: SirPoonga on June 15, 2005, 04:57:01 pm ---Various reason. --- End quote --- |
| SirPoonga:
--- Quote from: gl.tter on June 15, 2005, 05:06:38 pm --- --- Quote from: SirPoonga on June 15, 2005, 04:57:01 pm ---Various reason. In case of dotron the trackball is an up/down spinner hack. In case of game where mame says 4 buttons but it used 2 is because the driver dev used a generic macro to map the buttons for all games in the driver. There are various other reasons. --- End quote --- I'll have to check out dotron, but again, even if MAME thinks it's a track, I send signals about whatever hardware you've mapped to it, so the correct hardware lights. ie. I send hardware codes, not input ports. --- End quote --- But dial AND joy8way are defined IN mame which is the controls you use and map. So with what you are saying it would light a trackball that it should be unless the person plans on using the track ball as the up/down spinner hack. I don't use a trackball for dotron, but it is still defined since it is a hack. It would still get lighted up then? you have to remember hacks are hacks, not the normal way it should work. Also, what if a person has both a spinner and a 360 steering wheel. Will both light up for all dial games? --- Quote --- --- Quote ---right, because controls.dat doesn;t need to store that info, it's all readily available. Hence you need something like the Johhny 5 viewer which combines controls.dat and your ctrlr files to accuratly display the labels and control per your configuration --- End quote --- Not familiar with it, link? --- End quote --- http://fe.donkeyfly.com/forum/index.php?topic=119.new#new --- Quote --- --- Quote ---why would animated lights be part of controls.dat? --- End quote --- The point was that you have to associate lights with mapped hardware inputs - what the original controllers were doesn't really matter (except for eliminating false buttons) AFAIKS. --- Quote ---Why does it have to happen in mame? why can't it happen in an FE that supports controls.dat (and compares controls.dat with one's ctrlr files to get the correct key mappings). Or if the supprt was in the Johhny5 viewer (and use an FE like Mamewah that cna use the viewer). --- End quote --- Because the lighting changes interactively as the game is running, so I have to scan activated input codes and send signals on-the-fly. --- End quote --- Only for the lights that get turned on and off within the game. But to light what controls the game uses you don't need to do that. The event signals should still be in mame, however as a user I would trust controls.dat first, but if the game isn't in controls somehow use what mame says instead. But mame is highly inaccurate. |
| SirPoonga:
it's been awhile since I used buddamame, did he put support for controls.dat in there or just support to show a viewer and the viewer displays the info? If he has support for controls.dat directly in mame then that would be the best version of mame to use for lighting what controls a games uses. He'd have to generate whatever signals LSE needs based on controls.dat when the game gets loaded. |
| SirPoonga:
--- Quote from: gl.tter on June 15, 2005, 05:06:38 pm ---The point was that you have to associate lights with mapped hardware inputs - what the original controllers were doesn't really matter (except for eliminating false buttons) AFAIKS. --- End quote --- I forgot, that's what the FEDEv package is for. http://fe.donkeyfly.com/controls/controls_dat.php combine the two files in there to get the mame constants the control uses. This is how Johhny5 works with ctrlr files. Before the xml ctrlr files Johhny5 would look up the control info in controls.dat. Then use those table to look up the mame constants. Then goto the appropiate ctrlr file and see how you have those controls mapped. Then display the correctly labelled controls. |
| Navigation |
| Message Index |
| Next page |
| Previous page |