On Monday 12 November 2007 12:08:34 AJ MacLeod wrote: > On Monday 12 November 2007 06:31:26 John Denker wrote: > > Agreed! I've thought for ages that a top-to-bottom reorg > > would be helpful. > > The starting point for me was the realization that there > > are far more aircraft functions that need to be controlled > > than there are keys on the keyboard > > Which is why we have cockpit hotspots. The simple fact of the matter is > this; we model a vast array of aircraft, of almost every type imaginable. > We are modelling them in an ever more detailed way, and each aircraft > really is very different; far too different to provide enough key bindings > to make each aircraft controllable by the keyboard alone. > > For those who never fly or model anything other than single engine > light "training" type fixed-wing aircraft, perhaps the problem isn't so > noticeable; these are comparatively simple and probably have a reasonable > degree of commonality of functions between aircraft. > > There are, IMHO, very few functions indeed which really _require_ a > keyboard binding by default. Why try and squeeze every aircraft type and > function into one cramped mould? I don't think anyone is suggesting that. However now would seem a good time to get consensus on what _should_ be on the keyboard and what is best done via the menus and/or hot-spots.
In general, I like "realistic" start-up procedures (Lightning, Bravo, An-2 etc). At the hold I have time to run through the checklist and procedures and it adds greatly to the simming experience. I dont mind mousing to a hot-spot at this phase. In flight however there are functions I want on the keyboard or joystick and I want to get at them in (as far as possible) a simple and consistent manner. I dont have time to footer looking for the carb-heat hot-spot with a mouse etc So for the keyboard my wish list is gear g/G flaps [/] mixture m/M pitch n/N carb heat c (toggle on/off) seeing h is for the HUD wheel/air brakes b/B/ctrl B trim Home/End drag chutes and weapons release etc I feel should be on the keyboard but will leave the actual assignments to others This is pretty much as we have it for now _ I dont think we need BIG changes Stuff like hatches, cockpit hoods, liveries etc can be handled by hotspots where appropriate and menu items. Obviously a lot of the above I can do with joystick buttons and axes but then not everyone is lucky enough to have a Saitek Evo Oh and I'd like NOT to have any functions on the keyboard (such as the time-warp) that will screw up the flight if Im clumsy with the typing. On a slightly different note, is it time now to declare what I think most of us have known for a long time "There is no point in attempting to use FlightGear without a joystick of some sort"? I'd like to say a 4-axis stick but that may be a tad restrictive. If we state this upfront, we dont fail by delivering a good product that is disappointing to the user becuase the control input method is less than optimal. It also frees the arrow and number keys for possible reassignment for radios, autopilot. > > In situations such as this, the time-honored solution is > > to come up with a _language_. > > A good language has > > *) some orthogonality, and > > *) some mnemonic value. > > And will be detested (indeed, completely shunned) by the "average user". > While I can see your point, and some possible advantages with your idea, > it's a complete non-starter from the point of view of the non-programmer > "normal" user. > > Maybe most of us on this list find it natural to think in such terms, but I > can assure you (from dealing with typical "users" every day) that most > people don't. > > Just my opinion... and mine too... ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
