Josh Babcock wrote: > Here is a patch to view.nas to enable locking the view to a certain > direction regardless of the orientation of the aircraft. This is > especially useful for landing approaches. To use this you will need to > have two bindings: one that toggles /sim/view/lockview/active and one > that executes view.setLockView(). The first turns the system on and off, > and the second tells it what direction to point your "eyes". > > Currently it does not handle roll, so it breaks as soon as you diverge > from wings level. If anyone has any suggestions on how to fix that they > are welcome. Also, if there is a better way to implement it using a new > view, I would have no problem adding an eighth view that doesn't track > aircraft movement. This may be a more elegant solution, as it could > allow panning while the view is locked. > > I think this really gives a better feel for how the aircraft is moving. > I would like to modify it and add another mode where the pilot's view > tracks that of the aircraft orientation, but is run through a low-pass > filter first. That would allow you to see the bucking of the airplane > but still keep looking in a direction relative to the aircraft in the > longer term. Stay tuned. With the addition of a headshake nasal script > (in the works) this will add a huge amount of realism to the view in FG. > > Here's the CVS diff > http://jrbabcock.home.comcast.net/flightgear/lockview.1.diff > > Josh > > _______________________________________________ > Flightgear-users mailing list > [email protected] > http://mail.flightgear.org/mailman/listinfo/flightgear-users > 2f585eeea02e2c79d7b1d8c4963bae2d >
OK, I'm convinced that using nasal and not a separate view is the way to go. First, when yo switch to another view you loose all sorts of data, like the viewpoint for that particular plane, and any adjustments the user has made to that viewpoint. These could be copied, but it doesn't seem to be elegant to me. More importantly, this is basically just a way of controlling the slew and is functionally no different than using the mouse to do so. You are just letting the computer handle it for you. So, I'm going to keep working on the nasal script. My big problem now is how to convert from global heading/inclination to the local reference system in the cockpit. I have no experience with this, is is normally done with matrices? how would one go about it in nasal? Josh _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
