Software Support > controls.dat

Change discussion

<< < (2/2)

SirPoonga:
Interesting.  But do we need to worry about it?  What's the goal of controls.dat?  To create a description of the physical control panel and map it to the mame inputs.  However, should we worry about FAKE_X inputs that are hacks?  The game is a dial game.  Why should controls.dat also link to joystick or spinner?

In a controls viewer if all you have a joystick and 6 buttons on your control panel what you do is overlab the dial, spinner, and joystick labels.

Howard_Casto:
Well that's the thing.... if we are going by the book we would only list the real 720 spinner, which is an akward  2 dial system that makes the game completely unplayable. I also tried the method of just putting all the controls in the entry..... look at the hot mess that is the current 720 entry and you'll see what I mean. 

The thing about mapping the inputs is the killer.  See we can't map the inputs unless with deal with the flags at least because, like I said... two dials in 720's config with two different mapping ports, but they are both player 1 dial. 

I think we are going to eventually have to deal with it anyway.  There are drivers in mame besides this that already have a driver configuration setting, but they are incomplete drivers we don't have to worry about yet.  The option is intended to switch on/off inputs for those games that allowed multiple control types to be hooked up (trackball or joystick... ect). 

SirPoonga:

--- Quote from: Howard_Casto on March 31, 2011, 05:00:38 pm ---Well that's the thing.... if we are going by the book we would only list the real 720 spinner, which is an akward  2 dial system that makes the game completely unplayable. I also tried the method of just putting all the controls in the entry..... look at the hot mess that is the current 720 entry and you'll see what I mean. 

--- End quote ---
Oh right, 720 has the regular encoder disc and the one with a single notch to calibrate it.  I don't see the issue with only mapping 720 to P1_DIAL and P1_DIAL_V.  Both have labels associated with them.  In a control viewer you may not put the P1_DIAL_V labels in.  In this case the labels are going to be blank anyways - other cases they may not, but...

There will be an issue for someone that has a control panel witha  joystick and spinner on it.  The convtrol viewer will probably put the labels on the spinner though the person may actually just use the joystick instead.

I wish the mame cfg file was organizes to the aliases are under the input they simulate. 

For controls.dat we could ass an aliases node that maps out the aliased controls.  It would be up to the control viewer and user to add that they want to show the joystick alias instead of the dial.

Navigation

[0] Message Index

[*] Previous page