2022-03-09, 08:36 PM
You can always see the progress at the prefill row on the status page.
It shows you which set it is rendering and you see the chart numbers increasing.
It's just there to give you a smoother handling later. As it can at most consume around one CPU of the 4 available it should not really be a problem - and most of the time the Pi is idle anyway.
Unfortunately it will start over whenever you change settings.
But this process runs in the background - if you are showing a chart it will always prefer to work on your requests - and only continue the prefill if nothing else needs to be done.
Depending on the chart set sizes this really can take several (10+) hours.
In principle you cam limit the zoom level for the prefill (in the Server/Status page of AvNav at plugins you will find some settings for the ocharts plugin).
If you set this to e.g. 14 or 15 it will only render till this level and be much faster (with the cost of some potential delays later on when you are moving the chart).
Maybe you would like to play with this...
It shows you which set it is rendering and you see the chart numbers increasing.
It's just there to give you a smoother handling later. As it can at most consume around one CPU of the 4 available it should not really be a problem - and most of the time the Pi is idle anyway.
Unfortunately it will start over whenever you change settings.
But this process runs in the background - if you are showing a chart it will always prefer to work on your requests - and only continue the prefill if nothing else needs to be done.
Depending on the chart set sizes this really can take several (10+) hours.
In principle you cam limit the zoom level for the prefill (in the Server/Status page of AvNav at plugins you will find some settings for the ocharts plugin).
If you set this to e.g. 14 or 15 it will only render till this level and be much faster (with the cost of some potential delays later on when you are moving the chart).
Maybe you would like to play with this...