Closed glennliu closed 3 years ago
Hi @glennliu thanks for the question. I'll have a look at it in a few hours ok? -Eric
Ok so on a first and quick look the case is the following: I forked this repository from @dwhit who did the main bulk of the work. I made some final adjustments because on the newer Unity & HoloLens versions Ros# did not work anymore. His fork is 101 commits behind the original master at (Siemens/RosSharp). I'll may have time in the following weeks to synch this fork with the main repository, such that it provides all the functionality it does there.
So thats the main reason for the big differences between both versions. This fork is just a bit older.
Thanks. I realized this should be an issue that originated from /dwhit/RosSharp. I posted the issue on his forked as well. If I can work it out, I'll update my solution.
Currently working on the update on this branch. The message generation will look exactly the same at some point as it does in Siemens/RosSharp
Hi @EricVoll
I used your code of ROS# successful, which can be built on UWP platform.
But the RosSharp messages generation is quite different with the original code. Can you please explain a bit about message generation? How to generate a "sensor_msgs/PointCloud" message in your code?
Thanks