Forum Replies Created

Viewing 15 posts - 1 through 15 (of 36 total)
  • Author
    Posts
  • in reply to: Two minor software updates #102973

    maphew
    Participant

    …a new tool in RawKinectViewer that simplifies AR Sandbox calibration step 5 (“measure 3D extents of sand surface”).

    What is the new tool and how is it used?

    thanks!

    in reply to: USB insufficient permissions? #102804

    maphew
    Participant

    Logging out and back in again did the trick. Thanks for the details on what’s happening!

    • This reply was modified 1 year, 6 months ago by  maphew.
    in reply to: USB insufficient permissions? #102771

    maphew
    Participant

    Ignore the bit about makefiles being different, they’re not. My source folder was contaminated. I removed them and started over. The real problem was a typo in the install command, I typed devrules instead of Udevrules. The correct command is:

    sudo make installudevrules

    I misled by incorrect error message from make:

    $ make any-thing-you-want-man
    make: 'any-thing-you-want-man' is up to date.

    —-
    HOWEVER, this doesn’t fix the permissions problem. The rule file is now installed, but has no effect. :-/

    
    hello@sandbox ~ $ RawKinectViewer -compress 0
    Caught exception USB::Device::open: Insufficient device permissions
    
    hello@sandbox ~ $ ls -l /etc/udev/rules.d/
    total 8
    -rw-r--r-- 1 root root 1016 Dec  4 16:49 69-Kinect.rules
    -rw-r--r-- 1 root root 2233 Dec  3 20:30 69-Vrui-devices.rules
    
    hello@sandbox ~ $ ls -l /etc/udev/rules.d/69-Kinect.rules 
    -rw-r--r-- 1 root root 1016 Dec  4 16:49 /etc/udev/rules.d/69-Kinect.rules
    
    hello@sandbox ~ $ cat /etc/udev/rules.d/69-Kinect.rules 
    # Rules to relax permissions on USB files for Microsoft Xbox Kinect
    # This file was installed by the Kinect 3D Video Capture Project.
    # Copyright (c) 2013-2016 Oliver Kreylos
    
    # Rules for Kinect-for-Xbox model 1414:
    SUBSYSTEMS=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="02ad", TAG+="uaccess"
    SUBSYSTEMS=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="02ae", TAG+="uaccess"
    SUBSYSTEMS=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="02b0", TAG+="uaccess"
    
    # Rules for Kinect-for-Xbox model 1473 and Kinect-for-Windows model 1517:
    SUBSYSTEMS=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="02be", TAG+="uaccess"
    SUBSYSTEMS=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="02bf", TAG+="uaccess"
    SUBSYSTEMS=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="02c2", TAG+="uaccess"
    
    # Rules for Kinect-for-Windows version 2.0:
    SUBSYSTEMS=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="02c4", TAG+="uaccess"
    SUBSYSTEMS=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="02d9", TAG+="uaccess"
    
    • This reply was modified 1 year, 6 months ago by  maphew.
    in reply to: USB insufficient permissions? #102769

    maphew
    Participant

    By way of other posts in the forum I discovered there needs to be a rule added to /etc/udev/rules.d/ to allow non-sudo use of the camera. In the Kinect makefile I see the logic that is supposed to add the file, but for some reason it is not being triggered or used properly.

    This line in the makefile doesn’t get executed: @sudo install -m u=rw,go=r share/70-Kinect.rules $(UDEVRULEDIR)

    
    hello@sandbox ~/src/Kinect-3.2 $ sudo make install
    ---- Kinect configuration options: ----
    Support for Intel RealSense cameras via librealsense library disabled
    CPU-based facade projector selected
    ---- Kinect installation configuration ----
    Root installation directory: /usr/local
    Calibration data directory: /usr/local/etc/Vrui-4.2/Kinect-3.2
    Resource data directory: /usr/local/share/Vrui-4.2/Kinect-3.2
    Vislet plug-in directory: /usr/local/lib/x86_64-linux-gnu/Vrui-4.2/VRVislets
    ---- End of Kinect configuration options: ----
    Installing header files...
    Installing libraries...
    Configuring run-time linker...
    Installing executables...
    Installing vislet plugins...
    Installing configuration files...
    Installing resource files...
    Installing makefile fragments...
    hello@sandbox ~/src/Kinect-3.2 $ sudo make installdevrules
    make: 'installdevrules' is up to date.
    hello@sandbox ~/src/Kinect-3.2 $ RawKinectViewer -compress 0
    Caught exception USB::Device::open: Insufficient device permissions
    
    hello@sandbox ~/src/Kinect-3.2 $ ls -l /etc/udev/rules.d/
    total 4
    -rw-r--r-- 1 root root 2233 Dec  3 20:30 69-Vrui-devices.rules
    
    hello@sandbox ~/src/Kinect-3.2 $ sudo make installdevrule
    make: 'installdevrule' is up to date.
    
    hello@sandbox ~/src/Kinect-3.2 $ sudo make uninstalldevrule
    make: 'uninstalldevrule' is up to date.
    
    hello@sandbox ~/src/Kinect-3.2 $ sudo make installdevrule
    make: 'installdevrule' is up to date.
    
    hello@sandbox ~/src/Kinect-3.2 $ ls -l /etc/udev/rules.d
    total 4
    -rw-r--r-- 1 root root 2233 Dec  3 20:30 69-Vrui-devices.rules
    

    —–
    Aha! the source file 70-Kinect.rules doesn’t exist:

    
    hello@sandbox ~/src/Kinect-3.2 $ sudo install -m u=rw,go=r share/70-Kinect.rules /etc/udev/rules.d/
    install: cannot stat 'share/70-Kinect.rules': No such file or directory
    hello@sandbox ~/src/Kinect-3.2 $ ls -l share
    total 12
    -rw-r--r-- 1 hello hello 1016 Oct 14 16:23 69-Kinect.rules
    -rw-r--r-- 1 hello hello  306 Dec  4 15:02 Configuration.Kinect
    drwxr-xr-x 2 hello hello 4096 Dec 14  2013 Shaders
    

    —-

    Stranger still. The makefile I have in my Kinect-3.2 src folder does not match the v3.2 on GitHub: https://github.com/KeckCAVES/Kinect/blob/master/makefile. The github version uses 69-Kinect.rules and has a completely different *uninstall* section.

    • This reply was modified 1 year, 6 months ago by  maphew.
    in reply to: Minimum Requirements to Run Water Simulation #102017

    maphew
    Participant

    That machine sounds very similar to mine. Upgrading the video card made an improvement, but don’t go top of the line. An Nvidia GTX 750ti for ~$200 was enough to make the CPU be the limiting factor. More video card after that will have no effect. See http://lakeviz.org/forums/topic/min-system-specs-not-models/

    I’m happy enough with this machine for the moment. The animation is not as smooth as in the videos from Oliver, and with a lot of rain it gets sluggish, but it’s okay. The kids, big and little, still have fun.

    in reply to: installing to different location #101932

    maphew
    Participant

    oh, thanks. I’ve been passing variables on the command line instead of editing the makefiles because I want future upgrades to be easy. no worrying about migrating personal changes forward. I’m beginning to think I’ve just been making more work for myself!

    in reply to: Running on Windows? #101931

    maphew
    Participant

    It just doesn’t work on Windows. Even it did, the parts you’d likely have difficulty with initially — command line options, customized start scripts, elevation colour maps, etc. — would be essentially the same on both platforms anyway.

    Installing Linux, especially Mint Linux, is not that difficult and the instructions for SARndbox are pretty good, starting from square one. You’ll need to make the occasional trip to the internet to learn how to do some basic thing now and then but the answers are almost always there.

    in reply to: installing to different location #101928

    maphew
    Participant

    FWIW, Kinect and SARndbox makefiles don’t understand make clean.

    in reply to: installing to different location #101926

    maphew
    Participant

    ahh, make clean and then doing it over again worked. Thank you!

    in reply to: Computer Specs #101923

    maphew
    Participant

    Search is found at http://lakeviz.org/forums/

    If sandbox is the only thing the computer is doing, the memory in that machine is overkill by about 22gb. 🙂 SARndbox can run “ok” on 1GB of system memory and an 8 year old 2 core CPU (specs here).

    Sarndbox needs a good video card more than CPU. With your CPU you could go to the Nvidia 970 Oliver recommends, however on older machines like mine that would be wasted because the CPU can’t push to the GPU fast enough (ref); the cheaper GTX 750ti is alright — for my box.

    Your FX580 video card will work, flowing water simulation might be sluggish. My advice is to go ahead and build the sandbox with what you have, and then upgrade the video card later if you the experience is not good enough. (If the new one is also Nvidia it’s an easy 5-10min switch.)

    in reply to: Placing the Display Window #101916

    maphew
    Participant

    this is gold. thank you.

    in reply to: The AR Sandbox World Map #101915

    maphew
    Participant

    Not public yet, still in my basement, but there’s an operational AR sandbox in Whitehorse, Yukon.
    https://www.google.ca/maps/@60.7153946,-135.0467364,6z?hl=en

    No idea yet how it’s going to be public, I don’t work for a school or museum or anything, but it’s just too cool not to build and share!

    in reply to: Set level of both Water and Rain #101914

    maphew
    Participant

    For the internal forum search function go up to the forum root, http://lakeviz.org/forums/ (I found it be accident. Be a good item for one of the top sticky posts).

    If water level means “lower point at which things turn blue” try editing etc/SARndbox-1.6/HeightColorMap.cpt. 1st column is cm from camera, followed by Red,Green,Blue color triplets.

    in reply to: "Best of" Shader file collection #101913

    maphew
    Participant

    Whups, the shout out should have been to INTPTT (Bill gave us the photos of them in action, but INTPT posted the code)

    in reply to: Feature wish list #101907

    maphew
    Participant

    Integrated shader switching. Basically the wish is for a method for switching between different colour maps (water, lava, tropical, snowy, …) that’s integrated into the application. It could be as simple as <kbd>F5</kbd> cycles between all files in share/SARndbox-<version>/Shaders/AddWater/ or, with a bit more work, having a .cfg file map:

    F1 = SurfaceAddWaterColor.fs
    F2 = SurfaceAddWaterColor-lava.fs

    Secondarily, a “best of” collection of shader files to give people a head start and ideas on creating their own.

    (Longer term, a generalised key-to-function framework would be welcome. There a quite a number of topics in the forum about how to assign X to key Y)

Viewing 15 posts - 1 through 15 (of 36 total)