Skip to content

Releases: juchong/QuestNav

v0.4.0

21 Dec 12:11
Compare
Choose a tag to compare

This release adds the ability to reconfigure the team number on-the-fly. The feature is still a bit janky, so please read the rest of the release notes!

Known Issues

  • Changing the team number requires restarting the app
  • The app may appear to be very laggy on first start. This is caused by the DNS library blocking the main loop and is only an issue if the headset is actively connected to a robot network when the team number is set to a different subnet.
    • Workaround: Disconnect from the robot network, set the new team number, restart the app, and reconnect to the network.

Special thanks to @jasondaming for his help on getting the networking stuff sorted!

What's Changed

New Contributors

Full Changelog: v0.3.0...v0.4.0

v0.3.0

08 Dec 00:59
Compare
Choose a tag to compare

This release adds headset battery telemetry and cleans up the project details. It was also tested to work on the current public (not PTC) OS.

Full Changelog: v0.2.0...v0.3.0

v0.2.0

04 Dec 05:34
Compare
Choose a tag to compare

This build includes changes to the project name (QuestNav) and a few bug fixes to help address some of the "jumps" seen in AdvantageScope.

What's Changed

New Contributors

Full Changelog: v0.1.0...v0.2.0

Initial Release

16 Nov 12:48
Compare
Choose a tag to compare

Initial release. Mostly designed as an example project to demonstrate streaming pose information to an FRC robot. The team number is hard-coded to 9999. The robot IP address must be 10.99.99.2.