Despite NavimetriX's constant focus on optimisation, the wide variety of devices that can be used makes it impossible to guarantee optimal performance in every case. The prerequisites stated in the FAQ (1) are sometimes not enough, as technical specifications can be limiting on certain device ranges. It is therefore advisable to take precautionary measures to minimise the malfunctions that may be encountered.
Unexpected closure on launch or during use
An immediate closure on launch is often caused by a large number of saved routings that are reloaded at every start-up. This can be enough to cause the application to close immediately after opening by instantly saturating the RAM.
Only keep routings currently in use, especially if you are running ensemble routings, which are very heavy, as they are stored on our servers for synchronisation. A routing is only valid for the lifetime of the weather models it uses. Once it has expired, there is no need to keep it. If necessary, you can export it and re-import it later as a route.
RAM saturation can also cause unexpected closures during use, when launching a resource-intensive function: end of a long routing with an isochrone step that is too short or a search area that is too wide (> 220°), or an ensemble routing.
Degraded display
Sluggishness during screen interactions (zoom +/- functions, scrolling), or the appearance of black areas (partial or total loss of chart display) are often caused by RAM saturation on poorly equipped devices. Make sure to close and quit unused applications to free up RAM.
Also, to improve smoothness, the heaviest layers to disable are AIS, data stations (InSitu) and the track. Displaying GRIBs as particles is also graphics-intensive and drains the battery. Prefer arrow or barb display while navigating.
———
(1) See also: What are the minimum operating system versions?