Forum Replies Created
-
Posts
-
Can you link to pictures of your sandbox during calibration?
For the second part, this is probably related to the Base Plane Equation measured in Step 8. If you change the fourth number (near -100.0) to a few centimeters less negative, it will raise the “sea level”.
Check the AR Sandbox World Map
If the CD never turns green the tie point capture will not work. It should turn green before you press the “1” key.
Make sure the CD is isolated from other things (e.g. sand, box wall, a hand). The calibration software looks for a circle.
I have a few questions to better understand what to are doing and seeing.
I’ll assume you are “calibrating Kinect” with RawKinectViewer. Which field in the output says “-nan”? Do you have a value for “Camera-space plane equation”?
I’ll assume you are using CalibrateProjector when the second problem appears. After the “warning window” appears, do you press a second, different key? When you try to capture the first tie point (by centering the target on the crosshairs and pressing “1”), does your terminal window show “Capturing 60 tie point frames…”?
AFAICT, “Mouse” is the name of the standard keyboard/mouse input device adapter. So, the “1” and “2” in the bindings line refer to the keys which would produce the numerals “1” and “2” in a text editor.
What is the path of the file that contains your config?
Please also post that config file’s full contents.
Thanks Sean for your help, i solved that problem
Did my answer solve the problem? Or did you need to change something else?
I tried to replace mouse with USBEncoder but i don’t know witch number or letter are the button.
You will need to know the keyboard key(s) assigned to the button(s). With the cursor in a text editor, what letter or number appears when you press the USB button(s)? Can you assign a specific key with the button’s software?
If you have two buttons set up with the letters “p” (piove) and “a” (asciuga), I believe you will need to change the line bindings ((Mouse, 1, 2)) to bindings ((USBEncoder, p, a)).
bindings ((Mouse, p, a)) works for me, on a normal USB keyboard, to flood and drain.
Should section USBEncoder be inside section HIDAdapter?
The example for “Using USB Input Devices Directly From Vrui.cfg” shows the WingmanExtreme3DPro is a child of HIDAdapter, not a sibling.
Thank you, that’s what I expected to see.
The Vrui Download page mentions Build-Ubuntu.sh may not work with Mint versions before v19. Can you upgrade to Linux Mint 19.3 Tricia? Your other option, on the same page page, is to try Build-Ubuntu-Old.sh.
Did I somehow miss this and your previous posts on the same topic or were they held for moderation until recently? Well, I see this post.
Could you post the output of lsb_release -dc? The output will tell me what OS version you are using.
I suspect from the line “g++ is already the newest version (4:5.3.1-1ubuntu1).” that you are running “Ubuntu 16.04 LTS (Xenial Xerus)”. This is probably too old to tun the latest sandbox version.
I apologize, but I don’t understand what is not working. Could you give the steps you are using and where it goes wrong?
Most of the parts for this are ready and just need to be connected together. I added an evaporationRate control pipe command to our sandbox for a similar purpose.
To the computer, the projector is just a display device. So that can be swapped with a monitor.
The Kinect needs to be connected. The live depth image is what the shader uses as input. I have an additional (donated) Kinect on my desk and pointed at a nearby wall for development. I understand about comfort; I’d much rather work in my office than standing at our arsandbox in the back corner of a stockroom.
Can you plug a monitor into the arsandbox computer and turn off the projector?
Otherwise, what about a second computer? I use a separate computer with an Intel HD Graphics GPU for development, it will even animate water (slowly).
My first guess is that you are not using “sudo RawKinectViewer”.
If using “sudo” does not solve your problem, please copy-and-paste the exact command and the exact error.
