Forum Replies Created

Viewing 15 posts - 316 through 330 (of 488 total)
  • Author
    Posts
  • in reply to: Cleaning the sand? #101655

    Oliver Kreylos
    Keymaster

    If you have dust, you should definitely try washing your sand. Sand dust might muck up the workings of your PC and projector, and if your sand is silica/quartz, i.e., the kind of stuff you find at the beach, then you don’t want to breathe in large amounts, either.

    Sandtastik sand, the brand we recommend, has a cleaning guide that might or might not work for you.

    An alternative idea, off the top of my head, would be to dump a bunch of sand into a bucket, fill the bucket with water, and then use a plastic mesh kitchen strainer to fish handfuls of sand back out of the bucket, shaking on the way out to get rid of fine dust. If your sand is finer than the finest strainer you can find, you could try using a cheese cloth, but I’m just spitballing at this point.

    in reply to: Full Screen Mode #101645

    Oliver Kreylos
    Keymaster

    As of Vrui-3.1-004, all Vrui applications enter/leave full-screen mode via Win+f. Window system-wide keyboard shortcuts still work as well, of course.

    in reply to: Full Screen Mode #101642

    Oliver Kreylos
    Keymaster

    Creating a text file via terminal:

    $ pluma <name of file>

    pluma is Mate’s text editor, and <name of file> is the file name, with optional path. E.g.,

    $ pluma Vrui.cfg

    to create Vrui.cfg in the current directory, or

    $ pluma ~/Vrui-3.1/etc/FullScreen.cfg

    to create FullScreen.cfg inside Vrui’s default configuration directory.

    If you quickly want to create a short file with only a few lines, you can use cat:

    $ cat > <name of file>

    The first “>” tells cat to write into the given file. Then just type one or more lines into the terminal, and press Ctrl+d to finish the file.

    To display the contents of a (short) text file, use cat without the “>”, e.g.,

    $ cat ~/Vrui-3.1/etc/FullScreen.cfg

    To browse through longer files inside a terminal, use less instead of cat. Of course, you can always use pluma to look at files, but you run the danger of accidentally modifying the file.

    in reply to: Full Screen Mode #101630

    Oliver Kreylos
    Keymaster

    Add -vruiVerbose to SARNdbox’s command line. This will tell you which configuration files Vrui is trying to load on start-up. Make sure the one you made is among them.

    Don’t worry about icons, but ensure that the name of the file is exactly the same as the one you specify after -mergeConfig. Do an $ ls on the directory where you saved the file, and check that everything matches. If there are spaces or other special characters in the file name, you need to enclose it in double quotes when giving it on the command line.

    in reply to: Model Export #101629

    Oliver Kreylos
    Keymaster

    That shouldn’t happen, and I don’t know what could be causing it. Try capturing a longer video sequence, and experiment with different frame indices, and see if it makes a difference. Use a frame index range, say 60 100, to check if you get at least a few frames, and look at my comment above regarding the output file name format (it needs to include a number conversion).

    in reply to: Model Export #101628

    Oliver Kreylos
    Keymaster

    Right you are, the correct invocation is:

    $ ./bin/LWOWriter <depth/color file name prefix> <output file name> <first frame> <last frame>

    <output file name> has to include a printf-style number template to generate one file name per frame, as in OutputFile%06d.lwo, otherwise subsequent frames will overwrite previous ones.

    LWOWriter has to iterate through all frames as depth files are compressed, and have to be processed sequentially. But just skipping a frame is much faster than generating an LWO file.

    Yes, the quality is what you should expect. That’s raw Kinect v1 data for you. This is the reason why the sandbox uses a long baseline low-pass filter to smooth raw data, which causes the 30 frame (1s) delay in topography updates.

    I’m going to add model output as a feature to the next SARndbox version.

    in reply to: dismantling projector #101627

    Oliver Kreylos
    Keymaster

    Rif6 Cube light output: 50 lumens
    BenQ MX631ST light output: 3200 lumens

    in reply to: USB Button Help #101626

    Oliver Kreylos
    Keymaster

    Depends on the type of button. Some are set up to emulate keyboards, in which case you should see characters pop up when you press the button while you have a terminal or text editor open.

    Other buttons advertise themselves as HID controllers (which is actually the better way), in which case you’ll have to tell the sandbox software about them explicitly.

    Do an

    $ ls /dev/input

    before and after you plug in your button, and see if a new event device node appeared. If so, you have the second type of button. You can listen to incoming events via

    $ sudo cat /dev/input/event<X>

    where event<X> is the new event node. When you press the button, you will see some garbage-looking output, which are actually HID event reports in binary.

    in reply to: Complete Installation Instructions #101604

    Oliver Kreylos
    Keymaster

    Yes. The file name needs to be BoxLayout.txt , or you can name the file arbitrarily and place it into an arbitrary location, and pass its full path and name to SARndbox via the -slf <sandbox layout file name> command line parameter.

    in reply to: Complete Installation Instructions #101603

    Oliver Kreylos
    Keymaster

    Did you add -fpv to the command line?

    in reply to: Some errors at startup #101582

    Oliver Kreylos
    Keymaster

    SWR is neat, but the 29x – 52x speed-up can not be expected for this application. The primary difference between SWR and vanilla Mesa is multi-threading in the vertex processing stage, meaning that SWR can use multiple CPU cores for geometry-heavy workloads like the isosurface/slice rendering for large 3D data sets they are targeting, i.e., tens of millions of triangles per frame. The 29x speed-up for 3M triangle geometries is achieved on a machine with 36 CPU cores.

    Furthermore, the AR Sandbox is fill-limited, not geometry-limited. The rendered surface consists of exactly 612,162 triangles ( (640-1)*(480-1)*2 ), and the majority of work is per-pixel work in the fragment shader. The water simulation is even more extreme; it only renders 2 (two) triangles per computation step, and everything is done in fragment shaders.

    The fragment processing stage of SWR is not architecturally different from vanilla Mesa, which is already multi-threaded.

    SWR is meant for one specific application: visualization of tera-scale 3D data on massively parallel supercomputers, using fixed-function OpenGL as employed by Vtk/ParaView/VisIt. It probably won’t help much on a typical gaming PC or laptop with 2-4 CPU cores, and with fill-limited software using complex shaders.

    in reply to: Some errors at startup #101581

    Oliver Kreylos
    Keymaster

    Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller

    That’s not going to work. Intel’s GMA X3100 graphics adapter, which is based on the GM965/GL960 chipset, is from 2007, before several graphics features required by the AR Sandbox even existed. When SARndbox requests those features, the Mesa OpenGL library falls back to software emulation mode, which is not only orders of magnitude slower than hardware rendering, but also quite buggy, especially in the modern features that don’t make sense in software emulation, and are therefore hardly used or tested. My guess is the crashes you are getting are happening inside the Mesa library itself, not in SARndbox.

    Regarding speed: I just tested the AR Sandbox software on my new laptop, which has an Intel Core i5-5200U CPU with integrated HD 5500 graphics adapter. This is a 2015 CPU, and still doesn’t support the framebuffer / shader features required to run the water simulation. Without water simulation, the sandbox ran at a rate of around 25 frames per second, with visible glitches in contour line rendering (which hint at graphics driver bugs).

    According to the wikipedia article I linked above, this GPU is on the order of 50 times faster than the GMA X3100 (based on comparing core clock rate times number of computing units).

    in reply to: Some errors at startup #101556

    Oliver Kreylos
    Keymaster

    The (lack of) output is a good data point.

    What GPU (and driver) do you have? Please run

    $ lspci | grep VGA

    and

    $ glxinfo

    in a terminal and post the results here.

    in reply to: Minor software update #101540

    Oliver Kreylos
    Keymaster

    You won’t have much success with that machine. Your CPU (Athlon 64 X2) is about a factor of 7 slower than our minimal recommended CPU (Intel Core i5), and while I didn’t find a Radeon card with a 1540 or 1520 model number, I’m assuming it’s the same vintage as the CPU (2009), and probably won’t be powerful enough.

    You might be able to run the AR Sandbox without water simulation by appending -ws 0.0 0 to the command line, but even then it might be slow.

    To avoid the error message during calibration, ensure that the Kinect tracks your calibration target properly before confirming a tie point, and that you don’t move the target for 2 seconds after confirming. The target disk is supposed to show up green in the real-time calibration display.

    in reply to: Some errors at startup #101539

    Oliver Kreylos
    Keymaster

    The required command line parameter is -fpv (“fix projector view”) not -ftp. This shouldn’t cause an issue, but could you please try again?

    Also, what is the full output from SARndbox when it crashes?

Viewing 15 posts - 316 through 330 (of 488 total)