-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Support Unity Editor #81
Comments
Unity Editor has some interesting behaviors that need to be factored into ROS2.net and the unity package. ROS2 itself needs to be enlightened to this fact (which we have a pending change up stream for), but also how load library works in ROS2.net. When packaging a component for Unity, metafile declare where individual binaries will be deployed - but they aren't in the execution path. LoadLibrary doesn't function correctly. Hololens has a similar problem - LoadLibrary itself is missing in the API set. You need to use LoadPackagedLibrary, which loads it from the UWP package. (A similar fix is made in ROS2 itself). (On top of this, the Unity native compiler will optimize out Reflection only methods (it doesn't know they are going to be called), so you need to add a link.xml to prevent the optimizer from destroying the ability to bind to ROS messages. This hasn't been addressed in ROS2.net documentation yet) |
Yes, and that's why Moreover, https://youtu.be/lQXtoK3w5X8 and https://youtu.be/mGTKNB-Iog0 show using Can you elaborate further what's needed? |
In Unity 2020, the Native compiler is now used. When the DllImport is present for an API that doesn't exist, the binary doesn't load - it is an untrappable exception. |
I'll look at it again |
This feature is being implemented by Azure Edge Robotics. Payload incoming.
The text was updated successfully, but these errors were encountered: