jcamilodo / kinect-ultra

Automatically exported from code.google.com/p/kinect-ultra
Other
0 stars 0 forks source link

lose calibration #5

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
when i go into the psi pose and attempt to do anything it loses calibration

it will start to overlay the red onto me and then it stops half way through. if 
it gets my whole body red then it loses me as soon as i turn or move.

i am using a core 2 quad and a geforce 9800GT 

Original issue reported on code.google.com by glitchca...@gmail.com on 18 Jan 2011 at 1:35

GoogleCodeExporter commented 9 years ago
I put some note in [FAQ_en] as far as I know about improving the motion 
detection. Although I could double-check my logic to look for anything wrong, 
but I do not think I could find anything unless I could reproduce the issue.

Original comment by tom...@gmail.com on 18 Jan 2011 at 8:48

GoogleCodeExporter commented 9 years ago
I have the same problem. I don't start turning red but strike a pose and it 
starts calibration but always seems to lose it then says Henshin=Human, using 
intel dual core and ATI Radeon 4870.

Original comment by techiere...@gmail.com on 22 Jan 2011 at 5:13

GoogleCodeExporter commented 9 years ago
I found the cause with a help from my friend. It seems this issue is caused by 
unstable versions of OpenNI, NITE, and KinectDriver. You should use stable 
versions for all components listed below, and then the problem should be gone.

(1) OpenNI stable: 
http://www.openni.org/downloadfiles/openni-binaries/stable/26-openni-alpha-build
-for-windows-v1-0-0/download
(2) NITE stable: 
http://www.openni.org/downloadfiles/openni-compliant-middleware-binaries/stable/
55-primesense-nite-beta-build-for-windows-v1-3-0/download
(3) KinectSensor driver for stable OpenNI: 
https://github.com/avin2/SensorKinect/blob/4e91f689fc5c8320f920b2976abdd9b50ee1b
af0/Bin/SensorKinect-Win32-5.0.0.exe

Original comment by tom...@gmail.com on 5 Mar 2011 at 9:17

GoogleCodeExporter commented 9 years ago

Original comment by tom...@gmail.com on 5 Mar 2011 at 9:40

GoogleCodeExporter commented 9 years ago
I noted this on the FAQ and WorkingConfigurations pages. I will note this on 
the README also when I release the new package.

Original comment by tom...@gmail.com on 5 Mar 2011 at 9:45

GoogleCodeExporter commented 9 years ago
In any ways, I may try to find a way to make this program work even on the 
unstable versions of OpenNI, NITE, and SensorKinect. I may be able to do it if 
I can reproduce this symptom in my place using unstable versions.

Original comment by tom...@gmail.com on 5 Mar 2011 at 9:07

GoogleCodeExporter commented 9 years ago
I found the discussion about (perhaps) this issue on openni-dev group at: 
http://groups.google.com/group/openni-dev/browse_thread/thread/f1a56bca901acfc1/
587a25b5acb33829

I tried some of their suggestions, but there were no differences. I cannot 
think of anything but using the stable versions until PrimeSense fix the issue.

Original comment by tom...@gmail.com on 6 Mar 2011 at 4:59