| 1 |
< |
.\" RCSid "$Id" |
| 1 |
> |
.\" RCSid "$Id$" |
| 2 |
|
.TH OCONV 1 8/15/95 RADIANCE |
| 3 |
|
.SH NAME |
| 4 |
|
oconv - create an octree from a RADIANCE scene description |
| 109 |
|
between machines. |
| 110 |
|
The only limitation is that machines with radically different integer |
| 111 |
|
sizes will not work together. |
| 112 |
< |
For the best results, the -f option should be used if an octree is |
| 112 |
> |
For the best results, the \-f option should be used if an octree is |
| 113 |
|
to be used in different environments. |
| 114 |
|
.SH DIAGNOSTICS |
| 115 |
|
There are four basic error types reported by oconv: |
| 132 |
|
.IP "Set overflow in addobject (id)" |
| 133 |
|
This error occurs when too many surfaces are close together in a |
| 134 |
|
scene. |
| 135 |
– |
Sometimes a dense scene can be accommodated by increasing |
| 136 |
– |
the maximum resolution (by powers of two) using the |
| 137 |
– |
.I \-r |
| 138 |
– |
option, but usually this error indicates something is wrong. |
| 135 |
|
Either too many surfaces are lying right on top of each other, |
| 136 |
|
or the bounding cube is inflated from an oversized object |
| 137 |
|
or an improper |
| 138 |
|
.I \-b |
| 139 |
|
specification. |
| 140 |
+ |
If hundreds of triangles come together at a common vertex, it may |
| 141 |
+ |
not be possible to create an octree from the object. |
| 142 |
+ |
This happens most often when inane CAD systems create spheres using |
| 143 |
+ |
a polar tessellation. |
| 144 |
|
Chances are, the surface "id" is near one of those causing the problem. |
| 145 |
|
.IP "Hash table overflow in fullnode" |
| 146 |
|
This error is caused by too many surfaces. |
| 152 |
|
To add book1, book2 and a |
| 153 |
|
transformed book3 to the octree ``scene.oct'': |
| 154 |
|
.IP "" .2i |
| 155 |
< |
oconv -i scene.oct book1 book2 '\\!xform -rz 30 book3' > newscene.oct |
| 155 |
> |
oconv \-i scene.oct book1 book2 '\\!xform \-rz 30 book3' > newscene.oct |
| 156 |
|
.SH AUTHOR |
| 157 |
|
Greg Ward |
| 158 |
|
.SH NOTES |
| 169 |
|
can be used to automate octree creation and maintenance. |
| 170 |
|
.SH "SEE ALSO" |
| 171 |
|
getbbox(1), getinfo(1), make(1), obj2mesh(1), rad(1), |
| 172 |
< |
rpict(1), rview(1), rtrace(1), xform(1) |
| 172 |
> |
rpict(1), rvu(1), rtrace(1), xform(1) |
