-
Notifications
You must be signed in to change notification settings - Fork 105
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
skeleton tracking #65
Comments
I seem to remember the window being a solid color as well, but I had no problems with the library on windows 10. Here is kinectpv2 skeleton3d working with toxiclibs.
https://github.com/slowizzm/Processing-Gallery/tree/master/kinectParticles_spine
…Sent from my iPhone
On Aug 21, 2017, at 9:57 PM, SimonBiggsUK <[email protected]<mailto:[email protected]>> wrote:
I have the skeleton3d example working correctly in Windows 8. However, in Windows 10 instead of seeing the skeleton I just see the whole display window changing colour. Is there some issue with 3D skeleton tracking in Windows 10?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#65>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AOR0m3yu1qkepmEMTKUovRIdIQwVD8ekks5sakOXgaJpZM4O-DbO>.
|
Thanks |
Yes, the AttractionBehavior class is part of toxi.physics2d.behaviors. Not sure why it would not be working properly. I do remember initially having issues with processing pointing to the library. You may just need to restart a few times until process locates it.
…Sent from my iPhone
On Aug 22, 2017, at 8:14 PM, SimonBiggsUK <[email protected]<mailto:[email protected]>> wrote:
Thanks
I've downloaded your example along with toxic and mesh libraries and installed everything but the app will not run as it can't find the class AttractionBehavior - which I think is part of the toxic library. Am I missing something?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#65 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AOR0m4tUUKtVohi6lNYZhvb4z8Pq70FHks5sa3zmgaJpZM4O-DbO>.
|
Hello, I had the same problem. It seems that the strokeWeight depends on the z-value of the joints, but it's not properly scaled (or maybe the function or the map scaling have changed across the version). |
I've found that turning off the setColor function to the kinematic object (PJBullet) attached to the joint incoming from Kinect the flashing problem has gone away. I am assuming I've not fixed the problem but have stopped the symptom. I can live with that for now. |
@SimonBiggsUK Many thanks! |
pJoint is only applicable if you are rendering the skeleton in the JBullet physics engine. Is that what you are doing? If not then it's not relevant, which is why you can't see the function call. What you can try is only drawing the bones and commenting out the joint drawing. This gives you a clean skeleton image. I found that after doing that I didn't have anymore artefacts. I think the problem is one of a mismatch in scaling, which affects the joint drawing but not the bone drawing. You might need to add some extra bones to incorporate all the joints. Set the strokeweight to something light, like 0.01. Here's the relevant code: void drawBody(KJoint[] joints) { void drawBone(KJoint[] joints, int jointType1, int jointType2) { |
Thanks for the quick reply! Thanks so much!!! |
1 similar comment
Thanks for the quick reply! Thanks so much!!! |
I have the skeleton3d example working correctly in Windows 8. However, in Windows 10 instead of seeing the skeleton I just see the whole display window changing colour. Is there some issue with 3D skeleton tracking in Windows 10?
The text was updated successfully, but these errors were encountered: