Tony Peden writes: > IMO, this can be good for catching obvious stuff, but > I personally would much rather hear commentary from a > pilot experienced in type.
I would agree, especially when you are getting down to really subtle tweaks. However, there is often things that are so 'obviously' not right that it only takes a little 'real time scientific visualization' to demonstrate the problem. > IANAP, so I often don't know how much stock to put in my own > impressions. There just isn't any substitute for getting the > thoughts of someone whose "been there and done that" I also think > that I know *too much* about the details of the aero and that pilots > who don't have an in-depth understanding of aero engineering can > oftentimes give better feedback than those who do. > Yes, it can be. You have the opportunity to iterate, > though you do need to be careful that you're flying > the aircraft in a repeatable way. With > post-processing though, repeatability is not as much > of an issue, its easier to look at many different > parameters, if needed, and other things like cross > plotting and data manipulation are easier as well. Again, it all depends on what you are trying to get out of the system. Some effects are very easy to repeat, some aren't. However, we could get so caught up over designing a graphing system to handle every possible eventuality that we design a system that's impossible for us to impliment in a finite time. That's worse than implimenting a simple approach that has 90% of the functionality you need. Sure we can spend all day pointing out situations where realtime graphing wouldn't be helpful, but if there are some situations where it would be helpful, and in fact preferable to post processing, then doesn't that make it worth doing? Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
