Maybe this is human error; I couldn't find anything on the forums about it.

I tried to assign accelerate and decelerate to extra mouse buttons, but I'm seeing very strage behavior. If I click the "accelerate" button, my ship accelerates to maximum speed and will not decelerate. To regain control, I have to press 'r' (or whatever key is bound to accelerate), then things return to normal. Clicking the "decelerate" button does the same thing except, obviously, in reverse.

Running on Mac OS X 10.3.8. The mouse (trackball, really) is a Macally QBall.

Thanks for any advice.

You want to bind the mouse key to "+Accelerate" instead of "Accelerate".

So, this is something I'm going to need to do manually (i.e., using "binds")? I was trying to use the in-game keyboard assignment. I'll go look up the binds docs, then. Thanks.

Just type /bind LMBUTTON "+Accelerate"

etc

Okay; here's the odd thing. That works. However,

/bind XMBUTTON1 "+Accelerate"

has the effect I originally described. So this seems to be a bug/feature of the extra mouse buttons. And, as long as I'm reporting strange binding effects, trying to

/bind MWHEELUP "+Accelerate"

has no apparent effect whatsoever.

You XMBUTTON1 must not send a signal when it is released. That's most likely a "feature"/bug of the mouse. /bind MWHEELUP "+Accelerate" does do something. The effect is that when your move the mouse wheel up for the split moment that the mouse wheel passes the sensor to say it has moved once your ship will accelerate, and then almost immediately stops. If you were to continue to spin your mouse wheel up very quickly you should be able to see the change in movement.

Eldrad is right about the MWHEELUP bind.
Basically, the game receives a down button and then an up button for the MWHEELUP input. (The same goes for MWHEELDOWN)

You'll have to use other mouse buttons to handle acceleration.

I used the Keyboard menu to successfully bind my XMBUTTON1 to Accelerate and XMBUTTON2 to Decelerate and they both worked properly. I used a Logitech MX510 optical mouse.

Okay; thanks for the information. I guess this mouse is just junk and doesn't send the release on XMBUTTON{1|2}. Might help explain why it was so cheap. :-)

I tried binding my throttle to my wheel as well. However it seemed not to register the action of me rolling the wheel. I know I used the correct bind because I the bound the same command to a different key. Any ideas?

I eventually had to rebind to w and s. I may just move it to r and f and up vertical strafe on w and s. makes things a little easier i think.

if you have xmbutton 1/2, make them primary/secondary fire and use LMBUTTON AND RMBUTTON as your accel/decel. I do that with my regular ordinary 3 button mouse and just use the middle button as fire. It takes a bit of getting used to, but having the accel/decel on the hand that ISNT trying to run the strafes makes distance control SOOOO much easier.

Mousewheel binds are really only useful for togglable things, like switching weapons or opening/closing windows.
Mousewheels send a button down and then up right away, so things that require time will not work properly.