There is currently only one viable implementation of a ROS2 interface for Unity: ros2-for-unity. While it certainly works, its message generation using idl is cumbersome anmd very slow. On the other side, your approach enables a seamless integration with Visual Studio solutions, greatly simplifying the overall workflow on Windows. The C# message generation takes a fraction of the time with respect to ros2-for-unity.
This library currently targets .NET 7.0 8.0 and 9.0, whereas Unity only supports .NET Standard 2.1 and .NET Framework 4.8. As a result, the library is unfortunately incompatible.
Do you have any plans in converting the project to at least .NET Framework 4.8?
There is currently only one viable implementation of a ROS2 interface for Unity: ros2-for-unity. While it certainly works, its message generation using idl is cumbersome anmd very slow. On the other side, your approach enables a seamless integration with Visual Studio solutions, greatly simplifying the overall workflow on Windows. The C# message generation takes a fraction of the time with respect to ros2-for-unity.
This library currently targets .NET 7.0 8.0 and 9.0, whereas Unity only supports .NET Standard 2.1 and .NET Framework 4.8. As a result, the library is unfortunately incompatible.
Do you have any plans in converting the project to at least .NET Framework 4.8?