ashtonaut
commented
6 years ago OK, so it seems I posted this too soon...
It wasn't clear that the sand region rectangle is defined via click and drag as opposed to defining corner points. I clicked and dragged and it started working! (this explains the 'expected X, got Y' message).
Perhaps some kind of error handling for this case could be incorporated, rather than the application crashing?
Anyway, for now, issue closed.
I am getting this crash on two different systems both running the latest release (1.5.4.1).
When I run magicsand, it opens fine, the projector does a white image, and I can see the video from the Kinect. Following the instructions, I then click 'manually define sand region' under 'calibrate'.
I assume that the next step is to click four times to define the boundary of the sand in the image.
However, after the first click, the program slows, freezes, and then becomes unresponsive and/or crashes.
The console screen displays the following information when it freezes:
It looks like it captures the first point, then freezes. Sometimes I get the final line ('expected ...'), sometime I don't.
I get the same crash issue on two completely different systems (both running Win10 64).
Unfortunately this means I can't progress the calibration at all.
Any ideas how to troubleshoot this crash?