github RotorHazard/RotorHazard v4.3.0-beta.1
RotorHazard v4.3.0-beta.1

pre-release8 days ago

This is a beta-test version. Please post a GitHub issue to report bugs.

Highlights

  • "Community Plugins" area allows browsing, installation, and upgrading of community-submitted plugins
  • Improves performance of Format page for large events
  • Cooperative racing mode
  • Manage program and user data in separate directories, provide automatic migration
  • In-system configuration and first-run setup (removes need to create and edit config.json externally)
  • RHAPI 1.3: New field types, server-level settings, UI panel for Run page, calibration fallback filter, direct-to-database race importing

Note

The FPVTrackSide integration has been moved to an external plugin. It can be easily installed within RotorHazard using Community Plugins.

Documentation

Documentation for RotorHazard 4.3.0-beta.1 may be found at:
https://github.com/RotorHazard/RotorHazard/blob/v4.3.0-beta.1/doc/README.md
(New features in a beta release may not yet be documented.)

Installation / Upgrade Notes

Tip

RotorHazard Install Manager is generally able to install new beta versions within a few hours of release.

To install RotorHazard on a new system, see the instructions in 'doc/Software Setup.md'

To update an existing RotorHazard installation, see Updating an Existing Installation. The current version code is 4.3.0-beta.1

The minimum version of Python supported is 3.9. If your Python is older than this, you should upgrade using the steps in the Software Setup document under "5. Install Python." or set up a new environment. Do this before updating RotorHazard, or the update may fail.

RotorHazard Node Code

The node-code version is now 1.1.5 (introduced in 4.1.0-beta.1). Re-flashing your node processor is recommended if your current node version is older.

For STM32-based boards, the recommended method for installing the node firmware is to use the Update Nodes button (in the 'System' section on the 'Settings' page) on the RotorHazard web GUI.

Issues

If you encounter a bug, please report it using the Issues page on GitHub. When reporting issues, using the "Download Logs" button and including the generated '.zip' file is highly recommended.

The Server Log may be displayed via the "View Server Log" item in the drop-down menu. Clicking on the "Select Text" button will select all the displayed log text, which may then be copied and pasted. Clicking on the "Download Logs" button will create and download a '.zip' archive file containing all available log files and the current configuration and database files.

What's Changed

New Contributors

Full Changelog: v4.2.0...v4.3.0-beta.1

Don't miss a new RotorHazard release

NewReleases is sending notifications on new releases.