Use this button to overwrite the actual ARINC RNav database with the content of the current RNav content. If no action has been conducted on the RNav content, the database will remain unchanged. If some RNav items (waypoints, navaids, etc.) have been modified or removed, then the RNav database will be modified accordingly. This should be done after optimization (prune out).
If some RNav items have been manually added, question about merging them with the database will be asked. If answer is yes, then the added items will no more be tagged "user" and will belong to the RNav database.
The save process will use the file specified in File text field above. Change it in order to create another database and not overwrite the current one.
This function will remove from the memory all RNav records outside the terrains boundaries.
Using the button will rebuild the database file of (1) once the optimization is done.
Optimizing should be used to drastically reduce the amount of records loaded in memory when a scenario is concentrating only on a small area of the ARINC database. For example, using the europe.rnav database with a scenario doing ATC around Paris requires to much of memory. It is a good idea to optimize the database, rename the database as paris.rnav and save the optimized database under this new file.
button will rebuild the database file of (1) once the optimization is done.
