On Wednesday, 12 January 2005 10:29, Martin Spott wrote: > > One other possibility you might wanna consider is allowing uploads/ > > dloads of terrain (e.g. tiles modified through fgsd). > > This is not as easy as it sounds because you'd have to redo the tiles > on every scenery update. The "right way" to incorporate manual scenery > changes would be to parametrize these changes and provide a method > to add them to the automatic scenery build.
Ideally all changes made to the terrain should be done at the source. i.e. VMAP0 and friends fgsd should be able to display, edit and save the vector data then use the terrgear generation tools to build the new tile and display the results. One could have a live online central repository (db) that handles the storage. fgsd can connect, request a tile of vector data for editing (The db can do some sort of locking on that tile to avoid simultaneous edits) Once the user is finished they upload the changes for everyone to use. Then when Curt builds the new scenery he just requests all the data from the updated DB. Simple stuff. Now who's going to write it? :P Seriously though a system like this would be "cutting edge" in comparison to the MSFS route of having every author releasing their little updates which have to be downloaded and installed piece-by-piece with no garauntees that there will be no conflicts between various authors. And boy-oh-boy do the MSFS community have problems with scenery conflicts! BTW : Does anyone know of a free VMAP0 editor for Linux? Paul _______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
