-
Notifications
You must be signed in to change notification settings - Fork 26
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
Cannot read 6DOF body with residuals #55
Comments
TL;DR - Could it be that you didn't use "Play with Real-time Output"?It seems to be working for me. Here's a list of the steps I took / the test code I wrote. I started QTM and opened a file with one 6DOF rigid body and pressed "Play with Real-time Output" (found in the "Play" menu). I started the RTClientExample and used the following operations: Enter(x4) --> 8 (6D with residuals) --> 3 (frame by frame) --> 1 (show current frame). Calling that will execute the code in the else-statement found in RTClientExample/Output.cpp on line 140. Prior to running RTClientExample, I commented out all the code in that else-statement (starting on line 140) and replaced it with the following:
|
@mihaelapopescu If I misunderstood something, or if you have any more questions, don't hesitate to let me know / ask. :) |
Thank you very much and sorry for the delayed reply. In my case I am streaming live data instead of recorded data. Is there anything else I should enable in QTM to get the residuals as well? I used a similar approach to yours to get the residual rigid body data, but |
I am able to read the 6DOF rigid bodies using
Get6DOFBodyCount()
andGet6DOFBody()
. However, when I want to access the 6DOF with residuals usingGet6DOFResidualBodyCount()
andGet6DOFResidualBody()
, the count of rigid bodies is zero and there is no rigid body data streamed. I followed the minimal example from RigidBodyStreaming.cpp. Is there something else that should be done in order to enable the residual streaming? As a remark, I can see the residuals for all rigid bodies in QTM. Thanks!The text was updated successfully, but these errors were encountered: