Understanding oconv -i


#1

I’m looking for some clarification on the oconv -i option. This allows you to add an existing octree to a new octree. My question is whether the existing octree is fully integrated into the new one, or whether it remains a separate octree structure, similar to an instance in a rad file. Also, does the behavior change for frozen octrees?


#2

The result should be the same as creating the octree in one go with the new files. There is no sub-structure or any complication of the sort. Note that the original octree boundary (cube) must encompass the new scene objects. This is why you can specify the original scene cube with the -b option, by the way.

Frozen octrees on the input force a frozen octree on the output, and a warning is issued if the -f option isn’t given on the command-line with -i.