Re: Experimental DSM-based terrain renderer with streamed orthophotos

Stuart Buchanan <[email protected]> Tue, 2 Jun 2026 17:03:21 +0100
Newsgroups gmane.games.flightgear.devel
Message-ID <CAP3ntytFXsNWt1Bim9sEKgiop5vJDFW1DByWgajOAejFrs7iyg@mail.gmail.com>
Hi,

On Tue, Jun 2, 2026 at 4:27 PM Israel Emmanuel <[email protected]>
wrote:

> <snip>
>
WS3, on the other hand, has LOD in its scenery, with 1x1 degree tiles being
> broken up into 16x16 grids. While you'll only ever be rendering 4 tiles at
> the maximum (if you're at a corner, for example), each one of those tiles
> will require 1024 requests for the highest levels of detail. Even rendering
> one tile at a time, this is not something that can be reasonably kept up
> with. Querying the ortho server fast enough to keep up with TerraSync will
> inevitably result in 504s for most requests, and now you have
> snaggletoothed terrain rendering. If you pace your requests to not overload
> the server, you are now waiting several minutes to download a single tile
> of scenery. That's alright if you're downloading ahead of time, but
> unusable if you're trying to download on the fly.
>

I understand that WMTS supports LoD natively.  So WS3.0 would simply
request a WMTS ortho tile at an LoD appropriate for the WS3.0 LoD level.  I
anticipate that the tile scheme won't match perfectly, one might have to
load multiple tiles, but that should be manageable.

-Stuart

_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel