tudelft/UnifiedOptitrackClients

Issues

• Publishing messages for multiple rigid bodies in multicast

  #27 opened 8 months ago by mahimayoga
  8

• arm64 architecture not supported

  #23 opened 9 months ago by dfordequan
  1

• Move bigger implementations from .hpp files to .cpp files

  #10 opened 9 months ago by antbre
  0

• Refactor pose transformations into pose_calculations.hpp

  #2 opened 9 months ago by antbre
  0

• Error while running rospx4 client fix_minor_issues branch

  #25 opened 10 months ago by mahimayoga
  3

• Add option for ac-orientation correction

  #3 opened 10 months ago by antbre
  0

• Make custom ASCII art for each of the clients

  #7 opened 10 months ago by antbre
  0

• pull ahead natnetSDK to the new 4.1.0

  #17 opened 10 months ago by tblaha
  0

• Handle loss of tracking and loss of optitrack connection

  #21 opened 10 months ago by tblaha
  0

• protect against user setting higher frequency than natnet outputs. Or handle this case

  #20 opened 10 months ago by tblaha
  0

• remove "cyberzoo" everywhere in favour of something more neutral

  #8 opened 10 months ago by antbre
  0

• Support gazebo client

  #24 opened 10 months ago by antbre
  0

• Crazyflie support with Motive 2.0

  #14 opened a year ago by sstroobants
  2

• Improve logging to console and verbosity

  #11 opened a year ago by antbre
  0

• Find better way to join all threads and exit on errors

  #12 opened a year ago by antbre
  0

• add option to not autodetect natnet server, but rather use an IP from commandline

  #5 opened a year ago by antbre
  0

• Add option for user-defined coordinate systems

  #4 opened a year ago by antbre
  0

• Think of how to synchronize timestamps for the different clients

  #9 opened a year ago by antbre
  0

• Add support for ROS1

  #13 opened a year ago by antbre
  0

• Refactor natnet startup/detection code into start()

  #6 opened a year ago by antbre
  0