

* The new key is called "CatalogExpert" and should be entered like this in the OpenCPN config file: * Developers and experts have access to Alpha and Custom catalogs by editing the config/ini file. Only use the "Beta" Catalog, if specifically told to do so. That will ensure that you have access to the latest updates and all available Managed Plugins.Īlways use the "Master" Catalog. This "detour" in plugin installation will be corrected in future releases.Ĭlicking on a listed plugin reveals the options and actions available for the specific plugin.Īt the bottom of the Plugin Manager there are some general controls.Īlways make it a habit to click "Update Plugin Catalog: Master". New Linux users are recommended to install the legacy plugin from the PPA first, and then upgrade to the managed version. Debian based Linux systems, installed the traditional way, can use either use "Managed Plugins" or install plugins through the PPA. OpenCPN on Linux, installed with Flatpak should use "Managed Plugins". "Plugins not managed by OpenCPN", are plugins handled by the operating system, currently Debian based Linux packages. "Managed Plugins" are plugins handled by the new Plugin Manager. Other icons/states exist, and are documented with similar popups.

It is also important to know about the bug fixes, especially for users that have never used the 4.8 series of OpenCPN releases.Īllows Plugin installing and updates from within OpenCPN using a trusted repository. Here we concentrate on the new features in OpenCPN.

What's New in V5.2 Version 5.2 includes a number of new features as well as a large number of bug fixes.
