Thursday, February 24, 2011

Button Mapping

After thinking about buttons layout while holding some of the guns we have in the loft, here's my shot at it:


Justifications:
1. Shooting = Trigger - for obvious reasons
2. Aiming = Gun Pointer - placeholder
3. Move = thumbstick - default placeholder (fluid and intuitive)
4. Crouch/Prone = thumbstick press - its on the same button as move since its related to moving; hard to explain my other justifications on paper, but I can describe my reasonings in another median
5. Jump = button - its located on the same "hand" as move since its also related, and its used less often, meaning this less-comfortable-to-press button will be used less
6. Switch Weapons = button - located right infront of the trigger, meaning people can easily/quickly react situations where opponents suddenly appear while you have no ammo and switch to their secondary weapon (where there is ammo)
7. Killstreak/Use = button - located outside the "boundary" of trigger, because killstreaks are rarely used while you're shooting someone at the same time. Also, killstreaks are rare and precious, so the "boundary" protects users from accidentally hitting the killstreak button
8. Left Grenade = button - located on the left side of the gun near the trigger, intuitively mapped to the left and near the trigger because its some form of "attack"
9. Right Grenade = button - located on the right side of the gun near the trigger, for same reasons above
10. Melee = jolt gun in forward motion - good feedback from our DHP on this style of input
11. Sprint = tilt gun downwards - it'd be intuitive and (1 less button) if we incorporate this, since in game the soldier already tilts his gun downwards while he's sprinting
12. Aim Down Scope = cheek button (rotatable between left side and right side depending on left handed or right handed user) - good feedback from our DHP on this style of input

Finally, this gun is completely symmetrical (since cheek button can be rotatable) so its easy for lefties with their southpaw style too!

No comments:

Post a Comment