Forum Replies Created
-
Posts
-
came close to success.
Actually, the compiling errors ou posted in the Linux Mint forum hints that there are many incompatible changes between v19 and v21 that Vrui has not been updated to handle.
Question: which version of 20 do you recommend?
My initial recommendation for Linux Mint v20 was based solely on libdc1394-22-dev. But there may be other changes between v19 and v20 that would cause Vrui, Kinect, and SARndbox to not build.
As the latest recommended version is v19.3, stick to that version for now.
Also, from reading your post on the Linux Mint forum, the KeckCAVES Github page does not seem to be actively maintained. Your best bet for help is probably this forum.
My recommendation is to use Linux Mint v19 or v20. By using v21, some of the software needed by Vrui has been upgraded. This could work, but Vrui has not been tested with the newer versions.
To clarify, the Sourceforge address you shared is for the libdc1394 project. libdc1394-22-dev and libdc1394-25-dev are the Ubuntu packages made from the project code.
Another clarification: MATE is a GUI environment running on the Linux Mint distribution. Mint uses Ubuntu as a source for additional software packages. Having these distinctions in mind may help when researching software.
Wikipedia has good articles that can give you context for how these pieces (e.g. MATE, Mint, Ubuntu) mesh.
Make sure you are using -uhm with SARndbox to enable elevation color mapping.
You can also use SARndbox -h to see which file the sandbox will use for colors. Find “Default elevation color map file name” in the help output and verify the file shown on that line is located at the given path and that the file is readable (i.e. proper permisisons).
If the contour lines seem in the wrong places on the sand, then calibrate the sandbox, again, with CalibrateProjector.
Alguma dica?
Random calibration ideas:
- Use a CD or DVD as the target disc. A too big or too small disc will not work.
- Add a stiff wire or small stick to hold the target disc.
- Do not hold the disc itself, hold only the wire or stick. Leave a 2-3 cm gap between your fingers and the target disc edge.
- Keep the disc at least 2-3 cm from any box or sand wall.
- Keep the disc at least 2-3 cm above nearby sand.
- The yellow or green projected circle may not align with the target disc. This is not a problem.
- When the projected disc is green (no matter where projected), press the capture key.
- Clean the Kinect lenses with a soft cloth.
- The Kinect-to-sand distance should be close to 1 meter.
The list above contains generic advice, pictures from your calibration process might help find something else.
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.
