|
From: Israel E. <sri...@gm...> - 2026-06-02 16:30:09
|
Okay, I understand now. I don't foresee any problems with that; I just wasn't sure how to intercept the LOD rendering and slip in the ortho requests/downloads. Sounds good to me then! Hope everything goes well with that. ________________________________ From: Stuart Buchanan <stu...@gm...> Sent: Tuesday, June 2, 2026 9:23 AM To: FlightGear developers discussions <fli...@li...> Subject: Re: [Flightgear-devel] Experimental DSM-based terrain renderer with streamed orthophotos Hi, On Tue, Jun 2, 2026 at 5:13 PM Israel Emmanuel <sri...@gm...<mailto:sri...@gm...>> wrote: Oh, that might be interesting. So one query to a WMTS server would return all the LODs, or would you still have to make individual requests for each one? I think we would make individual requests for each one. There's no point in downloading all the LoDs for a 1x1 degree tile if we aren't going to see them all, and the aim of WMTS etc. is that you just request what you need. Also, I suppose a solution to this might be to have orthos download as LODs become visible. This might not work as all the LODs for a single tile are downloaded at once IIRC, but it might be something that can work a bit differently. Making this up as I go along: Yes - the idea would be that the ortho is requested (from disk/http) as FlightGear loads the WS3.0 scenery tiles. This happens in a bunch of separate threads, and would only replace the existing visible tile when it is complete. So from a user perspective all that would happen is that scenery would update a bit slower the first time as we download the ortho. -Stuart |