You are not logged in.

#1 2007-07-17 01:13:22

mrbug
Member
Registered: 2007-07-17
Posts: 221

n64 controller + boom converter problem

Before I came to this great distribution, my Boom n64/psx to USB converter worked perfectly, but now I can't get it to work correctly.

For some reason, it insists that I have 4 axes. While this is how the converter is detected on all operating systems, it does not allow me to calibrate it successfully anymore. Left and right work, but up and down are ...shaky at best. I can usually move down, but up doesn't do anything.

I think that I could maybe fix this by specifying the type when I load the analog module, but joystick.txt isn't very detailed in the one spot that I need it to be.

  For other joystick types (more/less axes, hats, and buttons) support
you'll need to specify the types either on the kernel command line or on the
module command line, when inserting analog.o into the kernel. The
parameters are:

    js=type,type,type,....

  'type' is type of the joystick from the table below, defining joysticks
present on gameports in the system, starting with gameport0, second 'type'
entry defining joystick on gameport1 and so on.

    Type     | Meaning
    -----------------------------------
    none     | No analog joystick on that port
    auto     | Autodetect joystick
    2btn     | 2-button n-axis joystick
    y-joy    | Two 2-button 2-axis joysticks on an Y-cable
    y-pad    | Two 2-button 2-axis gamepads on an Y-cable
    fcs      | Thrustmaster FCS compatible joystick
    chf      | Joystick with a CH Flightstick compatible hat
    fullchf  | CH Flightstick compatible with two hats and 6 buttons
    gamepad  | 4/6-button n-axis gamepad
    gamepad8 | 8-button 2-axis gamepad

  In case your joystick doesn't fit in any of the above categories, you can
specify the type as a number by combining the bits in the table below. This
is not recommended unless you really know what are you doing. It's not
dangerous, but not simple either.

    Bit | Meaning
    --------------------------
     0  | Axis X1
     1  | Axis Y1
     2  | Axis X2
     3  | Axis Y2
     4  | Button A
     5  | Button B
     6  | Button C
     7  | Button D
     8  | CHF Buttons X and Y
     9  | CHF Hat 1
    10  | CHF Hat 2
    11  | FCS Hat
    12  | Pad Button X
    13  | Pad Button Y
    14  | Pad Button U
    15  | Pad Button V
    16  | Saitek F1-F4 Buttons
    17  | Saitek Digital Mode
    19  | GamePad
    20  | Joy2 Axis X1
    21  | Joy2 Axis Y1
    22  | Joy2 Axis X2
    23  | Joy2 Axis Y2
    24  | Joy2 Button A
    25  | Joy2 Button B
    26  | Joy2 Button C
    27  | Joy2 Button D
    31  | Joy2 GamePad

I just need to be able to tell the module that I have two axes and fourteen buttons. Does anyone know how to do this or how to get the thing to work?

It's especially frustrating because it did work in my last distribution, but now I can't get it to work very well at all.


dvdtube - download all uploads from a YouTube user and then optionally create a DVD.
(Regular version AUR link / SVN version AUR link)

Offline

#2 2007-07-17 02:07:59

mrbug
Member
Registered: 2007-07-17
Posts: 221

Re: n64 controller + boom converter problem

Well, it looks like the controller was to blame. I tried another one and it worked perfectly. Odd.....


dvdtube - download all uploads from a YouTube user and then optionally create a DVD.
(Regular version AUR link / SVN version AUR link)

Offline

Board footer

Powered by FluxBB