Duncan Calvert

@SpaiR I haven't looked too much into what you're doing but I figured I'd throw it out there: Do you thing JavaCPP would address some of your needs? We've used...

Hi there! I just wanted to drop a quick note to say thanks for reporting this. Unfortunately, our team is super busy right now so we can't look at this...

Hi guys, yes it's necessary to set some of the message fields sizes larger and regenerate the messages. We haven't done that because we mostly use custom messages we maintain...

and by the way I am referring to these messages: https://github.com/ihmcrobotics/ihmc-open-robotics-software/tree/develop/ihmc-interfaces/src/main/messages/ihmc_interfaces/controller_msgs/msg

I think this code will do it: ``` public static String toStringFullPrecision(RigidBodyTransform rigidBodyTransform) { return EuclidCoreIOTools.getRigidBodyTransformString(EuclidCoreIOTools.getStringFormat(18, 18), rigidBodyTransform); } ```

I got 3 more NotARotationMatrixExceptions today. This feature would still be awesome.

Well there is a matrix in the printout I provided that's considered not a rotation matrix, but if you pack those values into a LinearTransform3D and get it as RotationMatrix...

Sneaky workaround ``` private static final Field referenceFrameHasBeenRemoved; static { try { referenceFrameHasBeenRemoved = ReferenceFrame.class.getDeclaredField("hasBeenRemoved"); referenceFrameHasBeenRemoved.setAccessible(true); } catch (NoSuchFieldException e) { throw new RuntimeException(e); } } public static boolean hasBeenRemoved(ReferenceFrame...

Two improvements would help: - Being able to change the parent frame - Being able to access the transformToParent to modify it rather than having to hold onto an instance...