584 |
|
added to the picture file name along with the standard ".pic" suffix. |
585 |
|
|
586 |
|
The standard views are specified by strings of the form |
587 |
< |
"[Xx]?[Yy]?[Zz]?[vlahc]?". |
587 |
> |
"[Xx]?[Yy]?[Zz]?[vlahsc]?". |
588 |
|
(That is, an optional upper or lower case X followed by an optional |
589 |
|
upper or lower case Y followed by an optional upper or lower case Z |
590 |
< |
followed by an optional lower case V, L, A, H or C.) |
590 |
> |
followed by an optional lower case view type.) |
591 |
|
The letters indicate the desired view position, where upper case "X" |
592 |
|
means maximum X, lower case "y" means minimum Y and so on. |
593 |
|
The final letter is the view type, where 'v' is perspective (the |
594 |
|
default), 'l' is parallel, 'a' is angular fisheye, 'h' is |
595 |
< |
hemispherical fisheye and 'c' is for cylindrical panorama. |
596 |
< |
A perspective view from maximum X, minimum Y would be "Xy" or |
597 |
< |
"Xyv". |
595 |
> |
hemispherical fisheye, 's' is for planisphere (stereographic) fisheye, |
596 |
> |
and 'c' is for cylindrical panorama. |
597 |
> |
A perspective view from maximum X, minimum Y would be "Xy" or "Xyv". |
598 |
|
A parallel view from maximum Z would be "Zl". |
599 |
|
If "ZONE" is an interior zone, the standard views will |
600 |
|
be inside the perimeter. |
633 |
|
Consult the rpict(1) manual page for a full description of the various |
634 |
|
view options, all of which begin with "-v". |
635 |
|
Just briefly, the "-vt?" option sets the view type, where "?" is |
636 |
< |
replaced by one of the letters "v, l, a, h or c", corresponding to |
636 |
> |
replaced by one of the letters "v, l, a, h, s or c", corresponding to |
637 |
|
perspective, parallel, angular fisheye, hemispherical fisheye |
638 |
|
and cylindrical panorama, respectively. |
639 |
|
The "-vp x y z" option sets the view position (eyepoint), where "x y z" |
883 |
|
It only means that some accuracy and possibly some smoothness |
884 |
|
will be traded for speed in the shadow calculations. |
885 |
|
|
886 |
+ |
.Options.Pgmap |
887 |
+ |
|
888 |
+ |
The "Pgmap" specifies the file to hold the global photons computed |
889 |
+ |
by the "mkpmap" command, followed by the number of photons to generate |
890 |
+ |
(required). |
891 |
+ |
A typical photon count for a global map is on the order of 100-200K. |
892 |
+ |
By convention, photon map files are given a ".pmp" suffix. |
893 |
+ |
An optional third parameter specifies the bandwidth to use |
894 |
+ |
for the global photons during rendering, and this value should be |
895 |
+ |
around 50. |
896 |
+ |
|
897 |
+ |
.Options.PgmDelete |
898 |
+ |
|
899 |
+ |
The "Delete" button next to the "Pgmap" window on the Options |
900 |
+ |
screen allows you to remove the named global photon map file. |
901 |
+ |
This is usually done when a change is made to the "mkpmap" options, |
902 |
+ |
as the file will be regenerated automatically after most scene changes. |
903 |
+ |
|
904 |
+ |
.Options.Pcmap |
905 |
+ |
|
906 |
+ |
The "Pcmap" specifies the file to hold the caustic photons computed |
907 |
+ |
by the "mkpmap" command, followed by the number of photons to generate |
908 |
+ |
(required). |
909 |
+ |
A typical photon count for a global map is on the order of 1000K. |
910 |
+ |
By convention, photon map files are given a ".pmp" suffix. |
911 |
+ |
An optional third parameter specifies the bandwidth to use |
912 |
+ |
for the global photons during rendering, and this value should be |
913 |
+ |
around 50. |
914 |
+ |
|
915 |
+ |
.Options.PcmDelete |
916 |
+ |
|
917 |
+ |
The "Delete" button next to the "Pcmap" window on the Options |
918 |
+ |
screen allows you to remove the named caustic photon map file. |
919 |
+ |
This is usually done when a change is made to the "mkpmap" options, |
920 |
+ |
as the file will be regenerated automatically after most scene changes. |
921 |
+ |
|
922 |
|
.Options.Ambfile |
923 |
|
|
924 |
|
The "Ambfile" is the file used to store Radiance ambient values for |
1003 |
|
.Options.Mkillum |
1004 |
|
|
1005 |
|
The "mkillum opts" window may be used to specify options to the |
1006 |
< |
mkillum(1) command, whose options are actually passed to rtrace(1). |
1006 |
> |
mkillum(1) command. |
1007 |
|
These options apply only if there are one or more "Illum" files |
1008 |
|
named on the Scene screen. |
1009 |
|
|
1010 |
|
It is very important to set mkillum options sensibly, |
1011 |
|
since rad does not have the intelligence to do it for you. |
1012 |
|
|
1013 |
+ |
.Options.Mkpmap |
1014 |
+ |
|
1015 |
+ |
The "mkpmap opts" window may be used to specify options |
1016 |
+ |
to the mkpmap(1) command. |
1017 |
+ |
There are no default values, and rad does not set these |
1018 |
+ |
options intelligently. |
1019 |
+ |
|
1020 |
|
.Options.Render |
1021 |
|
|
1022 |
|
The "render opts" window is used to specify additional options to |
1185 |
|
|
1186 |
|
The batch rendering view menu also selects the view or views |
1187 |
|
to use in producing a script during a dry run. |
1188 |
+ |
|
1189 |
+ |
.Action.Processes |
1190 |
+ |
|
1191 |
+ |
The "Number of processes" slider controls how many independent |
1192 |
+ |
processes are initiated by the "rvu" and "Start" buttons above |
1193 |
+ |
and below. |
1194 |
+ |
This should be set no greater than the number of virtual cores |
1195 |
+ |
on your system. |
1196 |
+ |
|
1197 |
+ |
For interactive rendering, the "new" command within rvu may |
1198 |
+ |
be used to change the number of processes running. |
1199 |
+ |
|
1200 |
+ |
For rendering in the background, the number of processes will |
1201 |
+ |
never be greater than the number of views if all views are |
1202 |
+ |
being rendered. |
1203 |
+ |
If only a single view is selected for rendering, rad |
1204 |
+ |
will call rpiece to render it in tiles using the given |
1205 |
+ |
number of processes. |
1206 |
|
|
1207 |
|
.Action.Start |
1208 |
|
|