1 |
< |
.\" RCSid "$Id" |
1 |
> |
.\" RCSid "$Id$" |
2 |
|
.TH OBJ2MESH 1 03/11/03 RADIANCE |
3 |
|
.SH NAME |
4 |
|
obj2mesh - create a compiled RADIANCE mesh file from Wavefront .OBJ input |
5 |
|
.SH SYNOPSIS |
6 |
|
.B obj2mesh |
7 |
|
[ |
8 |
+ |
.B "\-a matfile" |
9 |
+ |
][ |
10 |
+ |
.B "\-l matlib" |
11 |
+ |
][ |
12 |
|
.B "\-n objlim" |
13 |
|
][ |
14 |
|
.B "\-r maxres" |
29 |
|
which is sent to |
30 |
|
.I output.rtm |
31 |
|
(or standard output). |
32 |
+ |
Any RADIANCE material descriptions included via one or more |
33 |
+ |
.I \-a |
34 |
+ |
options will be compiled and stored in the mesh as well. |
35 |
+ |
If the |
36 |
+ |
.I \-l |
37 |
+ |
option is used to specify a material file, the RADIANCE library |
38 |
+ |
locations are searched. |
39 |
|
This mesh may be included in a RADIANCE scene description via the |
40 |
|
.I mesh |
41 |
|
primitive, thus: |
50 |
|
.PP |
51 |
|
The syntax and semantics are identical to the RADIANCE |
52 |
|
.I instance |
53 |
< |
primitive, except that the mesh modifier may not be "void", since |
54 |
< |
materials are not included in a compiled mesh file. |
53 |
> |
primitive. |
54 |
> |
If |
55 |
> |
.I mod |
56 |
> |
is "void", then the stored mesh materials will be applied during rendering. |
57 |
> |
Otherwise, the given material will be substituted on |
58 |
> |
all the mesh surfaces. |
59 |
|
.PP |
60 |
|
The |
61 |
|
.I \-n |
102 |
|
.I obj2mesh. |
103 |
|
Normals will be interpolated over the mesh |
104 |
|
during rendering to produce a smooth surface. |
105 |
< |
If no vertex normals are present, the mess will appear tesselated. |
105 |
> |
If no vertex normals are present, the mesh will appear tesselated. |
106 |
|
A zero length normal (i.e., 0 0 0) will generate a syntax error. |
107 |
|
.TP |
108 |
|
.BI vt " u v" |
111 |
|
to the "Lu" and "Lv" variables during rendering. |
112 |
|
Local coordinates can extend over any desired range of values. |
113 |
|
.TP |
114 |
+ |
.BI usemtl " mname" |
115 |
+ |
A material name. |
116 |
+ |
The following faces will use the named material, which is |
117 |
+ |
taken from the material definitions in the |
118 |
+ |
.I \-a |
119 |
+ |
input file(s). |
120 |
+ |
.TP |
121 |
+ |
.BI g " gname" |
122 |
+ |
Group association. |
123 |
+ |
The following faces are associated with the named group. |
124 |
+ |
If no "usemtl" statement has been |
125 |
+ |
encountered, the current group is used for the surface material |
126 |
+ |
identifier. |
127 |
+ |
.TP |
128 |
|
.BI f " v1/t1/n1 v2/t2/n2 v3/t3/n3" " .." |
129 |
|
A polygonal face. |
130 |
|
Polygon vertices are specified as three indices separated |
182 |
|
.IP "Hash table overflow in fullnode" |
183 |
|
This error is caused by too many surfaces, and there is |
184 |
|
little hope of compiling this mesh. |
185 |
< |
.SH EXAMPLE |
186 |
< |
To create a compiled triangle mesh from the scene file mesh.obj: |
185 |
> |
.SH EXAMPLES |
186 |
> |
To create a compiled triangle mesh from the scene file mesh.obj |
187 |
> |
using materials from the file mesh.mat: |
188 |
|
.IP "" .2i |
189 |
< |
oconv mesh.obj mesh.rtm |
189 |
> |
obj2mesh -a mesh.mat mesh.obj mesh.rtm |
190 |
> |
.PP |
191 |
> |
To use local coordinates to place a square tiled image on a mesh object: |
192 |
> |
.sp |
193 |
> |
.nf |
194 |
> |
void colorpict tiled_pat |
195 |
> |
7 red green blue mytile.pic . frac(Lu) frac(Lv) |
196 |
> |
0 |
197 |
> |
0 |
198 |
> |
|
199 |
> |
tiled_pat plastic tiled_mat |
200 |
> |
0 |
201 |
> |
0 |
202 |
> |
5 .9 .9 .9 0 0 |
203 |
> |
|
204 |
> |
tiled_mat mesh tiled_mesh |
205 |
> |
1 mymesh.rtm |
206 |
> |
0 |
207 |
> |
0 |
208 |
> |
.fi |
209 |
> |
.SH ENVIRONMENT |
210 |
> |
RAYPATH the directories to search for material files. |
211 |
|
.SH AUTHOR |
212 |
|
Greg Ward |
213 |
|
.SH "SEE ALSO" |
214 |
|
gensurf(1), getinfo(1), make(1), obj2rad(1), |
215 |
< |
oconv(1), rpict(1), rview(1), rtrace(1), xform(1) |
215 |
> |
oconv(1), rpict(1), rvu(1), rtrace(1), xform(1) |