OHM Virtual NumPad

OrbitHangar

Addon Comments
Joined
Apr 9, 2008
Messages
3,832
Reaction score
18
Points
0

Author: fredericva

This addon enables laptop users without numpad to use their RCS, main, retro and hover engines, and to play orbiter without any extra external hardware.

A new custom command is added to Orbiter, which displays a virtual numpad on screen when activated. All buttons perform their normal function you'd expect when using the real numpad keys, and pressing CTRL for finer RCS thrust is supported.

The virtual numpad does *NOT* control the aerodynamic control surfaces, so most crafts won't be flyable in the atmosphere. This will not be fixed, as reentry and atmospheric flight is hard enough even with a physical numpad, so I'd really recommend getting an external numpad -or even better- a joystick for atmospheric flight.



DOWNLOAD
 
AMAZING

THANK YOU SO MUCH

i love this addon, and i couldnt be able to run orbiters RCS stuff without it, because im on a laptop :thumbup:
i really appreciate your help!
 
Nice job :thumbup:. I have a laptop that has a numpad, but spread across the keys, and it is difficult to use.

Thanks
 
Thank you for this very welcome addon, which is a boon to users like me who don't have any kind of numpad capability on their daily driver computers. I have been able to remedy most of this problem by editing keymap.cfg in my Orbiter root directory, so that the important standard commands are mapped to available key combinations. In particular I have mapped most of the ROT/LIN thruster commands to where the embedded numpad would be on this computer, if it had one: e.g. "I" is where the NumPad5 would be, so that gets mapped to KILROT.

But for addons that use their own numpad assignments, this doesn't work, or if it does I haven't mastered that yet. So again, many thanks.

I do have one question: I appreciate the fact that atmospheric flight is computationally complex, but why should that matter? Isn't this addon simply an interface? If so, does using Virtual NumPad entail a slight delay in accessing the control feature that causes the issue?

ETA: When asking if the NumPad is "simply an interface", I mean in the general sense rather than in the specific OOD-related sense.
 
Last edited:
Back
Top