Talk:Hackathon Proposal: Performance Improvement for Ortho Scenery

Hi, I am the developer of photoscenary.jl I fully agree with your proposal as I know very much the problem you are posing and which requires a solution. For the LOD currently photoscenary.jl manages it in a very simple way, using lower resolutions as a function of the absolute distance, that is the distance between the plane and the center of the tile to be loaded. To handle this, there is no function in the loader that defines the LOD choice criterion. In my program I have inserted a separate directory called save which defines a series of folders with the resolution used, then physically copies the file and places it in the Orthophotos folder with the right resolution according to the distance. It seems strange, but it is a very fast process as the transfer of files is done with a low CPU usage (at least for UNIX and Mac systems). The problem is how to warn FGFS that a new tile has been loaded and that then FGFS must use it without refreshing the scenario. It would be enough for FGFS to have a property that, if activated with the tile id, leads to its refresh without interrupting the flight with a separate process. In fact I see two procedures, the first one that loads the images on a separate process for not loading the CPU and therefore lowering the frame rate. The second is a procedure that reads the specific property tree property with the tile id and performs the refresh. What do you think ? --Abassign (talk) 07:53, 11 October 2021 (UTC)