The Ur-Quan Masters Home Page Welcome, Guest. Please login or register.
Did you miss your activation email?
October 06, 2024, 10:06:40 pm
Home Help Search Login Register
News: Celebrating 30 years of Star Control 2 - The Ur-Quan Masters

+  The Ur-Quan Masters Discussion Forum
|-+  The Ur-Quan Masters Re-Release
| |-+  Technical Issues (Moderator: Death 999)
| | |-+  how to fix the keyboard bug
« previous next »
Pages: [1] Print
Author Topic: how to fix the keyboard bug  (Read 2945 times)
maxius
Zebranky food
*
Offline Offline

Posts: 8


All Your Base Are Belong To Us


View Profile
how to fix the keyboard bug
« on: December 17, 2002, 02:24:19 am »

ok i have a logitech elite keyboard and i cant move and fire at the same time help
Logged

i am a *happy* *camper*
ErekLich
*Many bubbles*
***
Offline Offline

Gender: Male
Posts: 247


One Ring to rule them all, eh you know the rest.


View Profile
Re: how to fix the keyboard bug
« Reply #1 on: December 17, 2002, 04:55:11 am »

You're stuck until the next release, if not later.

Keyjamming has always been with us unfortunately.
Logged

Oh God, please don't let me die today!  Tomorrow would be SO much better!
maxius
Zebranky food
*
Offline Offline

Posts: 8


All Your Base Are Belong To Us


View Profile
Re: how to fix the keyboard bug
« Reply #2 on: December 17, 2002, 10:49:37 am »

ok ill make due for now dam kiling ships just got harder
Logged

i am a *happy* *camper*
Robert Dunne
Guest


Email
Re: how to fix the keyboard bug
« Reply #3 on: December 19, 2002, 08:23:03 am »

The funny thing is I can move and fire just fine in Super Melee, but in the normal game it doesn't work. Same with the lander. (This is using the .2 cvs version.) So I don't think its really a keyboard problem, but a game problem. (I tried with three different keyboards on 2 computers, with the same result)

-Rob
Logged
ErekLich
*Many bubbles*
***
Offline Offline

Gender: Male
Posts: 247


One Ring to rule them all, eh you know the rest.


View Profile
Re: how to fix the keyboard bug
« Reply #4 on: December 19, 2002, 09:10:41 am »

Well, the controls are different in SM and the game!

In the game, Space fires and Esc is secondary.

In SM, Shift fires and Ctrl is secondary
Logged

Oh God, please don't let me die today!  Tomorrow would be SO much better!
Black Monk
Guest


Email
Re: how to fix the keyboard bug
« Reply #5 on: December 19, 2002, 08:57:48 pm »

I think this is largely a hardware issue.   I use a Northgate Omnikey/101 as much as possible.

http://firingsquad.gamers.com/guides/keyboards/report.asp

http://www.computingreview.com/Keyboard/Northgate+OmniKey+Ultra+keyboard/PRD_1445_1572crx.aspx

During the keyjammin' fun, it registered ALL the keys that were held down.  At the time, my pals' keyboards could only do about 3 to 5 keys depending on which combinations were used.

Now I'm temporarily stuck on a Dell keyboard.  My fiancee is on a Microsoft ergonomic one.  We lose keystrokes while playing.  Can't turn, move forward, and fire at the same time.  I can only imagine the pain involved if we both tried to play each other on one keyboard.

I had seen this explained as the way the keypress-sensing grid was laid out.  However, I cannot find a diagram of what I'm referring to.  Basically, most keyboards can only read X amount of keypresses from Y regions on the keyboard.  Some key combinations lock out any additional keys that get pressed.

I've been able to directly see this difference by plugging in different keyboards throughout the years and comparing them to my Omnikey.  If this is ONLY a software issue I am at a loss to explain how an old DOS game (all that I've played, actually) can automatically detect a different keyboard--no TSRs running or anything, and somehow accept more simultaneous keyboard inputs.

Heh, it'd be nice if we could get gamepads workin' with SC2, at least in Windows eh.
Logged
Pages: [1] Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!