(Computer specs follow at bottom of post)
(Thread title changed to focus on the numpad/numlock issue, which is resolved (Thanks, Helior!). There may still be mouse issues in some of the GUI based controls, in the generic and specialized virtual cockpits.)
I recently got a two-in-one notebook computer*, and like with all computers I've bought in the last eight of so years, installing Orbiter is one of the first things I've done. I've been using both 2006 and 2010.
There's no function lock or embedded numpad, and obviously there's no physical 10-key pad. I've tried an Android app that sets up my smart phone to function as an external numpad. This works for typing numbers, but provides no method for doing CTRL or FN combination keystrokes.
But even without a numpad, I'd think I would be able to control the spacecraft using a combination of the standard cockpit controls--like HLevel, KillRot, and Prograde, plus the custom external control module, but this usually doesn't work either. The exact behavior varies from spacecraft to spacecraft, and I will provide more details of that. But a couple of specific scenarios will serve to illustrate a general pattern.
In Orbiter 2010, under Delta Glider, using the "DG-S Ready For Takeoff": I can use the graphical sliders, or RControl, to start accelerating down the runway. However, the "U" button on RControl will not engage and the DG never takes off, but continues along the ground. When the scenario is started, "ROT" in the upper left of the generic virtual cockpit is disabled (set to "OFF"), and I can seemingly enable it with a click of the mouse. However, the "U" button still doesn't work.
Again in 2010, under Gemini--Reentry: The thruster setting is LIN, but I can mouseclick it to ROT. However, the RControl attitude control buttons remain ineffectual. From the behavior of the display it does seem that the mouse button click is recognized, as the button graphic visibly responds to being "pushed". The same is true of the standard attitude controls in the generic virtual cockpit--if I left-click on them with the mouse button, they will light up and appear to be activated as they should, but nothing happens. It's like being in a spacecraft with zero fuel in the RCS system.
In sum, I seem to be experiencing a general problem with using Orbiter in W8.1, beyond just not being able to use the keyboard shortcuts. Is this experience typical? I see quite a bit of posting about the difficulties posed by the lack of a numpad, but nothing about a wider problem for 8.1 users. (As I said, I haven't seen it, but it's certainly possible I've missed something.) This concerns me as it suggests that mere keypad workarounds won't solve my problem.
*i.e., the kind that lets you pivot the screen all the way around so it's flat against the bottom of the keyboard, so you can then use the touch screen like a tablet.
--------------------------------------------------------------------------------
HW and OS specs:
---------------------------------------------------------------------------------
WINDOWS EDITION: Windows 8.1
OEM: ASUS
MODEL: Q301L
PROCESSOR: Intel Core i3-4020U CPU @ 1.90 GHz 1.90 GHz
SYSTEM TYPE: 64-bit OS, x64-based processor
PEN AND TOUCH: Full Windows Touch Support with 10 Touch Points
Installed Memory (RAM): 6.00 GB (5.89 GB usable)
HDD 500 GB (61 GB currently used)
MOUSE: Just the standard two buttons and touchpad on the computer keyboard. When I say "mouse" I mean this configuration rather than a true external mouse.
---------- Post added 03-26-15 at 12:18 AM ---------- Previous post was 03-25-15 at 10:13 PM ----------
ETA: I just found this post from Donamy, explaining that the Remote Control module doesn't work correctly for Spacecraft3 vehicles. So that explains a big part of my problem right there.
(Thread title changed to focus on the numpad/numlock issue, which is resolved (Thanks, Helior!). There may still be mouse issues in some of the GUI based controls, in the generic and specialized virtual cockpits.)
I recently got a two-in-one notebook computer*, and like with all computers I've bought in the last eight of so years, installing Orbiter is one of the first things I've done. I've been using both 2006 and 2010.
There's no function lock or embedded numpad, and obviously there's no physical 10-key pad. I've tried an Android app that sets up my smart phone to function as an external numpad. This works for typing numbers, but provides no method for doing CTRL or FN combination keystrokes.
But even without a numpad, I'd think I would be able to control the spacecraft using a combination of the standard cockpit controls--like HLevel, KillRot, and Prograde, plus the custom external control module, but this usually doesn't work either. The exact behavior varies from spacecraft to spacecraft, and I will provide more details of that. But a couple of specific scenarios will serve to illustrate a general pattern.
In Orbiter 2010, under Delta Glider, using the "DG-S Ready For Takeoff": I can use the graphical sliders, or RControl, to start accelerating down the runway. However, the "U" button on RControl will not engage and the DG never takes off, but continues along the ground. When the scenario is started, "ROT" in the upper left of the generic virtual cockpit is disabled (set to "OFF"), and I can seemingly enable it with a click of the mouse. However, the "U" button still doesn't work.
Again in 2010, under Gemini--Reentry: The thruster setting is LIN, but I can mouseclick it to ROT. However, the RControl attitude control buttons remain ineffectual. From the behavior of the display it does seem that the mouse button click is recognized, as the button graphic visibly responds to being "pushed". The same is true of the standard attitude controls in the generic virtual cockpit--if I left-click on them with the mouse button, they will light up and appear to be activated as they should, but nothing happens. It's like being in a spacecraft with zero fuel in the RCS system.
In sum, I seem to be experiencing a general problem with using Orbiter in W8.1, beyond just not being able to use the keyboard shortcuts. Is this experience typical? I see quite a bit of posting about the difficulties posed by the lack of a numpad, but nothing about a wider problem for 8.1 users. (As I said, I haven't seen it, but it's certainly possible I've missed something.) This concerns me as it suggests that mere keypad workarounds won't solve my problem.
*i.e., the kind that lets you pivot the screen all the way around so it's flat against the bottom of the keyboard, so you can then use the touch screen like a tablet.
--------------------------------------------------------------------------------
HW and OS specs:
---------------------------------------------------------------------------------
WINDOWS EDITION: Windows 8.1
OEM: ASUS
MODEL: Q301L
PROCESSOR: Intel Core i3-4020U CPU @ 1.90 GHz 1.90 GHz
SYSTEM TYPE: 64-bit OS, x64-based processor
PEN AND TOUCH: Full Windows Touch Support with 10 Touch Points
Installed Memory (RAM): 6.00 GB (5.89 GB usable)
HDD 500 GB (61 GB currently used)
MOUSE: Just the standard two buttons and touchpad on the computer keyboard. When I say "mouse" I mean this configuration rather than a true external mouse.
---------- Post added 03-26-15 at 12:18 AM ---------- Previous post was 03-25-15 at 10:13 PM ----------
ETA: I just found this post from Donamy, explaining that the Remote Control module doesn't work correctly for Spacecraft3 vehicles. So that explains a big part of my problem right there.
Last edited: