Dave Culp wrote: >> After I asked a bit around, I came to (my) conclusion that making external >> changes trough custom data on the Scenery is a pain. No chance to get >> custom Sceneries (not just objects) really good to run.
Karsten Krispin wrote: [...] > But there would be a better way: > > The holes which were now cutted by terragear could be cutted in runtime of > FGFS. > I'm glad you looked into it, because I was hoping to add Sembach Airbase, > EDAS, to my local Germany terrain. Looks like this may be more work than I > thought. I don't believe that cutting holes into the scenery at runtime meets the performance expectations of FlightGear users. Therefore we already have an airport database where everyone can submit their favourite airport definitions they make with TaxiDraw. On the other hand I'd be willing to maintain a PostGIS database where we could store hand-tuned scenery shapes that don't fall into the regime of TaxiDraw. Maybe this could somehow be coupled with the FlightGear Scenery Designer for input if someone adds the required bits to let TerraGear read the output. Unfortunately we can't store elevations in such a database but Norman promised to be he would give us an update as soon as progress is made in this area ;-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -------------------------------------------------------------------------- _______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
