Hello,
Good News that AirNav have identify the problem.
i have make some tests, with screenshots, to understand how and when
RB freezing, and it's not easy .... (for helping AirNav, but if they have found the problem)
There is a "connection" with internet, but i don't think thats about slower
and disconnect, but rather request who have no answer.
Thats "funny" to observe that performance make slower with at first
information in the interface freez, after flight positions but not the trail
line and in the end all the system (and always with 1 processing photo or
info request ....).
in this "period" if we want to acces to another function, freezing is immediat.
No difference about computer performance (on the scope), when RB start freezing the processus goes to 00.
i think it's only with specific request, but i'm happy that AirNav correcting the isssue and waiting for the release.
Thanks for your hard job
i confirm the "bug" about local time in the report , and i my opinion
it will be better if ALL the date and time are on local time with
this option (screenshot, recorder, files ...).
Patrick / F6GSG