Yulong Science Edu equipment Company,Yulong road,TaiCang county,SooChow, JinagSu Province, China. Yulong road.
121.17021,31.480395
our Company equipments thousands of school in china
and i add three button to chang the surface from water to lava and Snow as well as the rain buttons.
The message means that Vrui is trying to synchronize the display, but the window manager doesn’t let it. It’s safe to ignore, and there’s a way to tell Vrui to stop trying if it gets annoying.
If you’re running SARndbox-2.2, you need to add -rer 20 100 to SARndbox’s command line to enable rain. It’s a bug that I fixed in SARndbox-2.3. I recommend replacing SARndbox-2.2. You can copy your existing configuration files over.
I think there is a larger issue here, apparently with multi-display use in Linux Mint Mate. I’ll have to have a closer look at that.
If someone wants to give this a shot: After installing Vrui, open Vrui’s main configuration file, /usr/local/etc/Vrui-
Then try the Vrui applications that caused problems again and see if there’s a difference.
Nope, has never happened to me. Did you run “sudo KinectUtil getCalib 0” before running RawKinectViewer?
If everything is blue, the loaded DEM is below the current sand surface everywhere (blue means too much sand, red means too little sand).
To adjust the DEM vertically, run the sandbox and load your DEM by assigning a “Show DEM” tool to some button. Once it’s assigned, select “Save Input Graph…” from the “Devices” sub-menu of Vrui’s system menu. Then exit the sandbox and open the file to which you saved.
It’s the same format as other Vrui configuration files, with one section per assigned tool. Find the section that says “toolClass DEMTool”. Into that section, put a new line
demVerticalShift 0.0
then save the file, run the sandbox again, and load the saved input graph from the “Devices” sub-menu.
You can also put the DEM file name in that section via demFileName
The trick is to fiddle with the vertical shift value by editing the input graph file until you have just enough sand to recreate the entire DEM. You can edit the file while the sandbox is running, and re-load the changes by selecting “Load Input Graph…” again.
If you have blue everywhere, use a large negative shift until everything is red. Then bisect until you get it just right.
Cinnamon!
That’s why I recommend Mate. 🙂
I’ll look into it, but it’s not a big deal I guess.
Oliver,
Thanks so much for looking into this. The desktop and terminal windows are displayed properly. The ShowEarthModel is a plain black window with no graphics, which is the same as RawKinectViewer and the Sarndbox application.
Screenshot here… http://imgur.com/a/mAXgQ
If I make the projector the primary display then nothing works. If I set the LCD monitor as primary then everything works just fine.
I opened up CompizConfig Settings but there is so much in here that I don’t know where to start. If I disable the composite plugin, it has to disable the OpenGL plugin, which has to disable 6 more plugins. I didn’t want to cause more problems by having so many plugins get disabled so I stopped. Do you know I would specifically disable in Compiz?
hi~ everybody
i always have some problem with my kinect (1414)，. I have successfully completed the installation process~ and it’s work~~ but every time i reboot the computer~ when i run again ~seems my kinect is Stop-motion @@
when i run “RawKinectViewer -compress 0” and the popup window with my kinect-detection is not
immediate~~ (stop at first second when open), both on (kinect 2.8 /vrui-3.1/sandbox1.6) or (kinect3.2/Vrui-4.2,SARndbox-2.2) , i always have same problem.. and when i esc and try again, it’s will show “caught exception kinect::camera::startStreaming:Failed to initialize streaming mode” then i need to re plug the kinect’s usb , then i can open the stop motion kinect again~~
how ever ~ sometimes it’s work good~ but i didnt change any thing, @@ i try two of my kinect (both1414) and two ver ubuntu (14.04 // 16.04) its all have this problem ~ di anyone know how to fix this?
sometimes when i occur and i will type the same line “RawKinectViewer -compress 0” and re-plug kinect until it’s works
i dont know why sometimes work and sometimes can’t with all the same commands.but i really want to fixed…
thanks help : )))
I get the same error message.
Hello to everyone, can anyone please, (please !), explain from scratch how to put it all together (included the xdotool)? I’m new in linux and this is really cool but hard to understand for a Linux newbie (like me), a video like the one from Oliver installing linux would be fantastic.
Thanks !
Is it possible to configure it by default so that you do not have to configure it every time?
Installing Kinect -3.2 and SARndbox-2.3 on a Fedora 24 (64bit) box, I had to add -ljpeg manually to the linker. Where should I update makefile to include jpeg library?
Thanks,
Zoltan
We are setting up an AR Sandbox and following the online directions. We are running Linux Mint 17.3 Rosa, Mate 64 bit. We have a Kinect 360 connected with this adapter https://www.amazon.com/gp/product/B00JVI6BVY/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1 to a Dell Alienware laptop (the laptop has 3.0 USB ports). The Kinect is powered and has a steady blinking green light. When I type “lsusb” into a command window it recognizes the Xbox Kinect is connected. However when I try to do Step 5 in the setup instruction, typing in “sudo KinectUtil getCalib 0” it asks for a password, which I typed in and continue, but then I get “sudo:KinectUtil: command not found”. So it seems it’s not pulling anything from the Kinect firmware or even liking the command. I was reading on the forum that maybe you need to be plugged into a 2.0 USB port, but my laptop does not have that. Is there a work around or is there some sort of hub or converter I should be trying? Or is there an alternate command that can be used to try to talk to the Kinect and get its firmware downloaded?
I ran the list of commands from the installation instructions post on Fedora 24 64-bit just now, and did not have to do that. The Kinect and SARNdbox packages correctly linked against libjpeg.so.
Do you have a non-standard libjpeg version on your system, or did you make any modifications to the Vrui, Kinect, or SARndbox packages before building? What is the output of
rpm -q libjpeg-turbo-devel
?
Basically, yes. All your configuration stuff is in …/etc/SARndbox-<version>, so you only have to copy over the share directory if you put custom shaders in there, such as lava shaders. But if you did that, you need to copy the entire share hierarchy, not just the share/SARndbox-<previous version> directory itself:
cp -R ~/src/SARndbox-<previous version>/share/SARndbox-<previous version> share/
I just realized that this is a problem with my instructions. You need to run
sudo /usr/local/bin/KinectUtil getCalib 0
for the command to work.
Thank you for reporting the error; I fixed the instructions accordingly.
There are a few additional steps one might want to do after successfully installing and calibrating the AR Sandbox software that I left out of the full installation instructions for brevity. These are minor tweaks: ensuring that CalibrateProjector and SARndbox always run in full-screen mode, automatically binding calibration or water management tools to keys, and automatically hiding the mouse cursor if the mouse isn’t moved.
These steps involve creating custom configuration files, which open up another host of possible fine-tuning options if one wants to go there. The following assumes an installation of Vrui-4.2-005 or newer, and SARndbox-2.3 or newer.
As of version 4.2, Vrui supports per-application configuration files. These are stored in a directory ~/.config/Vrui-<version>/Applications, and given the same name as the application to which they apply, plus a .cfg extension. In the following, replace Vrui-4.2 with your actual Vrui version, and replace pluma with another text editor if you do not use the MATE desktop environment. For example, the Gnome text editor is called gedit.
First, create a configuration file to force CalibrateProjector to start in full-screen mode, and bind the calibration tool to two buttons:
cd ~/.config/Vrui-4.2
mkdir Applications
cd Applications
pluma CalibrateProjector.cfgInto the new file, paste the following text exactly:
section Vrui
section Desktop
section Window
windowFullscreen true
endsection
section Tools
section DefaultTools
section CalibrationTool
toolClass CaptureTool
bindings ((Mouse, 1, 2))
endsection
endsection
endsection
endsection
endsectionand then save the file and exit from the text editor.
If you now start CalibrateProjector, its window will cover the entire screen, with no title bars or panels remaining. If you press the “1” key, the program will capture a tie point, and if you press the “2” key, the program will re-capture the background, indicated by the screen turning red for two seconds.
You can replace the “1” and “2” key names in the “bindings” tag with any other keys you like.
Next, create a configuration file to set up the SARndbox itself. In the same terminal, run:
pluma SARndbox.cfg
Into the new file, paste the following text exactly:
section Vrui
section Desktop
section MouseAdapter
mouseIdleTimeout 5.0
endsection
section Window
windowFullscreen true
endsection
section Tools
section DefaultTools
section WaterTool
toolClass GlobalWaterTool
bindings ((Mouse, 1, 2))
endsection
endsection
endsection
endsection
endsectionand then save the file and exit from the text editor.
As in the first case, this will force SARndbox to start in full-screen mode, ensuring that the calibration created using CalibrateProjector exactly matches the one used in the actual AR Sandbox. In addition, the “mouseIdleTimeout 5.0” setting will hide the mouse cursor after five seconds of inactivity. To get the cursor back, simply move the mouse. Finally, the “WaterTool” section binds a tool to add or remove water from the AR Sandbox globally, by pressing “1” to rain, and “2” to drain. As above, set the binding to whatever keys you prefer.
If you run the AR Sandbox from a laptop, or if your computer has a main display screen in addition to the projector, and you are using “extended desktop” mode where the two displays are logically placed next to each other, then the CalibrateProjector or SARndbox windows might show up on the wrong display. To automatically force them to the correct display, you can use Vrui-4.2’s output naming functionality.
Open up the SARndbox.cfg configuration file with a text editor, and insert the following into the “Window” section:
section Window
...
outputName Foo
...
endsectionthen save the file and exit from the text editor. Now run SARndbox with the -vruiVerbose command line option:
cd ~/src/SARndbox-2.3
./bin/SARndbox -uhm -fpv -vruiVerboseThis will print a lot of information to the console, including the names of all video outputs and monitors connected to your PC. Note the name that corresponds to your projector, and enter it in the configuration file in place of “Foo” above. Then apply the same change to the CalibrateProjector.cfg configuration file.
After the program spits out a bunch of those lines, it seems the software hangs shortly thereafter.
To set the record straight, I now suspect a faulty memory module is to blame for the hang. That said, I’ve reverted back to Sandbox 1.6 and Vrui 3.2 because it works with only the projector connected. (Having an another monitor connected was not an option.)
-Steve
hi~ i got some weird problem with my kinect. i got 2 kinect ( 1414 and 1473 ) and i run on ubuntu16.04 / kinect3.2 / Vrui-4.2 / SARndbox-2.2
i use 1414 when i run “RawKinectViewer -compress 0” and the popup window with my kinect-detection is not always immediate~~
sometimes is black and white https://drive.google.com/open?id=0B6Gvn85q9HptX1NQbEhQSHJaSjA
sometimes is lattice https://drive.google.com/open?id=0B6Gvn85q9HptMWpjRGhVeHNITlE
and most of times it’s seems stop at first second capture https://drive.google.com/open?id=0B6Gvn85q9HptdGpRYTI2M1NfeWM
and i follow the topic and try to usb2.0 or 3.0 and change different adapter it’s all the same
and when i press esc and try again, it’s will show
“caught exception kinect::camera::startStreaming:Failed to initialize streaming mode” then i need to re plug the kinect’s usb
https://drive.google.com/open?id=0B6Gvn85q9HptWDh1TDhZaURuMVE
however after i try several times ,and it’s will work (sometime many many many times ,sometimes few times)
i don’t know why and how but it’s troubled .
but! ~ when i use 1473 it’s all good without any problem (all the same hardware)
so @@?? any one knows how to fix? thanks a lot
Caught exception GLContext: GLX extension not supported on display :0 while initializing rendering window 0
This means that GLX, the X Window System binding for OpenGL, is not found on the local computer. Did you install the vendor-supplied drivers for your laptop’s Nvidia GeForce graphics card, and then reboot the computer to activate the drivers?
Please run
glxinfo
and look for “server glx vendor string” and “OpenGL vendor string” (should both be “NVIDIA Corporation”) and “OpenGL version string” which should be something like “3.3.0 NVIDIA 340.98.”
It is also possible that your laptop uses Nvidia’s Optimus technology to switch between the GeForce graphics card and the graphics adapter built into its Intel Core CPU. If that’s the case, it will get complicated. Optimus is nominally supported under Linux, but it needs to be set up manually. There is some background information in this somewhat outdated article, and setup instructions for Arch Linux that should be applicable to Ubuntu / Linux Mint in this post.
