General Question Laptop keymap?

[vorthon]

I use a laptop, and was wondering if anybody has a keymap suited to a QWERTY keyboard that is lacking a numpad they could share.

 

[diogom]

How to use Numpad on laptops, that's what you meant?
To use the Numpad keys, hold the fn key, next to the left Ctrl key, and press the keys with the numpad numbers.

 

[orbekler]

It depends on brands, it can vary. However there should be a PC key that enables the keypad, usually a part of standard keyboard. Of course on that part you won't be able to press letters again, until you switch off keypad.

 

[Ripley]

Maybe this?
[ame="http://orbithangar.com/searchid.php?ID=4473"]Virtual NumPad[/ame]

 

[Spacethingy]

Hmmmm, Virtual Numpad doesn't do aero controls - it's just like Orbiter's own built in remote vessel control.

I hate using the Fn key! You're doing nice precise RCS movements to align with the dock then... BANG! You accidentally forget Fn and so you suddenly start to align with the horizon... :lol:

 

[orbekler]

Hmmmm, Virtual Numpad doesn't do aero controls - it's just like Orbiter's own built in remote vessel control.

I hate using the Fn key! You're doing nice precise RCS movements to align with the dock then... BANG! You accidentally forget Fn and so you suddenly start to align with the horizon... :lol:

Yep, same to me, on my laptop, I'm forced to toggle between standard keyboard and keypad, another way around is to buy an external USB keypad.

 

[Ripley]

Exactly what Orbekler says, external USB keypad.

Vorthon, you asked for a keymap.
Do you know you can manually edit the keymap.cfg file in you Orbiter folder?

Searching for NUMPAD yelded this result:

(26 hits)
Line 33: IncHoverThrust = NUMPAD0
Line 37: RCSPitchUp = NUMPAD2
Line 38: RCSPitchDown = NUMPAD8
Line 39: RCSYawLeft = NUMPAD1
Line 40: RCSYawRight = NUMPAD3
Line 41: RCSBankLeft = NUMPAD4
Line 42: RCSBankRight = NUMPAD6
Line 43: RCSUp = NUMPAD2
Line 44: RCSDown = NUMPAD8
Line 45: RCSLeft = NUMPAD1
Line 46: RCSRight = NUMPAD3
Line 47: RCSForward = NUMPAD6
Line 48: RCSBack = NUMPAD9
Line 49: LPRCSPitchUp = NUMPAD2 CTRL
Line 50: LPRCSPitchDown = NUMPAD8 CTRL
Line 51: LPRCSYawLeft = NUMPAD1 CTRL
Line 52: LPRCSYawRight = NUMPAD3 CTRL
Line 53: LPRCSBankLeft = NUMPAD4 CTRL
Line 54: LPRCSBankRight = NUMPAD6 CTRL
Line 55: LPRCSUp = NUMPAD2 CTRL
Line 56: LPRCSDown = NUMPAD8 CTRL
Line 57: LPRCSLeft = NUMPAD1 CTRL
Line 58: LPRCSRight = NUMPAD3 CTRL
Line 59: LPRCSForward = NUMPAD6 CTRL
Line 60: LPRCSBack = NUMPAD9 CTRL
Line 67: NMKillrot = NUMPAD5

Then, if I'm not too wrong, you should also edit these lines...

Line 28: IncMainThrust = ADD CTRL
Line 29: DecMainThrust = SUBTRACT CTRL
Line 30: KillMainRetroThrust = MULTIPLY
Line 31: OverrideFullMainThrust = ADD
Line 32: OverrideFullRetroThrust = SUBTRACT
Line 34: DecHoverThrust = DECIMAL
Line 35: RCSEnable = DIVIDE CTRL
Line 36: RCSMode = DIVIDE

 

[vorthon]

Yeah, I'm aware that I can edit keymap.cfg.

Also, I feel stupid for forgetting about the FN key...

 

[Spacethingy]

Mucking about with me BIOS (as you do), I've just realised that some laptops can make numlock make the blue fn number keys work without fn.

 

[Ripley]

Then you can't use those keys for anything else until you reboot into your BIOS, can you??

 

[orb]

Then you can't use those keys for anything else until you reboot into your BIOS, can you??

I think they will work as normal keys again when you toggle the num lock off.

 

[Spacethingy]

I think they will work as normal keys again when you toggle the num lock off.

That's what happens for me!

 

[Ripley]

Ah! Never mind, hadn't quite understood what you meant...

 

[n122vu]

FWIW, Lenovo ThinkPads have a NumLock toggle. ScrLk key also has NmLk in blue. Can be turned on by Fn+ or Shift+ the ScrLk/NmLk button.

 

[Linguofreak]

I've not found it a huge problem with Orbiter, but on a desktop, numlock switches between arrow key behavior and number key behavior for the numpad. On a laptop (or at least mine), it switches between Fn being locked into the on state or not, and when Fn is on, it is *always* in the arrow key state, not the number key state.