Paul Surgeon wrote:
Ok this is just a rough idea what do ya guys think?
I think that a variation of what you described should be relatively
straight-forward to do, at least to get some basic support for
season-based textures going ...basically it sounds similar to what
has been mentioned already in earlier discussions about this topic.
So, one could still later on refine these things - however, while
supporting the corresponding tags would be a no-brainer, one would
still have to look into the current texturing code in order to be
really able to assess how feasible it would ultimately be to get
the thing easily done.
Also, personally I would consider it more plausible to either provide
the season(s) for a texture either as a parameter - or simply as a
sub/child-node, instead of using a separate tag.
But that's then probably really only a cosmetical factor ...
But such a dynamic backend option would certainly be interesting
to have. The ESRI data sets do also seem provide data for different
seasons if I remember correctly, so one might even be able to use
some of that for that purpose, too...
P.S. Oops that took a few more lines to explain than I anticipated. :P
I can reassure you, that your posting is certainly not the longest one
this mailing list has seen - don't ask me how I come to know that ;-)
--------
Boris
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
