ros

Feature request

Autotuning allows you to specify the axes to use for tuning. This is currently done using parameters.

The latest version of MAV_CMD_DO_AUTOTUNE_ENABLE allows the GCS to specify the axes as a bitmask in param2. Zero indicates "do all" or "do default".

The action is to update the stack to use the

Steps to Reproduce

1. Create empty directory with the wizard
2. Add a robot and a join
3. In view, add "Show join axes"
4. Nothing seems to happens, because the line is too small

Expected behaviour
A line should appear.

Expected solution
Change the default lineScale value to 10, which make it visible, at least for a default project.
Two solutions, change the default templa

Just a tip for everyone: I was having trouble running an offline cluster where the Unity Editor was the master and a remote machine was the client. The remote machine was never able to connect to the Editor, but if I ran the standalone build as the master, it connects fine.

Make sure you don't have any blocking Inbound Rules in Windows Firewall with Advanced Security for the Editor version

Good day,
I think it will be a great idea to include some tutorials, same as TEB planner's tutorials.
Thank you.

Hi all,

I have looked into the marker example and according to the description in line 47, the commands from line 47-63 should modify the existing marker. However in reality, new markers are created.

Reason is the id 0 that is being set for the first marker: [this line](https://github.com/osrf/gaze