-
Notifications
You must be signed in to change notification settings - Fork 203
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
send skeleton data to server? #31
Comments
Hi, Have you tried enabling the skeletons in the Server's settings? Marek |
Hi guys, I have tried to set the option for skeleton view or body view in the server settings, but each time I set the "body view only" this crashes the Live View screen. Also if the "Skeleton View" is checked then no skeleton is shown in the live view. any ideas? |
Hi, is this on the AzureKinect branch? If so, the skeletons are not supported there so far :( Thanks, Marek |
Hi Marek, yes it is on the Azure branch. Will you be rolling out a version on the azure branch in the future?CheersEarl
-------- Original message --------From: Marek <notifications@github.com> Date: 22/1/21 12:15 (GMT+01:00) To: MarekKowalski/LiveScan3D <LiveScan3D@noreply.github.com> Cc: earlsorensen <earl.sorensen@gmail.com>, Comment <comment@noreply.github.com> Subject: Re: [MarekKowalski/LiveScan3D] send skeleton data to server? (#31)
Hi, is this on the AzureKinect branch? If so, the skeletons are not supported there so far :(
Let me know if it's on the master branch and then we can debug it.
Thanks,
Marek
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hi, not sure when I'll have access to Azure Kinects again, so at the moment I do not have plans to add that functionality. |
Hello Marek
First I wanna thank you for this amazing project.
I notice the software can handle skeleton data now but I didn't see skeleton in the live view window.
I only saw skeleton in the client window.
Also could you please tell me how to send skeleton data to the server?
Thanks
The text was updated successfully, but these errors were encountered: