Forum Replies Created

Viewing 15 posts - 331 through 345 (of 448 total)
  • Author
    Posts
  • in reply to: SARndbox User Guide? #101145

    Oliver Kreylos
    Keymaster

    We don’t have a guide for running the AR Sandbox (yet).

    To your question: That should work. To enable the button in the software, start the AR Sandbox as usual, and then press and hold some key, say “9”. This will pop up a tool selection menu. Move the mouse to select “Manage Water” from the bottom, and let go of the key you pressed. This will bring up a dialog window asking you to press another button to assign to the “Drain” function. Now press the USB button, and the dialog window will go away.

    Now, if you press and hold “9”, or whatever key you picked, it will rain, and if you press and hold the USB button, the water will drain.

    To make the assignment permanent, press the right mouse button to bring up the main menu, move down to “Vrui System,” then to “Devices,” and finally select “Save Input Graph…”. This will suggest a file name; take note of the file name and location, and select “OK” to save.

    To load the new input graph on startup, run the sandbox as

    $<SARndbox location>/SARndbox [usual command line arguments] -loadInputGraph <location>/<file name>
    

    You can keep the original file name, or rename the file and move it to a convenient location.

    in reply to: Issues and errors #101144

    Oliver Kreylos
    Keymaster

    The error means that the projector calibration matrix that’s created as part of final calibration doesn’t exist yet (I assume you haven’t run that step yet). You can run the sandbox without, but you have to leave off the -fpv command line argument. In that mode, the topography is drawn as a regular 3D surface, and you can use mouse and keyboard to rotate, translate, and scale it. See the Vrui Application User Guide for details.

    Did you install Linux Mint according to the instruction video, i.e., using Mate as a desktop environment? Then the fullscreen shortcut should be there.

    If you installed another desktop environment, it might not be. In that case, you can force the sandbox to start in fullscreen mode by creating a new file Vrui.cfg inside the /home/ardadmin/src/SARndbox-1.5-001/ directory, with the following (exact) contents:

    section Vrui
      section Desktop
        section Window
          windowFullscreen true
        endsection
      endsection
    endsection
    

    If you then run the sandbox as follows:

    $ cd /home/ardadmin/src/SARndbox-1.5-001
    $ ./bin/SARndbox
    

    (adding the usual command line parameters), it will start in fullscreen.

    in reply to: Compatibility with Kinect for Windows v2? #101143

    Oliver Kreylos
    Keymaster

    It’s going to be a while, but you can still order new Kinect-for-Xbox-360 devices, for example via Amazon.

    in reply to: Modification of the current software #101081

    Oliver Kreylos
    Keymaster

    This is trickier than it appears because water data only lives on the graphics card, not in CPU-accessible main memory where you would need it to run simulations. You can download the current water state grid after it’s being updated in the display method, which is line 934 in Sandbox.cpp. Use WaterTable2::bindQuantityTexture to bind the water texture to the active texture unit, and then use glGetTexImage with a texture target of GL_TEXTURE_RECTANGLE_ARB, an RGB format, and a floating-point data type. The first texture component will be water surface level (not water height above ground), and the second and third are horizontal and vertical flux.

    in reply to: UML and modification #101080

    Oliver Kreylos
    Keymaster

    No, there is no formal specification for the AR Sandbox code, or a Doxygen-like class tree. Fortunately, the number of classes/modules in the Sandbox code itself is rather small. You can see how the depth data processing pipeline is set up in the Sandbox::Sandbox constructor: one FrameFilter for surface processing, a SurfaceRenderer to draw the surface including contour lines, a RainMaker plus another FrameFilter to detect “rain clouds,” and a WaterTable2 for water simulation. Data is passed between these objects via callback functions set up in the Sandbox constructor.

    in reply to: Hardware requirements #101078

    Oliver Kreylos
    Keymaster

    Old for-Xbox Kinects do not have a standard USB plug; they require the power adapter cable not only to draw power, but also to convert the plug to standard USB. You will need to check carefully what’s in the box. From day one, Kinect-for-Xbox devices sold in stores always had the power cable / USB adapter in the box.

    in reply to: Depth Issue / Sea Level at Base Line #101077

    Oliver Kreylos
    Keymaster

    If you followed the installation instructions, your BoxLayout.txt file will be in ~/src/SARndbox-1.5-001/etc/SARndbox-1.5/

    After editing the file, restarting the SARndbox application will read the changes.

    Did you resolve your issue?

    in reply to: VRUI – No spinning globe? #101076

    Oliver Kreylos
    Keymaster

    When you run the following in a terminal window:

    ~/Vrui-3.1/bin/ShowEarthModel

    what is the response in the terminal window?

    in reply to: Gigabyte BRIX #101075

    Oliver Kreylos
    Keymaster

    When you run the following from a terminal window:

    ~/Vrui-3.1/bin/ShowEarthModel

    what response do you get in the terminal window?

    in reply to: VRUI Menu To Small to read #101074

    Oliver Kreylos
    Keymaster

    The underlying issue is that your monitor/projector thinks it’s very large. Vrui bases everything on real-world measurements (i.e., fonts are configured to be 11pt by default), but if the graphics system misdetects your monitor, things will go astray. Run this from a terminal window:

    xdpyinfo | grep dimensions

    which will tell you how big the graphics system thinks your screen/projection image is (in mm).

    The ideal solution would be to set your display’s size to reality, but requires rooting around in system files. It’s easier either to 1) tell Vrui directly how big your screen is, or 2) exaggerate the font size Vrui uses.

    2) is easier: open Vrui.cfg in a text editor:

    gedit ~/Vrui-3.1/etc/Vrui.cfg

    go to line 58, and adjust the value of uiFontTextHeight to your liking. Once you found your favorite value, set uiSize (in line 52) to half that value, and uiSliderWidth (line 60) to the sum of uiSize and uiFontTextHeight.

    1) Open Vrui.cfg as above, and change autoScreenSize in line 146 to false, then go to lines 107 and 109 and set the actual width and height of your screen in inches. Adjust origin in line 105 accordingly.

    in reply to: Depth Frame Buffer/ Response time #101028

    Oliver Kreylos
    Keymaster

    Processor performance has little to do with it. The Kinect delivers depth frames at a fixed rate of 30 Hz, and the software uses a 30-tap smoothing and outlier removal filter to stabilize the reconstructed topography, leading to exactly 1s of latency between user action and graphics update.

    You can select an arbitrary size for the smoothing buffer via the -nas (“number of averaging slots”) command line option:

    -nas <filter size>

    If you reduce filter size below 10, you also need to adjust the stability parameters via

    -sp <min num samples> <max variance>

    You should set those two values to 1 and 10, respectively.

    With the minimum filter size of 1, the AR Sandbox response time will be around 1/30s, but the topography will be very noisy, and any body parts, tools, or other objects above the sand surface will be integrated into the surface.

    in reply to: Portable Sandbox for High School #101027

    Oliver Kreylos
    Keymaster

    Our AR Sandbox prototype, as shown on my web site, fits tightly through a standard door, with the projector/camera arm removed.

    Whenever you remove/reattach the projector/camera arm, you have to re-aim the projector and camera (unless you have a mechanical means to ensure that both end up exactly the same as before), and re-run the full calibration procedure (4: measuring base plane, 5: measuring box extents, 7: projector calibration). With a bit of practice you can probably do that in five minutes, but it needs to be done.

    We currently recommend the BenQ MX620 short-throw projector. Street price is around $530.

    in reply to: Where does the BoxLayout.txt go? #100990

    Oliver Kreylos
    Keymaster

    Check that the contents of your BoxLayout.txt file follow this format (with different numbers, of course). Most of the spaces are optional, but the parentheses and commas are required exactly as shown:

    
    (-0.0245965, 0.055518, 0.998155), -100.0
    (  -50.4308199070,   -41.4906340820,   -94.3587439431)
    (   48.1677580484,   -39.2855623569,   -91.4473216116)
    (  -52.0412743633,    30.7509568892,   -98.5064610284)
    (   45.7546216497,    32.6590139228,   -95.6029096114)
    
    in reply to: Complete Installation Instructions #100989

    Oliver Kreylos
    Keymaster

    RawKinectViewer, KinectViewer, and CalibrateProjector all worked fine?

    Please run the sandbox as

    SARndbox -fpv -ws 0.0 0

    to temporarily disable water simulation and see if that works.

    in reply to: Complete Installation Instructions #100988

    Oliver Kreylos
    Keymaster

    Strange. Did you install the binary Nvidia driver via “Driver Manager,” as in step 2 and shown in the video?

    Also, please post the output of the following command:

    
    find /usr/lib* -name "libGL*"
    
Viewing 15 posts - 331 through 345 (of 448 total)