Hi Eveybody, The text document linked below outlines a format for view configuration using the new viewer. The interface and backend that could support this is pretty much done. The only thing left is to finish the viewmanager, hence this document.
Overview: The "config" branches should be set in prefrences.xml (with a couple exceptions). The "current" branches generally would not be in config xml but would be readable and writeable by the application (in fact most of these will just be moved from other locations and renamed). The general principle is that there are only two viewer modes. One is "lookfrom" and the other is "lookat". They are comparible with our current "pilot" and "chase view". The basic difference is that "lookfrom" constructs the view frustum according to a vector that is always perpendicular to the eye. The "lookat" constructs the view frustum centered along a vector that goes from the eye to an object center. Either or both the eye point or the object point can be static or moving. A tower view could therefore be either "lookat" or "lookfrom" depending on what it is that you want to see. Tower as defined in the proposal would be "lookat" and would therefore follow an object down the runway. Also this structure will allow flexibility in defining views for multiple aircraft, and fdm instances, (both AI and piloted) down the road. This is because the position data is defined outside the viewer. This file contains an outline of the property structure (not just the config): http://www.spiderbark.com/fgfs/viewconfig.txt Comments? Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
