Forum Replies Created
-
Posts
-
…so i need to search for the rain…
Have you read “No rain under my hand”?
Congratulations! Now the fun of construction and calibration can begin?
I assume that when @okreylos moves to LM21 the missing include could be added to Vrui for the next release. I don’t think this would cause
backward-compatible problems.Changing the libdc1390-dev package name will probably be part of an update to Build-Ubuntu.sh when Ubuntu 22.04 LTS and LM21 become recommended distributions. Until that time, the current package name is proper for LM19.
Missing 1 line of code?
I misread the error and the Linux Mint forum poster is right, the cstddef header is not included in FrameRateViewer.h.
I have been able to build Vrui (and the full AR Sandbox software) in a LM21 virtual machine with two changes. First, the version number has been removed from the libdc1390-dev package. Edit Build-Ubuntu.sh to change libdc1390-22-dev to libdc1390-dev.
Second, FrameRateViewer.h needs to be patched before building. Add a new line to Build-Ubuntu.sh before “make -j$NUM_CPUS INSTALLDIR=$VRUI_INSTALLDIR” (line 65). The added line should contain “patch -p1 < ../../Fix-missing-size_t.patch”.
Create a new text file in the same directory as Build-Ubuntu.sh. This file should be named Fix-missing-size_t.patch and contain the following text.
--- a/Vrui/Vislets/FrameRateViewer.h 2019-07-17 13:48:41.000000000 -0700 +++ b/Vrui/Vislets/FrameRateViewer.h 2022-08-24 09:05:57.472284693 -0700 @@ -27,6 +27,8 @@ #include <GL/GLNumberRenderer.h> #include <Vrui/Vislet.h> +#include <cstddef> + namespace Vrui { namespace Vislets {Remove the old src directory (if still around) and run the new Build-Ubuntu.sh. Let me know if this works or not.
There will be copies of configuration files with default values in the directories where you built the sandbox. Or in the tar.gz files downloaded to start the build process.
If neither of these work, please give more details about which files you want to reset.
…we are using PC Dr Oliver mentioned…
I’m a bit confused. Do you have an “HP Victus” (as you mentioned above) or an “HP Pavillion” (Oliver’s new purchase)? If a Victus, is it a desktop computer or a laptop?
Thank you for posting the links to your Linux Mate threads, they filled in many details.
The short version: 19.3 & 20.1 can not see hard drive in this PC.
I see several discussions about changing the hard drive interface in BIOS to fix the missing drive on Ubuntu, et al. The following thread has one of the more explicit fixes and explanations.
https://ubuntu-mate.community/t/cant-see-nvme-m-2-drive-for-fresh-install/18463
Missing 1 line of code?
The cstddef header is included in iostream, which is included in FrameRateViewer.h. The include chain should bring in the size_t type. I built Vrui with g++ 11.2 (same version used in LM21) without that error.
Another possible avenue with your local Linux Mint expert: use a fresh, clean LM21 and try to manually build Vrui, etc. The “Unable to locate package libdc1394-22-dev” is specific to using Build-Ubuntu.sh. Or edit Build-Ubuntu.sh to install libdc1394-25-dev instead.
Is Artie your nickname?
Artie the Artichoke is our school’s mascot.
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.
