[Flightgear-devel] objects lifetime

[Matevz Jekovec]

I was thinking of the way we could ommit lifetime for our terrain and 
scenery objects. For e.g. if we get a WTC towers models or some other 
historical buildings one day, we cannot place them into year 2003. What 
if every object has a timestamp - an interval from when to when certain 
object lies in time. For WTC twin towers should be from 1972/1974 to 
2001 then. For e.g. our house, from 2000 and on etc. We could also place 
these timestamps to the terrain vertices, roads, rivers if they have 
changed over time and even textures for them (this way, the cities in 
1800 wouldn't be large as nowadays). e.g. highways in our country have 
changed the terrain drasticly in last 10 years!
Cause another e.g. if we implement a dynamic campaign (war) some day, we 
could really make a simulation of a historic battle in 1945, using 
certain units hiding behind certain buildings standing in that time etc. 
For modelers I don't think this should pose a large problem as they 
probably know enough about the building they are modeling and their 
timestamp. For the terrain, this is a bit more complicated though.
In practice, when you'd run fgfs only, you would be placed in present, 
but if you run fgfs --date=19990815, you would be placed in August 1999.
Just a brainstorm idea, but what do you think?

- Matevz

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel