rshow commandline options

rshow commandline options:

**rshow options**
-bg r g b	background color, each channel [0..1]
-bl factor	scale factor for Radiance colors (to display dark colors lighter )
-d display	set X11 display
-do	display only (not GUI)
-e	dump'n'exit mode (specify output file with -o)
-ep	exact pixel (window-height/width -y/-x the aspect ratio in view file is adjusted)
-o file	output file (for animations and screen dumps)
-oc	display octree
-ns	no stipple pattern for mist etc.
-qi	don't read instances
-qs size	don't read primitives smaller than 'size', given in percent of the scene boundary box
-qd	don't initially display cylinders and instances
-qm regexp	don't read primitives whose's material match regexp
-r chops	angular resolution (number of vertices per sphere,cylinder,cone,disc), minimum 3
-v	add verbose output
-vf file	view file
-x size	width of drawing window
-y size	height of drawing window

currently not implemented:

rshow options
-af file ambient file (displays ambient values as 'crystals')
-as scale size of ambient 'crystals'

**rshow options**
-af file	ambient file (displays ambient values as 'crystals')
-as scale	size of ambient 'crystals'

technical notes

Open-GL support on X11: There have been reports of dysfunctional behaviour on X11/GLX/Open-GL versions. Typical error output:
rshow scene.oct checked_eval: Tcl_Eval "gui1_ui .w0 ::w0" returned: Togl: couldn't get visual (line 1 ) Tk_NameToWindow returned: Togl: couldn't get visualbad window path name ".w0.acker" tcl eval failed - panic+exit
Technically, that happens when no suitable visual is found in the GLX extension of your X-Server.
Try setting your X-Server / GLX-extension to at least 16bit doublebuffer. If that doesn't help, to aid in debugging, please sent the output of xdpyinfo and glxinfo -t to rshow debugging. Thanks.

Textures

Texturing in raytracing and hardware accelerated drawing are implemented in different ways : Raytracing calculates texture coordinates (s,t) on a per-pixel basis using Radiance's function files. Mapping could depend non-linearly on all variables (position, view direction, surface normal etc.). On the other hand, hardware rendering calculates coordinates per vertex and interpolates linearly in s/t space, so it is implicitly limited:

function can be linearly interpolated between vertices
function depends only on Px,Py,Pz, Nx,Ny,Nz
texturing is only supported on polygons (thats actually more a limit of the GLU tesselation )
texture images are not tiled (can't work unless we subdivide the polygon)
currently the post-process functions for colorpict are ignore; values are clamped to [0..1]

rshow misc

Problems with shared libraries on Linux ? see here
tcl buttons may not reflect start-up values
»toggle buttons once
setting of aspect ratio (both command line and interactive) doesn't change window size
»open second window. This looks like a bug in the fvwm window manager.
Some CAD programs (notable AutoCAD) tesselate a 4-corner polygon into two triangles. Beware of selecting the 'lower-left' one for picture mapping.
How are data triplets mapped to color values ?
» Currently, data triplets are averaged and the resulting value linearly mapped to the blue-red colors.
The eye-response curve is not applied in any internal calculation, users may do this at their full control outside of rshow.

back to main rshow page