Forum Replies Created

Viewing 15 posts - 331 through 345 (of 435 total)
  • Author
    Posts
  • 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*"
    
    in reply to: Complete Installation Instructions #100987

    Oliver Kreylos
    Keymaster

    Most probably a driver problem. Use the “Additional Drivers” control panel to install the binary Nvidia driver, and that should fix it.

    in reply to: GL Error and No water formation #100986

    Oliver Kreylos
    Keymaster

    If your Iris Pro ran water simulation under Mac OS X, but not under Ubuntu, then this is something I have to fix in my code. The Linux Intel driver is “special” in how it handles framebuffers, and I never put dedicated Intel support into my code because I expected it wouldn’t work anyway. I’ll see if this is something I can add easily.

    in reply to: GL Error and No water formation #100985

    Oliver Kreylos
    Keymaster

    You are probably running the open-source “radeon” driver. There is an alternative driver directly from AMD called “fglrx.” That one should work. You should be able to find installation instructions online. I don’t use AMD cards myself, so I can’t help directly.

    in reply to: What is the scale on AR sandbox? #100984

    Oliver Kreylos
    Keymaster

    Could be a couple of different things; I’d have to see a picture.

    in reply to: What is the scale on AR sandbox? #100983

    Oliver Kreylos
    Keymaster

    By default, the AR Sandbox display scale is 1:100 (if your Kinect returns measurements in cm). The only component that’s affected by scale is the water simulation; water behaves differently at different scales. The rest of the display is scale invariant.

    You can set the distance between contour lines via the -cls <distance> command line parameter to SARndbox (“contour line distance”). The default is 0.75cm, which corresponds to 0.75m at the default 1:100 scale. To see the full list of command line parameters, run SARndbox -h.

    in reply to: Freeze Problem #100982

    Oliver Kreylos
    Keymaster

    Does the AR Sandbox freeze completely, or does it just no longer receive data from the Kinect?

    To test, once it freezes, move the mouse (doesn’t matter that the cursor is invisible), and see if you get updates again. If you don’t, or you can’t tell, press the right mouse button to bring up the program’s main menu. Does it show up, and can you interact with the menu?

    If yes, then the Kinect is frozen. This could be a nasty problem, as there is no easy and reliable way to wake it up again. If you close the SARndbox application (by pressing Esc) and rerun it, does it work again? If not, does it work if you stop the app, unplug the Kinect, plug it back in, and rerun the app? Does it work if you run KinectUtil reset all instead of unplugging/plugging the Kinect?

    If you set updateContinuously back to false, does the sandbox freeze earlier? In general, using that setting is only a short-term workaround, as it will waste a lot of power and can potentially overheat the computer.

    in reply to: Problem with sandbox's size #100957

    Oliver Kreylos
    Keymaster

    Please check the base plane equation in BoxLayout.txt (first line). The last number in that line corresponds to the vertical position of the zero-elevation plane relative to the camera. If your camera is approx. 2m above the sand, that number should be around -200.

    in reply to: Raw Kinect Viewer Question #100956

    Oliver Kreylos
    Keymaster

    Press and hold z and move the mouse to pan.

    For an introduction to Vrui’s user interface, please see the “Using Vrui Applications” document in the included documentation (online version here).

    in reply to: Killing the X-Server – Not working #100950

    Oliver Kreylos
    Keymaster

    I just did another from-scratch install, this time Linux Mint 17.1 MATE, and it also went through without a hitch. I’m sorry that you had such issues on your side.

    in reply to: Killing the X-Server – Not working #100949

    Oliver Kreylos
    Keymaster

    I just did a from-scratch Ubuntu 14.04 install for a video to accompany the complete instructions, and it went all the way through with one minor hitch (full-screen toggle).

    When I went to the “additional drivers” panel, it was initially empty, but then filled up with the list of Nvidia drivers after about a minute. From there I just clicked on the first choice, pressed apply, and was off to the races.

    in reply to: Alternate Download location #100946

    Oliver Kreylos
    Keymaster

    Web server is back up.

    in reply to: GL Error and No water formation #100945

    Oliver Kreylos
    Keymaster

    Intel’s on-chip graphics processors, such as the Iris Pro, won’t be powerful enough to run the AR Sandbox’s water simulation, and the GL error you’re seeing has the same root cause. You can get rid of it by disabling water simulation via SARndbox’s command line, by adding -ws 0 0.

    The GL error when bringing up any user interface component is also related, but doesn’t affect functionality. If it gets annoying, you can re-route error output from the program to the bitbucket by adding 2> /dev/null to the very end of the graphics program’s command line.

    in reply to: Kinect Viewer freezes #100944

    Oliver Kreylos
    Keymaster

    There is an alternative driver for AMD/ATI graphics cards directly from the vendor, called fglrx. You might have more luck with those. In general, Linux driver support for ATI/AMD graphics cards is not as good as that for Nvidia graphics cards, which is why we recommend the latter. But if you already have an ATI/AMD card, while a bit more complex, it should work.

    If the driver change doesn’t fix it, what happens when you press Win+Scroll Lock while the program is running, to enter “burn mode?” Will updates still freeze?

Viewing 15 posts - 331 through 345 (of 435 total)