Forum Replies Created
November 18, 2022 at 5:21 am in reply to: Adding different liquid textures/animations (lava, toxic waste, etc) #2338
I’ve not done more than play with different liquid textures, so others might have better information.
The key piece is replacing the
SurfaceAddWaterColor.fsfile with a copy using different colors. Search inside that file for “Lava” for the line to change. The sandbox will automatically update if you replace
SurfaceAddWaterColor.fswhile SARndbox is running.
Any sand is usable. All varieties will have benfits and drawbacks.
Have you seen the “Sand” and “Health Concerns” sections of the online instructions?
I think the Promethean has too short of a throw. As I read the specs, it will not focus beyond a 24 inch throw distance. It’s common to have around a 40 inch throw distance on a sandbox. Focus is not generally vital with the projected sandbox content (except for calibration), but this may be too far out.
From the image you shared, I suspect your depth camera has died. Are there any error messages in the terminal window where you started
The only thing I have seen similar to this is when I have tried to continue on from a failed build. The Make dependency graph does not see the need to recompile object files, so stale files are used during linking. One option is to remove the
srcdirectory before re-running
bash Build-Ubuntu.sh.November 10, 2022 at 1:13 pm in reply to: Further calibration problems–green indicator problems and no red crosshairs #2321
Do you have sand? Or are you still using cardboard?
I suspect the calibration error message is because all your tie points are above the “sand”. Once you are able to capture tie points below the sand surface level, I expect the error messages will stop.
Look for the “calibration-error-some-tie-points-have-negative-projection-weights” topic on the old forum on the Wayback Machine for a hint from okreylos about tie points.
(I would show the direct link, but my post fails when I include it.)November 7, 2022 at 9:41 am in reply to: Further calibration problems–green indicator problems and no red crosshairs #2316
Thank you for sharing the videos. That makes it much faster to see possible causes.
I believe the source of your calibration problems is that the handle on your target is too wide. The calibration software needs to “see” a circle floating in space and will not project green if fingers, box walls, sand, or other things are too close. Assuming the circle has a 12 cm diameter (CD size), your handle is about 1.6 cm across where it intersects the circle. Try replacing your wide handle with a stiff wire and keep at least a 5 cm gap between the circle and your fingers.
Let me know if this works or not.
I’ve seen this when I forget to “Average Frames” before trying to extract the base plane. Read the second paragraph of Step 8 again and let me know if this does not solve your issue.
Fortunately, there is a core dump and more information is available in there. Assuming you start the sandbox (in a terminal window) like “./bin/SARndbox”, then please post the output from
gdb -q ./bin/SARndbox core.
If you do not see message like “Core was generated by…” and “Program terminated with signal 11…”, then type
whereat the “(gdb)” prompt.
Please post the gdb output that starts with “Core was generated by…”. The info should help point out something for further checking.
…RawKinectViewer opened without that.
I can see why you thought the directory was not needed. This is a quirk to the way the Sandbox software is installed.
RawKinectVieweris a system-wide install, while
CalibrateProjectoris only under the compiling user’s home directory.
- This reply was modified 1 month, 1 week ago by Sean Robinson.
Welcome to the forum.
The response means that either the utility was not created in Step 5 (was there an error?) or your entered text does not match Step 11. Make sure you follow Step 11 as it is written since the directory is an important detail.
If that does not work, please post the output of
ls -lfrom the same command window. This will show all the files in your current directory with some metadata about the files.
Could you give more details about how you are creating the secondary view? Are you using
SARndboxClientor another method?
A few ideas…
I have previously made the mistake of editing the wrong BoxLayout.txt file. Make sure the file you’re editing is the same one SARndbox is reading. Try very large changes (i.e. 20-50 cm) and see if there is any change in the running sandbox. If not, it’s the wrong file.
Try cleaning the Kinect IR lens.
Your Kinect may have failing pixels “on the left side”. Physically reorient the camera so that the bad pixels view outside the box perimeter.