| 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: |
| 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 tesselation. |
| 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 |
