Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: Ctrlr INI Setup  (Read 1237 times)

0 Members and 1 Guest are viewing this topic.

Minwah

  • Trade Count: (+3)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 7662
  • Last login:January 18, 2019, 05:03:20 am
    • MAMEWAH
Ctrlr INI Setup
« on: July 04, 2003, 06:56:59 am »
Does anyone know how to refer to an analog sticks 'slider' (3rd Axis) in the ctrlr ini files?

The MAME UI refers to it as 'J1 Slider +/-', but I am unsure how to do this in the ini file.

This is in the ctrlr docs:

With respect to the windows port, the generated keycodes are identical to those displayed in the configuration menu with all spaces replaced by underscores.  For example, the keycodes automatically generated for a Wingman Warrior joystick are:

J1_X-axis_+        J1_X-axis_-        J1_Y-axis_+        J1_Y-axis_-
J1_Z-axis_+        J1_Z-axis_-        J1_Rz-axis_+       J1_Rz-axis_-
J1_Button_0        J1_Button_1        J1_Button_2        J1_Button_3
J1_POV_0_U         J1_POV_0_D         J1_POV_0_L         J1_POV_0_R

The names generated will vary with the port to which the joystick is connected.  In the codes listed above, the Wingman Warrior was connected as the first joystick (J1).  If it had been configured as a different input, the generated codes would have a different Jx number.

All keyword matching including the standard keywords is case sensitive.  Also, some of the automatically generated OSD codes may be redundant.  For example, J1_Button_0 is the same as JOYCODE_1_BUTTON1.  Standard codes are preferred over OSD codes.


...so with that in mind, I suppose 'J1_Slider_+' and 'J1_Slider_-' should work, but it does say 'Standard codes are preferred over OSD codes', what are the standard codes in this case?

Thanks for any help

u_rebelscum

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 3633
  • Last login:April 21, 2010, 03:06:26 pm
  • You rebel scum
    • Mame:Analog+
Re:Ctrlr INI Setup
« Reply #1 on: July 04, 2003, 08:33:33 am »
Does anyone know how to refer to an analog sticks 'slider' (3rd Axis) in the ctrlr ini files?

The MAME UI refers to it as 'J1 Slider +/-', but I am unsure how to do this in the ini file.

....

...so with that in mind, I suppose 'J1_Slider_+' and 'J1_Slider_-' should work, but it does say 'Standard codes are preferred over OSD codes', what are the standard codes in this case?

Thanks for any help

There is no standard code for a third axis.  You will need to use the 'J1_Slider_+' and 'J1_Slider_-' terms.  Much like if you want to use buttons greater than #6, you need to use the OSD codes. *shrug* :-\



(For programmers only) FWIW, your slider is probably the "7th" axis, as the directX directInput standard offset numbering is:
1: X axis
2: Y axis
3: Z axis
4: rX axis
5: rY axis
6: rZ axis
7: slider 1
8: slider 2
However, it is up to the driver to follow this standard or not.  Also the old dX standard it was okay for a slider to be axis with offset # 3 if there was no regular Z axis.  This is all hidden from the users, however, as even the current way, if there is on Z through rZ axes, the slider is seen as the third usable axis.  The programmers need to know this, but not the users.
Robin
Knowledge is Power

Minwah

  • Trade Count: (+3)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 7662
  • Last login:January 18, 2019, 05:03:20 am
    • MAMEWAH
Re:Ctrlr INI Setup
« Reply #2 on: July 04, 2003, 10:31:03 am »
OK Thats great, thanks URebel :)