Nicolò Genesio (二コゲネ)

> Does this also happen in a “gazebo-only” environment? I created and environment `gazebo_only` such as: ``` mamba create -n gazebo_only -c conda-forge gazebo ``` And `gazebo` works smoothly

> Fixed in the latest rebuild - this now pulls in gazebo built with ogre 1.10 which works nicely :) > > /cc @b1n-ch1kn Thanks heap @Tobias-Fischer!

> Will the device also perform some internal computation (e.g. for differential joints) or it is just a remapping of encoders data? My idea was to get the actuated axis...

> > * The device name > > * The interfaces that implement > > * The interfaces that has as private attribute members > > Name is ok for...

> > > * The device name > > > * The interfaces that implement > > > * The interfaces that has as private attribute members > > >...

An important update on this, I managed to finish the first working version of `controlBoardCouplingHandler` device. In the end I sorted out that this device just needs the `coupling_device` parameter...

cc @martinaxgloria

Looking at the code it seems that `gazebo_yarp_camera` does not inherit from `IRGBVisualParams` or the IRGBDSensorsInterface so it surprise to me that the `poly->view()` is working. @randaz81 are `IFrameGrabber` and...

> > IRGBVisualParams or the IRGBDSensorsInterface so it surprise to me that the poly->view() is working. > > Isn't that because there is an extra layer made by the `rgbdSensor_nws_yarp`...

Thanks to https://github.com/robotology/gazebo-yarp-plugins/pull/584 and https://github.com/robotology/gazebo-yarp-plugins/pull/583 the support has been extended also to `gazebo_imu` and `gazebo_forcetorque`