Forum Replies Created

Viewing 15 posts - 16 through 30 (of 403 total)
  • Author
    Posts
  • in reply to: Errors in Per-Pixel Depth Correction #115711

    Oliver Kreylos
    Moderator

    There are two separate calibration steps: per-pixel depth correction and full intrinsic calibration (which uses semi-transparent checkerboards).

    I advise against doing the second step. It’s not particularly useful for the AR Sandbox.

    The first step can be a big help in getting good feature alignment in the sandbox, as it takes out a non-linear distortion component. It’s described in the Kinect package’s README file and pretty straightforward. You have to point your Kinect at a flat surface, like a wall, from a few different distances and take a picture each time.

    in reply to: Recalibrating the Projector and Kinect #115665

    Oliver Kreylos
    Moderator

    Don’t forget to replace “<username>” with your actual user name.

    in reply to: Kinect Camera #115663

    Oliver Kreylos
    Moderator

    It’s getting harder, but they’re out there. The exact model numbers don’t matter. If it’s black, has a trapezoid shape, three lenses along the front, and is standing on a small foot, it’s a Kinect-for-Xbox-360 and will work well. If it’s a black rectangular brick with a single lens at the very left sitting on a very wide foot, it’s a Kinect-for-Xbox-One and will not work so well.

    in reply to: Recalibrating the Projector and Kinect #115655

    Oliver Kreylos
    Moderator

    This does not affect any of the installation steps. You can re-calibrate any time. If you end up doing it a lot, you should create another desktop icon for CalibrateProjector. Follow the instructions for the SARndbox icon.

    in reply to: Joystick as tracking device? #115654

    Oliver Kreylos
    Moderator

    Yes, there is a built-in way. You should have a SpaceTraveler.cfg configuration file in /usr/local/etc/Vrui-4.5. It maps several levels of functionality to a six-axis spaceball device. The relevant bit is the SixAxisTransformTool definition. This tool class creates a virtual input device (a cursor) that can be moved by pushing three analog axes. You can bind that tool to three axes on your controller (you’d only be using two of those in the end), and a set of buttons to trigger actions at the cursor’s current position.

    in reply to: Joystick as tracking device? #115647

    Oliver Kreylos
    Moderator

    Re: controller That doesn’t seem to be a Bluetooth controller, but a regular wireless one with a custom dongle. Those show up as USB devices. Setting those up usually involves a bit of detective work. You need to check that the controller is recognized at the USB level. Plug it in and check the output of lsusb for something that looks like the controller, then note down its vendor and product IDs.

    Second, you need to open access to the device for non-admin users. This is done via scripts in /etc/udev/rules.d . There should already be a 69-Vrui-devices.rules in there, open it in a text editor (via sudo). Then insert a line like this:

    ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c625", TAG+="uaccess"

    but replace the vendor and product IDs with your device’s. Then unplug the wireless dongle and plug it back in.

    Then create a patch configuration file like “Controller.cfg” with contents similar to the following:

    section Vrui
    	
    	section Desktop
    		inputDeviceAdapterNames += (HIDAdapter)
    		
    		section HIDAdapter
    			inputDeviceAdapterType HID
    			inputDeviceNames (SteelSeriesStratusXL)
    			
    			section SteelSeriesStratusXL
    				name SteelSeriesStratusXL
    				deviceVendorProductId 0111:1419
    				trackingDeviceName Mouse
    				trackingDeviceType Ray
    				axis0Settings (-2047, 0, 0,  2047)
    				axis1Settings ( 2047, 0, 0, -2047)
    				axis2Settings (-2047, 0, 0,  2047)
    				axis3Settings ( 2047, 0, 0, -2047)
    				axis4Settings (-4095, 0, 0,  4095)
    				axis5Settings (-4095, 0, 0,  4095)
    				buttonNames (Back, Home, A, B, X, Y, L1, R1, Forward, LStick, RStick)
    				valuatorNames (LStickX, LStickY, RStickX, RStickY, R2, L2, DPadX, DPadY)
    			endsection
    		endsection
    	endsection
    	
    endsection

    adapting settings to your controller. You can store the configuration file in /usr/local/etc/Vrui-4.5. Then load it via the command line:

    ./bin/SARndbox ... -mergeConfig Controller

    and you should be able to bind tools to the controller’s buttons.

    in reply to: SandBox Registration #115646

    Oliver Kreylos
    Moderator

    It gets updated every two weeks, usually.

    in reply to: Recalibrating the Projector and Kinect #115644

    Oliver Kreylos
    Moderator

    You might be in the wrong place. Run this in a terminal:

    cd ~/src/SARndbox-2.4
    ./bin/CalibrateProjector -s 1024 768
    in reply to: SandBox Registration #115634

    Oliver Kreylos
    Moderator
    in reply to: Projector #115631

    Oliver Kreylos
    Moderator

    If you already have a projector, and it’s working for you, there’s no need to change.


    Oliver Kreylos
    Moderator

    That happens when you accidentally build the SARndbox package with

    make INSTALLDIR=

    or if you accidentally changed the makefile line

    INSTALLDIR := $(PWD)

    to

    INSTALLDIR :=

    or removed that line completely.

    As this will cause you problems later, I recommend checking that the makefile is correct, and re-building the package exactly as in the instructions:

    cd ~/src/SARndbox-2.4
    make

    You can check the result by looking into Config.h. It should contain the line

    #define CONFIG_CONFIGDIR "/home/<username>/src/SARndbox-2.4/etc/SARndbox-2.4"

    where you previously had

    #define CONFIG_CONFIGDIR "/etc/SARndbox-2.4"

    in reply to: Staggered cloud(s) and no rain #115626

    Oliver Kreylos
    Moderator

    If your projector image fills the box, but the topo display is smaller, you have one of two problems:

    1) The Kinect camera doesn’t see the entire interior of the box. The topography is only reconstructed where the Kinect can see it.

    2) Something went wrong during projector calibration. Pass the correct pixel size of your projector to CalibrateProjector (./bin/Calibrateprojector -s <width> <height>) , and ensure that its display window is full-screen. Do the same when running SARndbox.

    in reply to: Extracting DEM and save it as STL or OBJ file #115625

    Oliver Kreylos
    Moderator

    DEMs can be saved by binding a “Save Bathymetry” tool. When the associated key/button is pressed, the current surface will be written in USGS DEM format.

    in reply to: No detection of the hand for rain #115624

    Oliver Kreylos
    Moderator

    Are you making the “rain gesture” — hand flat, palm down, all five fingers spread?

    in reply to: No rain #115623

    Oliver Kreylos
    Moderator

    Can you create a global water tool and flood the sandbox, or does that not work either?

    Are you getting any error messages when running ./bin/SARndbox?

    What is the output from

    glxinfo | grep vendor

    The jitter in contour lines is due to noise from the Kinect camera. You can reduce jitter by adding a hysteresis envelope: add -he 1.5 to the command line, and adjust the number up or down until the contour lines just stop jittering.

Viewing 15 posts - 16 through 30 (of 403 total)