Forum Replies Created

Viewing 15 posts - 16 through 30 (of 522 total)
  • Author
    Posts
  • in reply to: Intersect Plane on 3D view #124225
    Oliver Kreylos
    Keymaster

    There is specific functionality to show dipping beds. It is exposed via SARndbox’s command pipe. First, create a named UNIX pipe somewhere in the file system, say in the directory from which you typically run the program:

    cd ~/src/SARndbox-2.7
    mkfifo SARndbox.fifo

    Then run SARndbox with the additional -cp <pipe name> command line argument:

    ./bin/SARndbox <usual command line parameters> -cp SARndbox.fifo

    You can now enable the dipping bed by writing its plane equation to the command pipe, like so:

    echo dippingBed <nx> <ny> <nz> <offset> > SARndbox.fifo

    where <nx>, <ny>, and <nz> are the plane’s normal vector and <offset> is the origin offset, i.e., the planes are specified in non-normalized Hessian form. The ">" in front of SARndbox.fifo has to be typed literally, it’s an output redirect operator to print to the pipe instead of the terminal.

    For example, to draw a horizontal plane at zero elevation, write

    echo dippingBed 0.0 0.0 1.0 0.0 > SARndbox.fifo

    You can turn the dipping bed off again by writing:

    echo dippingBed off > SARndbox.fifo

    It’s probably best to make scripts for these commands, and bind those scripts to buttons/keys inside SARndbox via the ScriptExecutorTool.

    • This reply was modified 5 months, 2 weeks ago by Oliver Kreylos. Reason: Added example and clarification
    in reply to: ARSandox-Projector Calibration? #124224
    Oliver Kreylos
    Keymaster

    To delete a tool assignment, move the mouse cursor into the red box in the corner of the window, and then press and release the key or button whose tool binding you want to clear. See Step 3 in the instructions for details.

    in reply to: ARSandox-Projector Calibration? #124222
    Oliver Kreylos
    Keymaster

    If you are getting a red screen after pressing a button, then you are pressing the wrong button. Here is the relevant bit from the instructions:

    “To recap, you need to bind a “Capture” tool from the root tool menu to two unused mouse buttons or keyboard keys to capture tie points. For example, to bind a “Capture” tool to the “1” and “2” keys, first press and hold “1.” This will pop up the tool selection menu. While holding “1,” move the mouse to highlight the “Capture” menu entry. Then let go of the “1” key. This will close the tool selection menu, and open a “Creating Capture Tool…” dialog prompting you to press another key for tool function “Capture Background.” Now press and release the “2” key. This will close the dialog, and finish tool assignment. Afterwards, press and release “1” to capture a tie point and advance calibration, and press and release “2” to re-capture the background sand surface after you have made any changes to it, such as digging a hole to capture a low tie point.”

    Please note the highlighted section.

    in reply to: Vrui Installation Problems #124220
    Oliver Kreylos
    Keymaster

    I assume you did not use the automatic installation script, Build-Ubuntu.sh? In that case you have to install the Xrandr library by hand, via
    sudo apt-get install libxrandr-dev

    Afterwards run make again.

    In general, I strongly recommend using the automated build script. It will do two main things for you: it will install the most recent Vrui version, and install all system libraries required by it.

    in reply to: Intersect Plane on 3D view #124207
    Oliver Kreylos
    Keymaster

    You mean you want to have a 3D plane with some position and orientation, and see the trace on the surface where the plane intersects it?

    in reply to: Trying Kinect Azure, which SARndbox version? #124194
    Oliver Kreylos
    Keymaster

    In that case you’d want to start with the current versions: Vrui-5.2-001, Kinect-3.9, and SARndbox-2.7.

    in reply to: Trying Kinect Azure, which SARndbox version? #124192
    Oliver Kreylos
    Keymaster

    None of the Kinect packages have support for Kinect for Azure. It’s a totally different type of camera, yet again, and requires a new driver.

    in reply to: Vrui Installation Problems #124187
    Oliver Kreylos
    Keymaster

    I uploaded new versions of Vrui, Kinect, and SARndbox to the download server at http://www.idav.ucdavis.edu/~okreylos. Those updates should build fine on Linux Mint 19.3.

    in reply to: Keyboard causing system freezes #124184
    Oliver Kreylos
    Keymaster

    I updated a system to Linux Mint 19.3 (MATE) last night, and did not have the keyboard problem reported here. I did have that same problem on Fedora 30, but there the grabPointer change fixed it.

    in reply to: Keyboard causing system freezes #124088
    Oliver Kreylos
    Keymaster

    Edit Vrui.cfg, by default in /usr/local/etc/Vrui-<version>:

    $ sudo xed /usr/local/etc/Vrui-4.6/Vrui.cfg

    Find the section called “MouseAdapter” and insert the following line into it:

    grabPointer false

    Then save Vrui.cfg. That should fix it.

    in reply to: Binding additional functions to keys #124087
    Oliver Kreylos
    Keymaster

    You gave both tool sections the same name (“WaterTool”). You need to give them different names, such as “WaterTool1” and “WaterTool2”, or “GlobalWaterTool” and “LocalWaterTool”.

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

    I added a remote viewing feature a while ago, see https://youtu.be/6_TTNfz9Vkg , but haven’t released that new version of the SARndbox package yet.

    Essentially, you need a second computer also running the SARndbox software, and connect them over a local-area network. Streaming the view requires very high bandwidth right now, so the best way is to connect the two computers directly with an Ethernet cable.

    in reply to: Vrui Installation Problems #124085
    Oliver Kreylos
    Keymaster

    That’s a bug, exposed by a change in system libraries with a new OS version.

    The fix is to edit Images/BaseImage.h in the Vrui source code directory, and insert the line

    #include <stddef.h>

    before line 27, which is currently #include <Threads/Atomic.h>

    in reply to: Had any luck with RealSense? #123983
    Oliver Kreylos
    Keymaster

    As an aside, was the original first-gen Kinect better than the Kinect v2 for the AR Sandbox even?

    The Kinect v2 has higher effective resolution for most applications because of its time-of-flight nature, but for the AR Sandbox, where filtering collects depth samples over time, that didn’t really have an advantage, so Kinect v1’s higher nominal resolution was a plus. In addition, the Kinect v2 is quite unreliable compared to Kinect v1, at least using the reverse-engineered Linux driver I have. It seems there are multiple slightly different versions out there, and my driver works pretty solidly on the two cameras I have (where I reverse-engineered and debugged it), but others have reported persistent issues.

    Overall, and only for the AR Sandbox, I recommend Kinect v1 over Kinect v2.

    in reply to: Had any luck with RealSense? #123982
    Oliver Kreylos
    Keymaster

    If so, is it resolution dependent or could someone just write a Kinect For Azure wrapper and pipe in the 1024×1024 depth stream and things would just work?

    In principle, yes. Ideally this would be done inside my Kinect package, which has support for other camera types as well and a generic depth/color image streaming API. Cameras advertise their depth and color stream resolutions and intrinsic parameters, and downstream software is device-independent.

    It would also be possible to run the low-level camera driver on a separate host (using original Windows drivers for example), and stream the depth images over the network. There is already a remote camera protocol in the Kinect package, so it would be easiest to stream using that protocol. It also does compression to reduce bandwidth.

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