5 |
|
.SH SYNOPSIS |
6 |
|
.B obj2mesh |
7 |
|
[ |
8 |
< |
.B "\-a matinput" |
8 |
> |
.B "\-a matfile" |
9 |
|
][ |
10 |
+ |
.B "\-l matlib" |
11 |
+ |
][ |
12 |
|
.B "\-n objlim" |
13 |
|
][ |
14 |
|
.B "\-r maxres" |
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: |
61 |
|
.I \-n |
62 |
|
option specifies the maximum surface set size for |
63 |
|
each voxel. |
64 |
< |
Larger numbers result in quicker mesh generation needing |
65 |
< |
less memory, but potentially slower rendering. |
60 |
< |
Smaller values may produce faster renderings, |
61 |
< |
since the default number (15) is on the high side to reduce |
62 |
< |
the compiled mesh octree size. |
64 |
> |
Larger numbers result in quicker mesh generation, |
65 |
> |
but potentially slower rendering. |
66 |
|
Values below 6 are not recommended, since this is the median |
67 |
|
valence for a mesh vertex (the number of adjacent faces), |
68 |
|
and smaller values will result in pointless octree subdivision. |
69 |
+ |
The default setting is 9. |
70 |
|
.PP |
71 |
|
The |
72 |
|
.I \-r |
100 |
|
.I obj2mesh. |
101 |
|
Normals will be interpolated over the mesh |
102 |
|
during rendering to produce a smooth surface. |
103 |
< |
If no vertex normals are present, the mess will appear tesselated. |
103 |
> |
If no vertex normals are present, the mesh will appear tesselated. |
104 |
|
A zero length normal (i.e., 0 0 0) will generate a syntax error. |
105 |
|
.TP |
106 |
|
.BI vt " u v" |
180 |
|
.IP "Hash table overflow in fullnode" |
181 |
|
This error is caused by too many surfaces, and there is |
182 |
|
little hope of compiling this mesh. |
183 |
< |
.SH EXAMPLE |
183 |
> |
.SH EXAMPLES |
184 |
|
To create a compiled triangle mesh from the scene file mesh.obj |
185 |
|
using materials from the file mesh.mat: |
186 |
|
.IP "" .2i |
187 |
|
obj2mesh -a mesh.mat mesh.obj mesh.rtm |
188 |
+ |
.PP |
189 |
+ |
To use local coordinates to place a square tiled image on a mesh object: |
190 |
+ |
.sp |
191 |
+ |
.nf |
192 |
+ |
void colorpict tiled_pat |
193 |
+ |
7 red green blue mytile.pic . frac(Lu) frac(Lv) |
194 |
+ |
0 |
195 |
+ |
0 |
196 |
+ |
|
197 |
+ |
tiled_pat plastic tiled_mat |
198 |
+ |
0 |
199 |
+ |
0 |
200 |
+ |
5 .9 .9 .9 0 0 |
201 |
+ |
|
202 |
+ |
tiled_mat mesh tiled_mesh |
203 |
+ |
1 mymesh.rtm |
204 |
+ |
0 |
205 |
+ |
0 |
206 |
+ |
.fi |
207 |
+ |
.SH ENVIRONMENT |
208 |
+ |
RAYPATH the directories to search for material files. |
209 |
|
.SH AUTHOR |
210 |
|
Greg Ward |
211 |
|
.SH "SEE ALSO" |
212 |
|
gensurf(1), getinfo(1), make(1), obj2rad(1), |
213 |
< |
oconv(1), rpict(1), rview(1), rtrace(1), xform(1) |
213 |
> |
oconv(1), rpict(1), rvu(1), rtrace(1), xform(1) |