Some more questions...
1. Are there any meta-commands which may not appear in the geometry sections? Is, for example, nesting !TEXMAP blocks in the same file supported?
0 !TEXMAP START PLANAR ...
0 !: 1 16 0 0 0 1 0 0 0 1 0 0 0 1 somepart.dat
0 !TEXMAP START PLANAR ...
0 !: 1 16 0 0 0 1 0 0 0 1 0 0 0 1 someotherpart.dat
0 !TEXMAP END
0 !TEXMAP END
2. Is there any intention that the texture-image paths should support absolute filepaths? We do support these for type-1 lines (although that doesn't necessarily mean we need to for textures).
3. Is it the case that you use either geometry1+geometry3 or geometry2, or can you use geometry2 in combination with either of the others?
4. The description states that "If an END command given in a sub file stops the use of a texture specified in a calling file, then that texture will be restored to use when the sub file is exited." Does this mean that you can use "0 !TEXMAP END" in a file without it being preceded (in the same file) by an "0 !TEXMAP START"?
1. Are there any meta-commands which may not appear in the geometry sections? Is, for example, nesting !TEXMAP blocks in the same file supported?
0 !TEXMAP START PLANAR ...
0 !: 1 16 0 0 0 1 0 0 0 1 0 0 0 1 somepart.dat
0 !TEXMAP START PLANAR ...
0 !: 1 16 0 0 0 1 0 0 0 1 0 0 0 1 someotherpart.dat
0 !TEXMAP END
0 !TEXMAP END
2. Is there any intention that the texture-image paths should support absolute filepaths? We do support these for type-1 lines (although that doesn't necessarily mean we need to for textures).
3. Is it the case that you use either geometry1+geometry3 or geometry2, or can you use geometry2 in combination with either of the others?
4. The description states that "If an END command given in a sub file stops the use of a texture specified in a calling file, then that texture will be restored to use when the sub file is exited." Does this mean that you can use "0 !TEXMAP END" in a file without it being preceded (in the same file) by an "0 !TEXMAP START"?