|
Eyrie Productions, Unlimited
VoidRandom
Member since Dec-9-02
186 posts |
Jul-15-16, 08:08 AM (EDT) |
|
25. "RE: A shadowy flight, etc."
In response to message #13
|
>Generally, I've taken the consensus as this: Use physical switches for >very common, need to know where they are and have the physical >landmark, with reliability being something of a second (since so much >is computer controlled, but when it's that vital, they try to make >said computer controls so redundant, like 4-5 independent computers >polling, that if you lose the computer control, it's likely because >something destroyed the craft already). Use touch interfaces for >esoteric and menu selection functions, generally the sorts of things >that you're never going to be in a position to need to select it >hurriedly. A lot of military stuff uses a compromise design multi function display, typically a screen with hardware buttons near it. The screen indicates the current function of the buttons. This means you can put a thick protective cover on the screen, have a good chance of hitting the right buttons firmly in a moving and vibrating environment, and cram lots of functionality in. Standard hard controls are still used for controls you need constant or quick access too. CF-18 cockpit http://learntofly.ca/wp-content/uploads/2012/08/CF-18-Hornet-Pilot-Captain-Patrick-Paco-Gobeil.jpg?x M1A2 tank gunner position http://techgenmag.com/wp-content/uploads/2014/05/m1a2.jpg?x Of course, this is the USA practice. If you dig around in google you can see similar but different approaches in the AMX-65, recent revs of the Leopard 2 and T-90. Myself, I don't really like touchscreens. Tablets are fine, but fixed displays are always running into the "gorilla arm" issue. -VR You can even get a semi-fake (buttons work, screen doesn't) MFD from Thrustmaster to make your flight sims feel more realistic. "They copied all they could follow, but they couldn't copy my mind, And I left 'em sweating and stealing a year and a half behind." |
|
Alert | IP |
Printer-friendly page | Edit |
Reply |
Reply With Quote | Top |
|
|
Subject |
Author |
Message Date |
ID |
A shadowy flight, etc. [View All] |
Gryphon |
Jul-13-16 |
TOP |
RE: A shadowy flight, etc. |
Mercutio |
Jul-13-16 |
1 |
RE: A shadowy flight, etc. |
Gryphon |
Jul-13-16 |
2 |
RE: A shadowy flight, etc. |
Mercutio |
Jul-13-16 |
3 |
RE: A shadowy flight, etc. |
pjmoyer |
Jul-13-16 |
4 |
RE: A shadowy flight, etc. |
BobSchroeck |
Jul-13-16 |
9 |
RE: A shadowy flight, etc. |
Gryphon |
Jul-13-16 |
11 |
RE: A shadowy flight, etc. |
BobSchroeck |
Jul-14-16 |
17 |
RE: A shadowy flight, etc. |
TheOtherSean |
Jul-15-16 |
29 |
RE: A shadowy flight, etc. |
Gryphon |
Jul-13-16 |
10 |
RE: A shadowy flight, etc. |
Mercutio |
Jul-13-16 |
15 |
RE: A shadowy flight, etc. |
JFerio |
Jul-13-16 |
12 |
RE: A shadowy flight, etc. |
Wiregeek |
Jul-14-16 |
22 |
RE: A shadowy flight, etc. |
Pasha |
Jul-14-16 |
23 |
RE: A shadowy flight, etc. |
Wiregeek |
Jul-15-16 |
26 |
RE: A shadowy flight, etc. |
Gryphon |
Jul-14-16 |
24 |
RE: A shadowy flight, etc. |
Wiregeek |
Jul-15-16 |
27 |
RE: A shadowy flight, etc. |
Gryphon |
Jul-15-16 |
28 |
RE: A shadowy flight, etc. |
Peter Eng |
Jul-13-16 |
5 |
RE: A shadowy flight, etc. |
Mercutio |
Jul-13-16 |
6 |
RE: A shadowy flight, etc. |
Peter Eng |
Jul-13-16 |
7 |
RE: A shadowy flight, etc. |
JFerio |
Jul-13-16 |
13 |
RE: A shadowy flight, etc. |
VoidRandom |
Jul-15-16 |
25 |
RE: A shadowy flight, etc. |
Gryphon |
Jul-13-16 |
8 |
RE: A shadowy flight, etc. |
Mercutio |
Jul-13-16 |
14 |
RE: A shadowy flight, etc. |
drakensis |
Jul-14-16 |
16 |
RE: A shadowy flight, etc. |
Gryphon |
Jul-14-16 |
18 |
RE: A shadowy flight, etc. |
Meridias |
Jul-14-16 |
19 |
RE: A shadowy flight, etc. |
Lime2K |
Jul-14-16 |
20 |
RE: A shadowy flight, etc. |
Peter Eng |
Jul-14-16 |
21 |
version 3.3 © 2001
Eyrie Productions,
Unlimited
Benjamin
D. Hutchins
E P U (Colour)
|