Fix the keymap
*rattles cage*
It's ridiculous at this point that this hasn't been changed, after 12 years of constantly having to tell new players that they have to remap at least their thrusters in order to play the game.
Is this some huge maniacal code change or something? What am I missiing?
It's ridiculous at this point that this hasn't been changed, after 12 years of constantly having to tell new players that they have to remap at least their thrusters in order to play the game.
Is this some huge maniacal code change or something? What am I missiing?
+1!Adept wrote:QUOTE (Adept @ Jan 2 2010, 01:01 PM) The people who are used to WASD in FPS will actually try those controls, and they will immedeately discover sidethrusters.
As it is currently 90% won't discover them until somebody tells about them. This is the key difference. I don't care where they bind the stuff later, but the defaults should be something that help them discover key aspects of Allegiance.
Last edited by Dome on Tue Oct 16, 2012 9:07 pm, edited 1 time in total.
When this was brought up in the past, there was a point where it always got wrapped around the axle when it came to the training missions. Because the training missions reference the default key map in the voice overs, and use some hard coded internal keymap, the conversation died at the points of:
"We should fix the training missions to support a new default key map. "
And then nothing much happened after that point.
AEM probably had the best handle on what needed to be done, and LANS had the sexy voice to go with it. I'm not sure how far they got, if at all.
So, that's what I remember of the history. And I have early stage dementia.
If we were to remap WASD to thrust, and ' to cycle cargo (which I believe defaults on S in the current map), is that all that needs doing? Because if that's it, and the training is only a little wrong, is that good 'nuff?
If so, I can add that to the installer, and put it out on getsetup, and that's it, new default key map.
"We should fix the training missions to support a new default key map. "
And then nothing much happened after that point.
AEM probably had the best handle on what needed to be done, and LANS had the sexy voice to go with it. I'm not sure how far they got, if at all.
So, that's what I remember of the history. And I have early stage dementia.
If we were to remap WASD to thrust, and ' to cycle cargo (which I believe defaults on S in the current map), is that all that needs doing? Because if that's it, and the training is only a little wrong, is that good 'nuff?
If so, I can add that to the installer, and put it out on getsetup, and that's it, new default key map.
Yeah. Just use the one on the wiki.Sheriff Metz wrote:QUOTE (Sheriff Metz @ Oct 16 2012, 03:01 PM) As with any game, it is best that the most actively used commands be accessible around the WASD keys
And deciding which ones should go where will likely need some discussion
WASD only covers 4 thrusters when there are 6, (forward/backward/left/right/straight up/straight down)
plus the roll keys should be accessible, and the zoom keys, and the toggle mouse control key
just by getting all the most important things revolving around WASD, it is an enormous change from the default, and will take up...every key easily accessible by the left hand
and then you have to find places for all the commands you've replaced (targetting keys, deploy key, swap cargo key, etc)
Really the entire keymap needs to be redone all at once
It takes care of all thrusters, rolling, zooming, and mouse control. The most important things are where they ought to be.
As always the inputmap.mdl can be downloaded from the wiki page and/or here
Last edited by Dome on Tue Oct 16, 2012 10:11 pm, edited 1 time in total.