Re: RFD: Landmarks and scenery (was Re: [Flightgear-devel] CYTZ andCN Tower)

[Matevz Jekovec]

Curtis L. Olson wrote: David Megginson writes: Lee Elliott writes: > Perhaps we need a directory in Scenery that can be scanned for > world landmarks like this. Could the model and location data be > defined in an xml file? Would it be possible to animate them? > (thinking rotating restaurants and swing bridges here). I've been thinking about this for a while, and I think that the best approach would be to read scenery from multiple directories at once. For example, I could have the main scenery under /usr/local/FlightGear/Scenery/, and major landmarks under /usr/local/FlightGear/Landmarks/, and configure it something like this: FG_SCENERY_PATH=/usr/local/FlightGear/Scenery/:/usr/local/FlightGear/Landmarks/ What if we create /usr/local/FlightGear/Scenery/Terrain and /usr/local/FlightGear/Scenery/Models. For env. variables we should only have FG_SCENERY_PATH=/usr/local/FlightGear/Scenery. Or possibly FG_SCENERY_MODELS_PATH, FG_SCENERY_TERRAIN_PATH to override it and set custom paths in case of e.g. terrain dedicated server or too small disk. I think we shouldn't name models as "Landmarks", because we can model djamia, hay layer, wind mill or some other 3d models specific for quite some areas (not all of course) and I wouldn't call them landmarks. So structure I prefer would look like that: /FlightGear: ----/Scenery:                     --------/Terrain:                 // Same as Scenery directory now ------------/e010n40...       // These terrains have pointers to the models with their coordinates then ------------/w130n30... ------------/w130n40... --------/Models:                  // New directory meant only for models of the scenery (this includes airports!) This will include all the 3d models and its textures, zipped with comment in which terrains we can spot them and maybe some other useful info(this is for information only and FG shouldn't depend on it) ------------/General: ----------------church01.gz       ----------------church02.gz ----------------djamia01.gz ----------------windmill01.gz ----------------windmill02.gz ----------------windmill03.gz ------------/Landmarks:        // Landmarks or small area specific objects (e.g. those funny painted houses in few towns in Switzerland:)) ----------------toronto_tower.gz ------------/Airports: ----------------KSFO.gz          // This could include driving paths on taxiways, parking spaces and other static data as well! ----------------LJLJ.gz When you'd download the new scenery, you would get a zipped terrain + specific models. General very common objects to all terrains (ie. trees) should be already present in base package under General folder. The only problem here is how to organize this scenery packages even further, not to get too large scenery packages while most of the objects are already present (General folder can become quite large and maybe won't be included as a whole in base package). Maybe to make sets of e.g. windmills (all from Holand to USA) and djamias (from Iraq to European branches) etc. If the model isn't present, FG should simply ignore it and not render it. - Matevz

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