simon wrote:
I don't think adding more views is the way to go long term. Would you
add multiple views (cockpit/helicopter/chase) for each multiplayer
aircraft? For each AI aircraft? For each carrier? For each X model?
That's a lot of views to scroll through to get the one you want, not
to mention the redundancy overhead.
For my part I thought of having an identifier for each set of views, so
that I could select a multiplayer aircraft and cycles through all the
views belonging to that aircraft. I don't really know the overhead
involved in adding several views for each aircraft, and possibly other
structures.
To me, a view is really just a set of position and orientation sources
and targets, position and orientation offsets, fov and a few other
configuration settings. My goal is to be able to switch from-model
type, index, and offset, at-model type and index for any given view.
Not only would it be nice to be able to switch the model you're
viewing from (multiplayer,tower,carrier), it would be nice to switch
the model you are looking at, if any. Basically, a more open viewing
system that would allow fly-by views using nasal (my original goal),
bomb - uh, I mean drop tank - view all the way to the ground,
switching models by type, and anything else you can dream up in nasal.
This resembles my initial approach of modifying the properties of the
already existing news based on the selected multiplayer aircraft.
As it seems you have done quite some work on this, and have better
knowledge of the system than myself, I'll let it lie and let you get on
with it :). If, after all, there is something I can do, let me know. I
have implemented a simple approach of modifying the existing views for
the selected multiplayer aircraft, and I was now looking in to adding
use for each multiplayer aircraft as they appear in the hope that I
would get an approach without the synchronisation problems I described
earlier. I suspect that the problem was caused by the fact that
_target_location was created from current multiplayer position, while
the camera position was read from the property tree.
--
Frank Olaf Sem-Jacobsen
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
