ViewVC Help
View File | Revision Log | Show Annotations | Download File | Root Listing
root/Development/ray/doc/man/man1/vwrays.1
(Generate patch)

Comparing ray/doc/man/man1/vwrays.1 (file contents):
Revision 1.2 by greg, Tue Dec 9 15:59:07 2003 UTC vs.
Revision 1.6 by greg, Mon Nov 10 19:08:17 2008 UTC

# Line 22 | Line 22 | If a given pixel has no corresponding ray (because it
22   legal view boundaries), then six zero values are sent instead.
23   .PP
24   The
25 < .I -i
25 > .I \-i
26   option may be used to specify desired pixel positions on the standard
27   input rather than generating all the pixels for a given view.
28   .PP
29   The
30 < .I -f
30 > .I \-f
31   option may be used to set the record format to something other than the
32   default ASCII.
33   Using raw float or double records for example can reduce the time
# Line 41 | Line 41 | manual page, including input from a view file with the
41   .I \-vf
42   option.
43   Additionally, the target X and Y dimensions may be specified with
44 < .I -x
44 > .I \-x
45   and
46 < .I -y
46 > .I \-y
47   options, and the pixel aspect ratio may be given with
48 < .I -p.
48 > .I \-pa.
49   The default dimensions are 512x512, with a pixel aspect ratio of 1.0.
50   Just as in
51   .I rpict,
52   the X or the Y dimension will be reduced if necessary
53   to best match the specified pixel
54   aspect ratio, unless this ratio is set to zero.
55 + The
56 + .I \-pj
57 + option may be used to jitter samples.
58 + The default value of 0 turns off ray jittering.
59   .PP
60   If the
61 < .I -d
61 > .I \-d
62   option is given, then
63   .I vwrays
64   just prints the computed image dimensions, which are based on the view
65   aspect and the pixel aspect ratio just described.
66   The
67 < .I -ld
67 > .I \-ld
68   switch will also be printed, with
69 < .I -ld+
69 > .I \-ld+
70   if the view file has an aft clipping plane, and
71 < .I -ld-
71 > .I \-ld-
72   otherwise.
73   This is useful for passing options to the
74   .I rtrace
# Line 78 | Line 82 | equal the maximum distance for each pixel, which will
82   correctly by
83   .I rtrace
84   with the
85 < .I -ld+
85 > .I \-ld+
86   option.
87   Note that this option should not be given unless there is an aft
88   clipping plane, since the ray direction vectors will be normalized
# Line 101 | Line 105 | for light rays leaving the scene surfaces to strike ea
105   To compute the ray intersection points and returned directions corresponding
106   to a picture and its depth buffer:
107   .IP "" .2i
108 < vwrays scene_v2.pic scene_v2.zbf > scene_v2.pts
108 > vwrays scene_v2.hdr scene_v2.zbf > scene_v2.pts
109   .PP
110   To determine what the dimensions of a given view would be:
111   .IP "" .2i
112 < vwrays -d -vf myview.vf -x 2048 -y 2048
112 > vwrays \-d \-vf myview.vf \-x 2048 \-y 2048
113   .PP
114   To generate a RADIANCE picture using
115   .I rtrace
116   instead of
117   .I rpict:
118   .IP "" .2i
119 < vwrays -ff -vf view1.vf -x 1024 -y 1024 |
120 < rtrace `vwrays -d -vf view1.vf -x 1024 -y 1024` -ffc scene.oct > view1.pic
119 > vwrays \-ff \-vf view1.vf \-x 1024 \-y 1024 |
120 > rtrace `vwrays \-d \-vf view1.vf \-x 1024 \-y 1024` \-ffc scene.oct > view1.hdr
121   .SH AUTHOR
122   Greg Ward Larson
123   .SH ACKNOWLEDGMENT
# Line 125 | Line 129 | can reproduce any pixel ordering (i.e., any image orie
129   a rendered picture, it will only produce standard scanline-ordered rays when
130   given a set of view parameters.
131   .SH "SEE ALSO"
132 < rcalc(1), rpict(1), rtrace(1)
132 > rcalc(1), rpict(1), rtcontrib(1), rtrace(1)

Diff Legend

– Removed lines
+ Added lines
< Changed lines (old)
> Changed lines (new)