The only scene file changes that do not require octree regeneration are modifications to non-surface parameters. If the coordinates of a surface are changed, or any primitives are added or deleted, oconv must be run again. Although the octree file format is binary, it is meant to be portable between machines. The only limitation is that machines with radically different integer sizes will not work together. For the best results, the -f option should be used if an octree is to be used in different environments.
Most errors are self-explanatory.
This error occurs when too many surfaces are close together in a scene. Either too many surfaces are lying right on top of each other, or the bounding cube is inflated from an oversized object or an improper -b specification. This error is caused by too many surfaces. If it is possible to create an octree for the scene at all, it will have to be done in stages using the -i option. In the octree, the names of the scene files are stored rather than the scene information.