| 1 |
.\" RCSid "$Id: rtpict.1,v 1.1 2018/03/20 02:40:38 greg Exp $" |
| 2 |
.TH RTPICT 1 3/19/2018 RADIANCE |
| 3 |
.SH NAME |
| 4 |
rtpict - generate a RADIANCE picture using rtrace |
| 5 |
.SH SYNOPSIS |
| 6 |
.B rtpict |
| 7 |
.B "-n nproc" |
| 8 |
[ |
| 9 |
.B "rpict options" |
| 10 |
] |
| 11 |
[ |
| 12 |
.B @file |
| 13 |
] |
| 14 |
.B octree |
| 15 |
.SH DESCRIPTION |
| 16 |
.I Rtpict |
| 17 |
is a script that generates a picture from the RADIANCE scene given in |
| 18 |
.I octree |
| 19 |
and sends it to the standard output, or to a file specified with the |
| 20 |
.I \-o |
| 21 |
option. |
| 22 |
Most options and defaults are the same as |
| 23 |
.I rpict(1), |
| 24 |
although a few switches are silently ignored. |
| 25 |
Options incompatible with multi-processing can generate an error. |
| 26 |
.PP |
| 27 |
The |
| 28 |
.I rtrace(1) |
| 29 |
tool is called with |
| 30 |
.I vwrays(1) |
| 31 |
to perform the actual work. |
| 32 |
This enables the |
| 33 |
.I \-n |
| 34 |
option for multiprocessing on platforms that support it. |
| 35 |
If the |
| 36 |
.I \-n |
| 37 |
option is not specified or is set to 1, then |
| 38 |
.I rpict |
| 39 |
is called directly. |
| 40 |
There is no benefit in setting the number of processes to anything |
| 41 |
greater than the number of virtual cores available on your machine. |
| 42 |
Also, it is very important to set the |
| 43 |
.I \-af |
| 44 |
option if an irradiance cache is being generated; |
| 45 |
otherwise, your speed-up will be far from linear. |
| 46 |
.SH EXAMPLE |
| 47 |
To render a scene with four processes: |
| 48 |
.IP "" .2i |
| 49 |
rtpict -n 4 -vf mypers.vf -ab 1 -af scene.amb scene.oct > scene_pers.hdr |
| 50 |
.SH AUTHOR |
| 51 |
Greg Ward |
| 52 |
.SH "SEE ALSO" |
| 53 |
getinfo(1), lookamb(1), mkpmap(1), oconv(1), pdfblur(1), pfilt(1), |
| 54 |
pinterp(1), pmblur(1), printf(3), ra_rgbe(1), rad(1), rpiece(1), |
| 55 |
rpict(1), rtrace(1), rvu(1) vwrays(1), |
