Complete Installation Instructions

Home Forums AR Sandbox Forum Complete Installation Instructions

This topic contains 101 replies, has 53 voices, and was last updated by  Alucard 1 week, 3 days ago.

Viewing 15 posts - 1 through 15 (of 102 total)
  • Author
    Posts
  • #100825

    Oliver Kreylos
    Moderator

    Note: Please don’t comment on this thread; it’s gotten unwieldy. If you have any questions, concerns, or problems, please start a new thread.

    Due to the currently surging interest in AR Sandbox installations, I am posting complete installation instructions, starting from a blank desktop PC with an Nvidia GeForce graphics card. Due to increasing weirdness in recent versions of Mac OS X (starting with 10.7), I can no longer recommend Mac computers and Mac OS X to drive AR Sandbox installations.

    You can also watch a full walk-through video of steps 1-5.

    1. Install the current version of 64-bit Linux Mint with MATE desktop on a blank desktop computer. This needs to be a real computer; the AR Sandbox does not work from inside a virtual machine.
    2. Install vendor-supplied drivers for the Nvidia graphics card. Open the Control Center, select “Driver Manager,” wait for the panel to show up and the list of available drivers to be populated, and then select the recommended Nvidia binary driver and press “Apply Changes.” Then wait until the change is complete (might take a while), and reboot your computer.
    3. Open a terminal window and enter precisely the following commands (if in doubt, cut & paste directly from this web page, one line at a time). ~ is shorthand for the user’s home directory:
      cd ~
      wget http://idav.ucdavis.edu/~okreylos/ResDev/Vrui/Build-Ubuntu.sh
      bash Build-Ubuntu.sh

      The script run in the last command will ask you for your user’s password to install prerequisite libraries, and then build the Vrui VR toolkit. That will take a little while and produce lots of output, and at the end you’ll be greeted by a spinning globe in a window. Close that window and go back to the same terminal as before.

    4. To install the Kinect 3D video package, run in the same terminal:
      cd ~/src
      wget http://idav.ucdavis.edu/~okreylos/ResDev/Kinect/Kinect-3.2.tar.gz
      tar xfz Kinect-3.2.tar.gz
      cd Kinect-3.2
      make
      sudo make install
      sudo make installudevrules
      ls /usr/local/bin

      Check that the list of names printed by the last command contains KinectUtil and RawKinectViewer.

    5. To install the AR Sandbox software itself, run in the same terminal:
      cd ~/src
      wget http://idav.ucdavis.edu/~okreylos/ResDev/SARndbox/SARndbox-2.3.tar.gz
      tar xfz SARndbox-2.3.tar.gz
      cd SARndbox-2.3
      make
      ls ./bin

      Check that the list of names printed by the last command contains CalibrateProjector and SARndbox. The AR Sandbox calibration utility and main application are now in ~/src/SARndbox-2.3/bin.

    6. Plug in your first-generation Kinect device and download intrinsic calibration parameters directly from its firmware. In a terminal window, run:
      sudo /usr/local/bin/KinectUtil getCalib 0

      This might ask you for your password again; if so, enter it to continue.

    7. Align your camera so that its field of view covers the interior of your sandbox. Use RawKinectViewer to guide you during alignment. To start it, run in a terminal window:
      cd ~/src/SARndbox-2.3
      RawKinectViewer -compress 0
    8. Calculate your sandbox’s base plane, by following the instructions in the AR Sandbox Calibration – Step 4 video, or this new video that shows all required calibration steps in one. You can use the already-running instance of RawKinectViewer.
      You need to enter the base plane equation (and the 3D sand surface extents in the next step) into the BoxLayout.txt file in etc/SARndbox-<version> inside the SARndbox source directory. Under Linux Mint, the default text editor is called “pluma.” So to edit the file, run in a terminal window:

      cd ~/src/SARndbox-2.3
      pluma etc/SARndbox-2.3/BoxLayout.txt &

      The ampersand at the end of the second command will keep the terminal window usable while the text editor is running. Now enter the base plane equation as described in the video. To copy text from a terminal window, highlight the desired text with the mouse, and then either right-click into the terminal window and select “Copy” from the pop-up menu that appears, or press Shift-Ctrl-c. To paste into the text editor, use the “Edit” menu, or press Ctrl-v.

      Pro tip: The quickest way to copy&paste text from any window into any other window is: 1: Highlight text in source window with the mouse. 2: Move mouse to destination window and to the location where you want to paste the text, and click the middle mouse button.

    9. Measure the 3D extents of the sand surface. In the newly-released Kinect-3.2 package, this can be done inside RawKinectViewer as well by following the instructions in this video, starting at 4:10. Make sure to measure the box corners in the order lower-left, lower-right, upper-left, upper-right. After you have copied the box corner positions into the text editor as described in the video, save the file (via the “File” menu or by pressing Ctrl-s), and quit from the text editor (via the “File” menu or by pressing Ctrl-q).
    10. Align your projector such that its image fills the interior of your sandbox. You can use the calibration grid drawn by Vrui’s XBackground utility as a guide. In a terminal, run:
      XBackground

      After the window showing the calibration grid appears, press the “f” key to toggle it into full-screen mode. Ensure that the window really covers the entire screen, i.e., that there are no title bar, desktop panel, or other decorations left.

      Press Esc to close XBackground’s window when you’re done.

    11. Calibrate the Kinect camera and the projector with respect to each other by running the CalibrateProjector utility:
      cd ~/src/SARndbox-2.3
      ./bin/CalibrateProjector -s <width> <height>

      where <width> <height> are the width and height of your projector’s image in pixels. For example, for an XGA projector like the recommended BenQ, the command would be:

      ./bin/CalibrateProjector -s 1024 768

      Very important: switch CalibrateProjector’s window to full-screen mode by pressing F11 before proceeding. Then follow the instructions in this video, starting at 10:10.

    12. Finally, run the main AR Sandbox application:
      cd ~/src/SARndbox-2.3
      ./bin/SARndbox -uhm -fpv

      Switch SARndbox’s window to full-screen mode by pressing F11, or the calibration created in the previous step will not line up.

    13. Read the “AR Sandbox post-installation setup” post for some additional automation and fine-tuning suggestions.
    • This topic was modified 2 years, 7 months ago by  Oliver Kreylos.
    • This topic was modified 2 years, 7 months ago by  Oliver Kreylos.
    • This topic was modified 2 years, 7 months ago by  Oliver Kreylos.
    • This topic was modified 2 years ago by  Oliver Kreylos.
    • This topic was modified 1 year, 11 months ago by  Oliver Kreylos.
    • This topic was modified 1 year ago by  mbyikilmaz.
    • This topic was modified 1 year ago by  mbyikilmaz.
    • This topic was modified 1 year ago by  mbyikilmaz.
    • This topic was modified 1 year ago by  Oliver Kreylos.
    • This topic was modified 1 year ago by  Oliver Kreylos.
    • This topic was modified 1 year ago by  Oliver Kreylos.
    • This topic was modified 12 months ago by  Oliver Kreylos. Reason: Broke software installation into several steps; added error checks
    • This topic was modified 12 months ago by  Oliver Kreylos. Reason: Added full path for sudo KinectUtil
    • This topic was modified 11 months, 2 weeks ago by  Oliver Kreylos. Reason: Removed item to assign full-screen shortcut key; no longer required with Vrui-4.2
    • This topic was modified 11 months, 2 weeks ago by  Oliver Kreylos. Reason: Added link to post-installation setup post
    #100856

    kwikstrom
    Participant

    Any chance at a walk through video clip? Several errors occur as early as step 2 and would like to see how others, or you, are doing it? And will this work in Oracle VM VirtualBox?

    • This reply was modified 2 years, 8 months ago by  kwikstrom.
    #100858

    kwikstrom
    Participant

    After thinking, the next question I would like to ask (probably a better one too) is: What’s the best avenue towards a working AR Sandbox if starting from a Windows 8.1 OS?

    #100861

    Oliver Kreylos
    Moderator

    What errors are you getting in step 2? Most importantly, are you doing step 2 from inside a virtual machine?

    The AR Sandbox does not in general work from inside a virtual machine, as those normally don’t get access to accelerated graphics hardware, which is crucial for running the AR Sandbox. I don’t know enough about Oracle VM VirtualBox to say whether it does or does not.

    #100863

    Oliver Kreylos
    Moderator

    The AR Sandbox software, or, rather, the underlying Vrui VR toolkit, does not run under Windows.

    #100866

    kwikstrom
    Participant

    Yes, from inside a Virtual Machine. The problem I was having was under Software Sources > Additional Drivers did not detect NVIDIA. But since the VM isn’t accessing the graphics hardware this makes sense.

    I did go further in one of my attempts and when installing the Vrui toolkit I received errors that “libcheese”s and “libclutter”s had unmet dependencies. I did somehow manage a work around or a way to meet those requirements.

    An issue I had later with the Kinect was it was not being detected when I ran commands such as “lsusb” even when I attempted to pass it through the VM. Sometimes a USB thumb drive would make it through, but not always. Again, all of this is likely stemming from being run in a VM, which doesn’t work as you said. Too bad too, we’d hoped to demo the sandbox at a fair soon. We really appreciate that you placed instructions online for us all.

    #100872

    CanisiusPhysics
    Participant

    Could you elaborate more on how you fixed those dependency issues? I am getting the same on a brand-new Ubu install.

    #100875

    kwikstrom
    Participant

    I attempted this so many times that I cannot remember for certain which methods worked. But if I am remembering correctly, once I downloaded “aptitude” and ran that instead of “apt”, and on a separate attempt I downloaded the utopic versions (prior versions I think). If I can remember positively I will post more here for you.

    #100876

    GregWirth
    Participant

    Maybe lock this install thread, and place the questions elsewhere?

    #100877

    kwikstrom
    Participant

    In dual boot?

    #100881

    spacecadet
    Participant

    I too ran into problems with step 4 above.
    After executing: “bash Build-Ubuntu.sh”, I got the following:

    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    Note, selecting ‘libpng12-dev’ instead of ‘libpng-dev’
    Note, selecting ‘libtiff5-dev’ instead of ‘libtiff-dev’
    Some packages could not be installed. This may mean that you have
    requested an impossible situation or if you are using the unstable
    distribution that some required packages have not yet been created
    or been moved out of Incoming.
    The following information may help resolve the situation:

    The following packages have unmet dependencies:
    libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not going to be installed
    Depends: libcogl15 (>= 1.15.8) but it is not going to be installed
    libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going to be installed
    Depends: gstreamer1.0-clutter but it is not going to be installed
    libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going to be installed
    Depends: libcogl15 (>= 1.15.8) but it is not going to be installed
    E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
    Problem while downloading prerequisite packages; please fix the issue and try again

    Did I miss an obvious step?
    I’d appreciate any specific suggestions you can give.

    THanks.

    #100886

    Oliver Kreylos
    Moderator

    What version of Ubuntu was this?

    #100887

    Oliver Kreylos
    Moderator

    Dual boot works fine. As long as Linux runs on the real hardware, it’s OK.

    #100888

    Oliver Kreylos
    Moderator

    Which version of Ubuntu was this?

    #100889

    CanisiusPhysics
    Participant

    I am running into the same problem when installing in a fresh Ubu 14.04 install. I ran apt-get install individually for each of the prerequisite packages. I got hung up on the last 2 (libgl1-mesa-dev and libglu1-mesa-dev). When I locate and install the appropriate .deb files, I get the error that the unresolved dependency is because of mesa-common-dev. However, that package is already installed.

    No time now to look further, but may have time later today (teaching would be so much better without all those pesky students).

Viewing 15 posts - 1 through 15 (of 102 total)

You must be logged in to reply to this topic.