| 5 |
|
.SH SYNOPSIS |
| 6 |
|
.B obj2mesh |
| 7 |
|
[ |
| 8 |
+ |
.B "\-a matinput" |
| 9 |
+ |
][ |
| 10 |
|
.B "\-n objlim" |
| 11 |
|
][ |
| 12 |
|
.B "\-r maxres" |
| 27 |
|
which is sent to |
| 28 |
|
.I output.rtm |
| 29 |
|
(or standard output). |
| 30 |
+ |
Any RADIANCE material descriptions included via one or more |
| 31 |
+ |
.I \-a |
| 32 |
+ |
options will be compiled and stored in the mesh as well. |
| 33 |
|
This mesh may be included in a RADIANCE scene description via the |
| 34 |
|
.I mesh |
| 35 |
|
primitive, thus: |
| 44 |
|
.PP |
| 45 |
|
The syntax and semantics are identical to the RADIANCE |
| 46 |
|
.I instance |
| 47 |
< |
primitive, except that the mesh modifier may not be "void", since |
| 48 |
< |
materials are not included in a compiled mesh file. |
| 47 |
> |
primitive. |
| 48 |
> |
If |
| 49 |
> |
.I mod |
| 50 |
> |
is "void", then the stored mesh materials will be applied during rendering. |
| 51 |
> |
Otherwise, the given material will be substituted on |
| 52 |
> |
all the mesh surfaces. |
| 53 |
|
.PP |
| 54 |
|
The |
| 55 |
|
.I \-n |
| 104 |
|
These coordinates will be interpolated and passed |
| 105 |
|
to the "Lu" and "Lv" variables during rendering. |
| 106 |
|
Local coordinates can extend over any desired range of values. |
| 107 |
+ |
.TP |
| 108 |
+ |
.BI usemtl " mname" |
| 109 |
+ |
A material name. |
| 110 |
+ |
The following faces will use the named material, which is |
| 111 |
+ |
taken from the material definitions in the |
| 112 |
+ |
.I \-a |
| 113 |
+ |
input file(s). |
| 114 |
+ |
.TP |
| 115 |
+ |
.BI g " gname" |
| 116 |
+ |
Group association. |
| 117 |
+ |
The following faces are associated with the named group. |
| 118 |
+ |
If no "usemtl" statement has been |
| 119 |
+ |
encountered, the current group is used for the surface material |
| 120 |
+ |
identifier. |
| 121 |
|
.TP |
| 122 |
|
.BI f " v1/t1/n1 v2/t2/n2 v3/t3/n3" " .." |
| 123 |
|
A polygonal face. |
