Tremulous Forum

General => Feedback => Topic started by: /dev/humancontroller on July 13, 2007, 06:10:36 pm

Title: implementing Sprint as a +buttonX
Post by: /dev/humancontroller on July 13, 2007, 06:10:36 pm
Instead of having a "boost" command, how about using +button9 for example? Then you could keep it pressed while changing directions. This could improve the human dodging skills, a lot for n00bz, and a bit for uBeR1337Zorz.
Title: implementing Sprint as a +buttonX
Post by: Odin on July 13, 2007, 07:02:37 pm
Seriously. I'm tired of repeatedly hitting the sprint key when I change directions.
Title: implementing Sprint as a +buttonX
Post by: Bajsefar on July 13, 2007, 08:56:57 pm
No. Most keyboards (or drivers, i dunno) will only allow you to press 3 buttons or so at a time before things get fucked up.
But you could atleast make the sprint a real toggle, optionized of course so the people who think it is perfect the way it is (like me) can choose the 'old' way.
Title: Re: implementing Sprint as a +buttonX
Post by: kevlarman on July 13, 2007, 08:59:33 pm
Quote from: "/dev/humancontroller"
Instead of having a "boost" command, how about using +button9 for example? Then you could keep it pressed while changing directions. This could improve the human dodging skills, a lot for n00bz, and a bit for uBeR1337Zorz.
calling it +button9 is braindead, there is no reason to change the name (other than to add a +).
Title: Re: implementing Sprint as a +buttonX
Post by: TinMan on July 13, 2007, 09:05:02 pm
Quote from: "kevlarman"
Quote from: "/dev/humancontroller"
Instead of having a "boost" command, how about using +button9 for example? Then you could keep it pressed while changing directions. This could improve the human dodging skills, a lot for n00bz, and a bit for uBeR1337Zorz.
calling it +button9 is braindead, there is no reason to change the name (other than to add a +).

why did they make taunt a button then? lol
Title: Re: implementing Sprint as a +buttonX
Post by: kevlarman on July 13, 2007, 09:06:15 pm
Quote from: "TinMan"
Quote from: "kevlarman"
Quote from: "/dev/humancontroller"
Instead of having a "boost" command, how about using +button9 for example? Then you could keep it pressed while changing directions. This could improve the human dodging skills, a lot for n00bz, and a bit for uBeR1337Zorz.
calling it +button9 is braindead, there is no reason to change the name (other than to add a +).

why did they make taunt a button then? lol
no clue, maybe it's an artifact from pre-standalone.
Title: implementing Sprint as a +buttonX
Post by: /dev/humancontroller on July 13, 2007, 09:27:00 pm
Quote from: "Bajsefar"
No. Most keyboards (or drivers, i dunno) will only allow you to press 3 buttons or so at a time before things get fucked up.
But you could atleast make the sprint a real toggle, optionized of course so the people who think it is perfect the way it is (like me) can choose the 'old' way.
If an another key will not be possible, it doesn't matter wether u have +boost or boost. If you can't press the sprinting button, then that's it.
But you shouldn't have problems like that, because the shift, ctrl and alt are keys that are made for simultaneous pressing.
Title: Re: implementing Sprint as a +buttonX
Post by: /dev/humancontroller on July 13, 2007, 09:32:06 pm
Quote from: "kevlarman"
Quote from: "TinMan"
Quote from: "kevlarman"
calling it +button9 is braindead, there is no reason to change the name (other than to add a +).

why did they make taunt a button then? lol
no clue, maybe it's an artifact from pre-standalone.

No, they easily could have made it be called +taunt.
So they might have missed the opportunity to change.
Tip: +attack is an alias for +button0
Title: implementing Sprint as a +buttonX
Post by: Somethief on July 13, 2007, 09:41:58 pm
Quote from: "Bajsefar"
No. Most keyboards (or drivers, i dunno) will only allow you to press 3 buttons or so at a time before things get fucked up.
But you could atleast make the sprint a real toggle, optionized of course so the people who think it is perfect the way it is (like me) can choose the 'old' way.


Mine works with all buttons down that i can press, logitech + linux :)
Title: implementing Sprint as a +buttonX
Post by: TinMan on July 13, 2007, 09:58:42 pm
Mine's the same, some cheapo ergonomics ps/2 keyboard and a Logitech MX Revolution mouse in Linux.
Title: implementing Sprint as a +buttonX
Post by: Lakitu7 on July 13, 2007, 10:59:25 pm
Keyboard simultaneous keypress limitations are hardware, guys. The almighty power of your infallible operating system has nothing to do with how the keyboard you plugged into it is built.
Title: implementing Sprint as a +buttonX
Post by: TinMan on July 14, 2007, 12:24:54 am
Then my cheap ps/2 ergonomics keyboard rocks, I tried playing Frets of Fury on a Dell once and the keyboard locked up at 3 keys and I was all "WTF SHITTY DELL LAWL!"
Title: implementing Sprint as a +buttonX
Post by: Caveman on July 14, 2007, 12:50:54 am
Quote from: "Bajsefar"
... Most keyboards (or drivers, i dunno) will only allow you to press 3 buttons or so at a time before things get fucked up. ...


You do not know many keyboards or you just buy crappy gamer-gear or cheapos.
E.g. the old IBM (original AT) does not fuck up, nor do Cherry-Golds.
Title: implementing Sprint as a +buttonX
Post by: Somethief on July 14, 2007, 05:48:33 pm
Quote from: "Lakitu7"
Keyboard simultaneous keypress limitations are hardware, guys. The almighty power of your infallible operating system has nothing to do with how the keyboard you plugged into it is built.


True, but most of logitech keyboards seem to not have any kind of limitations (Well the cheap ones are cheap ones..) under linux.
But as you well know keyboard can't controll the beeper of computer, it's your windoze limiting the amount of buttons you can press down at once.
Title: implementing Sprint as a +buttonX
Post by: kevlarman on July 14, 2007, 07:12:08 pm
Quote from: "Lakitu7"
Keyboard simultaneous keypress limitations are hardware, guys. The almighty power of your infallible operating system has nothing to do with how the keyboard you plugged into it is built.
actually that's not entirely true. if you're getting input from your wndproc() events, then you can only have 3 keys down at any time (modifier keys excluded), however if you call GetAsyncKeyState(), there seems to be no limit. i can't comment on how directinput will work, which is what trem uses on windows iirc.
Title: implementing Sprint as a +buttonX
Post by: 4RT1LL3RY on July 24, 2007, 06:19:57 pm
Most standard keyboards suffer from phantom keystrokes, where if you press several keys at the same time, then if you try to press another key it won't work.  My old keyboard from dell was like that with wasd and my arrow keys.  Its was annoying, but now I have my Merc Zboard, and you don't get Phantom Keys unless you press more then 15 keys at once.  I need to find a driver or something that will work for Ubuntu, I love the gamepad part of my keyboard but can't get it set up for linux.