4 |
|
vwrays - compute rays for a given picture or view |
5 |
|
.SH SYNOPSIS |
6 |
|
.B vwrays |
7 |
< |
.B "[ -i -f{a|f|d} | -d ]" |
7 |
> |
.B "[ -i -u -f{a|f|d} -c rept | -d ]" |
8 |
|
{ |
9 |
|
.B "view opts .." |
10 |
|
| |
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 |
+ |
If the |
29 |
+ |
.I \-u |
30 |
+ |
option is also given, output will be unbuffered. |
31 |
|
.PP |
32 |
|
The |
33 |
|
.I \-f |
37 |
|
requirements of transferring and interpreting information in |
38 |
|
.I rtrace. |
39 |
|
.PP |
40 |
+ |
The |
41 |
+ |
.I \-c |
42 |
+ |
option repeats each pixel the given number of times (default is 1). |
43 |
+ |
This is most useful when sending rays to |
44 |
+ |
.I rcontrib(1) |
45 |
+ |
with the same |
46 |
+ |
.I \-c |
47 |
+ |
setting, providing a much faster way to average pixels over image sets. |
48 |
+ |
The |
49 |
+ |
.I \-pj |
50 |
+ |
and/or |
51 |
+ |
.I \-pd |
52 |
+ |
options should be used to jitter sample postions in most cases. |
53 |
+ |
.PP |
54 |
|
View options may be any combination of standard view parameters described |
55 |
|
in the |
56 |
|
.I rpict(1) |
72 |
|
The |
73 |
|
.I \-pj |
74 |
|
option may be used to jitter samples. |
75 |
< |
The default value of 0 turns off ray jittering. |
75 |
> |
The |
76 |
> |
.I \-pd |
77 |
> |
option specifies a world-diameter aperture for depth-of-field jittering. |
78 |
> |
The default value of 0 for both options turns off all ray jittering. |
79 |
|
.PP |
80 |
|
If the |
81 |
|
.I \-d |
110 |
|
.PP |
111 |
|
If a picture is given on the command line rather than a set of view options, |
112 |
|
then the view and image dimensions are taken from the picture file, and |
113 |
< |
the reported ray origins and directions will exactly match the center of each |
114 |
< |
pixel in the picture. |
113 |
> |
the reported ray origins and directions will match the center of each |
114 |
> |
pixel in the picture (plus optional jitter). |
115 |
|
.PP |
116 |
|
If a depth buffer file is given as well, then |
117 |
|
.I vwrays |
125 |
|
To compute the ray intersection points and returned directions corresponding |
126 |
|
to a picture and its depth buffer: |
127 |
|
.IP "" .2i |
128 |
< |
vwrays scene_v2.pic scene_v2.zbf > scene_v2.pts |
128 |
> |
vwrays scene_v2.hdr scene_v2.zbf > scene_v2.pts |
129 |
|
.PP |
130 |
|
To determine what the dimensions of a given view would be: |
131 |
|
.IP "" .2i |
137 |
|
.I rpict: |
138 |
|
.IP "" .2i |
139 |
|
vwrays \-ff \-vf view1.vf \-x 1024 \-y 1024 | |
140 |
< |
rtrace `vwrays \-d \-vf view1.vf \-x 1024 \-y 1024` \-ffc scene.oct > view1.pic |
140 |
> |
rtrace `vwrays \-d \-vf view1.vf \-x 1024 \-y 1024` \-ffc scene.oct > view1.hdr |
141 |
|
.SH AUTHOR |
142 |
|
Greg Ward Larson |
143 |
|
.SH ACKNOWLEDGMENT |
149 |
|
a rendered picture, it will only produce standard scanline-ordered rays when |
150 |
|
given a set of view parameters. |
151 |
|
.SH "SEE ALSO" |
152 |
< |
rcalc(1), rpict(1), rtcontrib(1), rtrace(1) |
152 |
> |
rcalc(1), rcode_depth(1), rcontrib(1), rpict(1), rtpict(1), rtrace(1) |