109 |
|
.IP |
110 |
|
M material name |
111 |
|
.IP |
112 |
< |
- dash (end of trace marker) |
112 |
> |
~ tilde (end of trace marker) |
113 |
|
.IP |
114 |
|
If the letter 't' appears in |
115 |
|
.I spec, |
118 |
|
If the capital letter 'T' is given instead of 't', then all rays will |
119 |
|
be reported, including shadow testing rays to light sources. |
120 |
|
Spawned rays are indented one tab for each level. |
121 |
< |
The dash marker ('-') is a handy way of differentiating the final ray |
122 |
< |
value from traced values preceeding it, and should appear immediately |
123 |
< |
after the |
124 |
< |
.I \-o |
125 |
< |
and before the rest of the specification. |
121 |
> |
The tilde marker ('~') is a handy way of differentiating the final ray |
122 |
> |
value from daughter values in a traced ray tree, and usually appears |
123 |
> |
right before the 't' or 'T' output flags. |
124 |
|
E.g., |
125 |
< |
.I \-o-vTmW |
125 |
> |
.I \-ov~TmW |
126 |
> |
will emit a tilde followed by a tab at the end of each trace, |
127 |
> |
which can be easily distinguished even in binary output. |
128 |
|
.IP |
129 |
|
Note that there is no space between this option and its argument. |
130 |
|
.TP |
622 |
|
Greg Ward |
623 |
|
.SH "SEE ALSO" |
624 |
|
getinfo(1), lookamb(1), oconv(1), pfilt(1), pinterp(1), |
625 |
< |
pvalue(1), rpict(1), rvu(1), vwrays(1), ximage(1) |
625 |
> |
pvalue(1), rpict(1), rtcontrib(1), rvu(1), vwrays(1), ximage(1) |