> > I consider this as a required option for novices - although I might be > > proven to be wrong. Anyway I'd dare to suggest making running engines a > > default on startup - knowing that this might be an excellent start for a > > flame war ;-)))
I hereby deliver the flame war. 8-) _IF_ we had a checklist that novices could follow, including keystrokes dynamically recovered by reverse mapping the loaded keyfile, then the need to start engines would not be a hurdle to new users. I _DO_ think it's an important bit of realism to have users think procedurally. >> I'm quite interested in this topic because Michael Basler and I are required >> to have precise information on this for putting the right phrases into the HOWEVER, I also think the checklist package should be a set of textures in the base package, which are reproduced in the getting started guide, with keystroke/menu type action items to bring them up and page through them. For novices, we use an alpha-ed texture that overlays the screen, so you can still see the panel and the view while reading the text on the texture. For realism, we blank the panel and the view and show only the texture on screen, because that reproduces the limitations of the human eye, forcing the pilot to switch between checklist and view frequently (every few secs) to maintain control while looking something up. For 0.7.9 I suggest we don't actually do the FGFS code modification, but do think about generating the checklists and making them available. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
