Test File: Point In Screen / 3D Hitbox Checking

[snarks]

test_PointInScreen is up for testing.

Turns out that PApplet has screenX() and screenY() to convert 3d points to 2d

[hype]

I pushed the Kinect example we were working on / can you update my code to use screenX() and screenY()

[snarks]

Status update: I'm just gonna lay down what information we have.

Kinect Model

Model 1473 for Xbox 360 (the new one)

Processing Version

2.0b9 (pre release build 9 for 2.0)

Main Issue

When using SimpleOpenNI with Processing 2.0b9 (pre release build 9), our simple depth image sketch runs normally until after about a minute. The red lights from kinect's camera are still visible during this time.

Afterwards, the framerate drops dramatically (but not fully stopped), and the red lights are no longer visible from the camera. The depth image seemed to stop updating. The call to context.update() seems to be the source of the lowered framerate.

Test Sketch Source

import SimpleOpenNI.*;

SimpleOpenNI context;

void setup() {
  context = new SimpleOpenNI(this);
  context.enableDepth();
  size(context.depthWidth(),context.depthHeight());
}

void draw() {
  print("["+frameCount);
  context.update();
  println("]");
  image(context.depthImage(),0,0);
}

Stuff to Test

• Use Processing 2.0 (stable)
• Directly use the Java wrapper for OpenNI, instead of Simple OpenNI

[snarks]

Using Processing 2.0 (stable) doesn't seem to cut it. I'll try directly using OpenNI instead.

[snarks]

I tried using Simple OpenNI with Eclipse (default java, not the processing plugin), and the same thing happens. Now we know that it's probably not an IDE issue.