Forum Replies Created

Viewing 15 posts - 451 through 465 (of 522 total)
  • Author
    Posts
  • in reply to: KinectUtil not finding my Kinect #100865
    Oliver Kreylos
    Keymaster

    Glad it wasn’t anything serious.

    in reply to: Problem about not smooth video #100864
    Oliver Kreylos
    Keymaster

    At what exact point are you getting a segmentation fault when running ShowEarthModel?

    in reply to: Complete Installation Instructions #100863
    Oliver Kreylos
    Keymaster

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

    in reply to: Complete Installation Instructions #100861
    Oliver Kreylos
    Keymaster

    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.

    in reply to: Feature wish list #100860
    Oliver Kreylos
    Keymaster

    I might already be working on DEM overlays. There will be a mode where the sand is color-coded based on vertical distance to a pre-loaded DEM, so that the sandbox guides the user towards recreating that DEM. Once the sand surface is close enough, it becomes possible to project other information, such as aerial photography, onto the sand without deformation.

    in reply to: KinectUtil not finding my Kinect #100859
    Oliver Kreylos
    Keymaster

    When you plug in your Kinect, lsusb should display the following new devices:

    Bus 003 Device 005: ID 045e:02ad Microsoft Corp. Xbox NUI Audio
    Bus 003 Device 006: ID 045e:02ae Microsoft Corp. Xbox NUI Camera
    Bus 003 Device 004: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor

    Xbox NUI Camera is the actual camera (that’s the device KinectUtil tries to open), Xbox NUI Audio is the built-in microphone array, and Xbox NUI Motor is the little motor that can tilt the Kinect up or down.

    If you’re only seeing the Xbox NUI Motor device, then either your Kinect is broken, or there is something wrong with the cable connecting it to your computer, or with your computer’s USB ports. Can you confirm that you are not seeing the Xbox NUI Camera device?

    You can also try plugging the Kinect into different USB ports on your computer and see if that makes a difference. As USB devices go, the Kinect is relatively demanding, and often shows flaws in a USB system that otherwise go unnoticed.

    in reply to: how to autostart on power up #100853
    Oliver Kreylos
    Keymaster

    OK, here is the explanation from my colleague Burak Yikilmaz, who set up the AR Sandbox computers for our affiliated institutions:

    The user auto-logs into a special sandbox session (which resides
    under /usr/share/xsessions) where I use matchbox window manager with
    restrictions like no cursor and titlebar. The session automatically
    executes a script that starts and sets the window manager options and
    runs the RunSandbox script which checks/waits whether/until the kinect
    is connected. There is also an auto-start script which sets the sandbox
    session as the default session. This is helpful in case you log into
    gnome session for admin work. By default, the computer auto-logs into
    the last session after a restart. That script prevents that and lets the
    computer automatically go into the sandbox session.

    Until we write up detailed instructions, the basic idea is that you create a new user account with minimal privileges (no administrative rights), and set up the login manager to auto-login that user on boot.

    To set it up further, you log in as that user normally, and then create a script file to run the sandbox application with the desired command line options, and then add that script to the auto-user’s autostart list.

    This will roughly do it; the rest is fine-tuning. It should not be necessary to run a special window manager as Burak describes; using the Vrui configuration file(s), the SARndbox can be set up to start in fullscreen mode, without window borders and cursor images, automatically.

    in reply to: Problem about not smooth video #100849
    Oliver Kreylos
    Keymaster

    We’ve been running into this problem with the Mesa OpenGL library, which is used to drive (some?) AMD/ATI graphics cards, and Intel’s integrated HD xxxx GPUs). I have not been able to replicate the problem as I don’t have access to any of those GPUs, and I don’t have an idea what could be causing it.

    Could you do me a favor and update to the newest versions of the software (Vrui-3.1-002, Kinect-2.8-001, and SARndbox-1.5-001) and see whether the problem persists? Vrui is available via the regular download site, and I have links to the new Kinect and SARndbox packages in this thread. There are also updated detailed instructions in this thread.

    in reply to: Projector Calibration Question #100848
    Oliver Kreylos
    Keymaster

    Especially the contour lines will be much crisper if you run the projector at its native resolution. Upscaling from 1024×768 to 1440×1080 introduces some aliasing because it’s a non-integer ratio.

    If you could generate a video signal of 1440×1080 from your graphics card it would be the best of both worlds, as you’ll get a 4:3 aspect ratio and native pixel resolution.

    in reply to: Kindect height and rain issues #100847
    Oliver Kreylos
    Keymaster

    I think I see the problem. Your Kinect uses millimeters as measurement units, and the sandbox by default expects centimeters. In that case the default elevation ranges won’t work, because they’ll translate to only a few dozen millimeters each way.

    The sandbox can be configured to use millimeters, but you’ll have to override a lot of default settings.

    As it so happens, I just uploaded new versions of the Kinect and SARndbox packages (find locations in this thread), and the new Kinect package has a KinectUtil that converts mm-based calibrations to cm-based ones. I suggest re-installing the new versions of the Kinect and SARndbox packages, run “KinectUtil getCalib 0” again, and redo calibration steps 4, 5, and 7.

    The other benefit is that the new Kinect package also has a new tool to simplify measuring 3D surface positions. I think your second problem is that the points you measured in KinectViewer weren’t directly on the surface. It’s counter-intuitive because KinectViewer allows you to measure anywhere in 3D space. Check out the complete installation instructions thread, and look at the instruction video segments for calibration steps 4 (baseplane) and 5 (box extents). You can use the same method as for step 5 to get the true elevation range of your sandbox.

    in reply to: Kindect height and rain issues #100843
    Oliver Kreylos
    Keymaster

    Once you have the min/max elevation range for surfaces (which you can pass to SARndbox via the -er <min> <max> command line option), you can then set the rain layer above the valid surface layer, leaving maybe a few cm gap, via the -rer <min> <max> (for “rain elevation range”) command line option.

    in reply to: Kinect Viewer freezes #100841
    Oliver Kreylos
    Keymaster

    Can you please post the output of

    glxinfo | grep vendor

    in reply to: Projector Calibration Question #100840
    Oliver Kreylos
    Keymaster

    Forgot to mention: Always run your projector at native resolution (1920×1080), and pass that resolution to CalibrateProjector when you’re calibrating.

    Also make sure that your projector is using the full 1920×1080 frame. By default many don’t, to account for view borders in broadcast HD. Use the test pattern displayed by XBackground (part of Vrui package), and ensure that you see the white lines around the borders, and the full circles in the corners. There is usually a “show pixels 1:1” or some similar item in the projector menu somewhere.

    in reply to: Projector Calibration Question #100839
    Oliver Kreylos
    Keymaster

    Do you have a set of pictures showing how the red crosshairs track your calibration target in CalibrateProjector, and then how features don’t line up later in SARndbox?

    in reply to: Kindect height and rain issues #100838
    Oliver Kreylos
    Keymaster

    The first thing you want to do is set up an appropriate base plane equation by running calibration step 4. All elevation values used by the AR Sandbox are relative to this base plane. Say your Kinect is 50″ above the flat sand surface, then the offset value of your base plane should be about -127 (cm).

    If you want to adjust elevation ranges (surface min/max and rain layer min/max) based on your local setup, you can use KinectViewer to measure the 3D coordinates of arbitrary points on the surface, just as you did for the box corners in calibration step 5. Those values will be in camera space, i.e., to convert them to base-plane relative elevation space, you need to subtract the base plane offset. Say you measure the top of a high mountain at (30, -20, -86), i.e., at a z position of -86 relative to the camera, then that point’s elevation above the base plane is -86-(-127)=41 (cm). That would then be the number to use for max elevation, and so forth.

    If you download the new Kinect-2.8-001 and SARndbox-1.5-001 packages (see Two minor software updates), you can take these measurements more easily directly inside RawKinectViewer. See the new calibration video linked in the complete installation instructions.

Viewing 15 posts - 451 through 465 (of 522 total)