| 487 |
|
|
| 488 |
|
There are two basic ways to compute the exposure value. |
| 489 |
|
The first is by trial and error, where the value is adjusted up and |
| 490 |
< |
down within rview using the "e = value" command. |
| 490 |
> |
down within rvu using the "e = value" command. |
| 491 |
|
Though it sounds flaky, this is the most reliable way to set the |
| 492 |
|
exposure (and ambient level) in general lighting situations. |
| 493 |
|
|
| 545 |
|
To remove an unwanted view, select it and press the "Delete" button. |
| 546 |
|
To undo this action, simply press the "Add" button again. |
| 547 |
|
|
| 548 |
< |
The first view in the list is the default given to rview during |
| 548 |
> |
The first view in the list is the default given to rvu during |
| 549 |
|
interactive rendering, and is the first view rendered in a batch run. |
| 550 |
|
To change the default view, select the newly desired view and press |
| 551 |
|
the "Set Default" button. |
| 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. |
| 614 |
|
define a view. |
| 615 |
|
|
| 616 |
|
The simplest view specification is of the form "-vf viewfile", where |
| 617 |
< |
"viewfile" is a file created with the rview "view" command, or a |
| 617 |
> |
"viewfile" is a file created with the rvu "view" command, or a |
| 618 |
|
Radiance picture. |
| 619 |
|
This method of naming views, although convenient, is not the best |
| 620 |
|
since it is difficult to know exactly where such a view is by |
| 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" |
| 702 |
|
The "Set Default" button may be used to make the selected view the |
| 703 |
|
default view for rendering. |
| 704 |
|
This simply moves the view to the top of the list in the rad input file. |
| 705 |
< |
The default view will be the one normally rendered by rview when rad |
| 705 |
> |
The default view will be the one normally rendered by rvu when rad |
| 706 |
|
is started interactively, and is the first view rendered in a batch |
| 707 |
|
process. |
| 708 |
|
|
| 838 |
|
minutes) between progress reports. |
| 839 |
|
|
| 840 |
|
Other windows allow the user to customize the options to oconv(1), |
| 841 |
< |
mkillum(1), rview(1) and rpict(1), and pfilt(1). |
| 841 |
> |
mkillum(1), rvu(1) and rpict(1), and pfilt(1). |
| 842 |
|
|
| 843 |
|
.Options.Quality |
| 844 |
|
|
| 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 |
| 952 |
|
|
| 953 |
|
The "Optfile" setting assigns a file to hold rendering options, |
| 954 |
|
which may be a convenience when these options are reused for |
| 955 |
< |
rtrace(1) or rpiece(1), or manual invocations of rview or rpict. |
| 955 |
> |
rtrace(1) or rpiece(1), or manual invocations of rvu or rpict. |
| 956 |
|
Using an options file also reduces the size of the command line, |
| 957 |
|
making it a little easier on the eye. |
| 958 |
|
|
| 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 |
| 1023 |
< |
the rview(1) and rpict(1) rendering programs. |
| 1023 |
> |
the rvu(1) and rpict(1) rendering programs. |
| 1024 |
|
Most of the important parameters are computed by rad, so this |
| 1025 |
|
window is usually used to override specific parameters or to give |
| 1026 |
|
additional information, such as which materials to exclude from the |
| 1069 |
|
run, usually via rad(1). |
| 1070 |
|
The top row of buttons is used to update the octree following a |
| 1071 |
|
change to one or more input files. |
| 1072 |
< |
The "rview" button starts an interactive rendering in the |
| 1072 |
> |
The "rvu" button starts an interactive rendering in the |
| 1073 |
|
foreground. |
| 1074 |
|
The next set of buttons provides for the control of a batch |
| 1075 |
|
rendering process, taking place in the background. |
| 1147 |
|
(This will still cause the ambient file to be removed, |
| 1148 |
|
unfortunately.) |
| 1149 |
|
|
| 1150 |
< |
.Action.Rview |
| 1150 |
> |
.Action.Rvu |
| 1151 |
|
|
| 1152 |
< |
The "rview" button on the Action screen starts an interactive |
| 1152 |
> |
The "rvu" button on the Action screen starts an interactive |
| 1153 |
|
rendering for the selected view, indicated by the menu button |
| 1154 |
|
just to the right. |
| 1155 |
< |
Other views may be accessed within rview using the "L name" |
| 1155 |
> |
Other views may be accessed within rvu using the "L name" |
| 1156 |
|
command, and new views can be added with the "V name" |
| 1157 |
|
command. |
| 1158 |
|
|
| 1162 |
|
a number later), then use the Views screen to override the previous |
| 1163 |
|
view definition with the new one. |
| 1164 |
|
(See the "View" topic in the current |
| 1165 |
< |
help category, the "Change" topic under "Views" and the rview(1) |
| 1165 |
> |
help category, the "Change" topic under "Views" and the rvu(1) |
| 1166 |
|
manual page for more information.) |
| 1167 |
|
|
| 1168 |
|
If the octree is out-of-date, it will be rebuilt before rendering |
| 1171 |
|
.Action.View |
| 1172 |
|
|
| 1173 |
|
The Action screen contains two menus for selecting views. |
| 1174 |
< |
The top menu, next to the "rview" button, sets the view to start |
| 1175 |
< |
with in rview, and is selected from the current view list. |
| 1174 |
> |
The top menu, next to the "rvu" button, sets the view to start |
| 1175 |
> |
with in rvu, and is selected from the current view list. |
| 1176 |
|
The second view menu, next to the "Start" button for batch |
| 1177 |
|
rendering, selects the view or views to render in batch mode. |
| 1178 |
|
If the special entry "ALL" is selected, then every view in the |
| 1179 |
|
current list will be rendered if it hasn't been already. |
| 1180 |
|
|
| 1181 |
< |
The view menu next to the "rview" button will be disabled if there |
| 1181 |
> |
The view menu next to the "rvu" button will be disabled if there |
| 1182 |
|
is only one view to choose from. |
| 1183 |
|
The view menu next to the "Start" button will be disabled if there |
| 1184 |
|
is a batch job in progress, and thus the view cannot be changed. |
| 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 |
|
|
