Dear Fred,
I have been struggling with this kind of problem for 2 months. DX does not
seem to care much for closed surfaces (eg. {Connect} will fail because it
expects an open surface with a single, all-purpose normal).
I have been experimenting on a somewhat more complex geometry than your
sounds, and I have just verified a new approach. I write a file that
contains 3 sets of coords: 1 representing the surface, 1 representing an
inner layer, and 1 representing an outer layer. The data component is then
a flag: "0" for the actual surface, "1" for the inner layer, and "-1" for
the outer layer. I then use {AutoGrid} to form a cubic grid and
{Isosurface} (with <value> set to "0") to render the surface.
It sort of works, but is a bit patchy and glitchy, and wastes time and
memory, so I'm trying to figure out where to go next.
I think you can forget about an elegant, generic solution to this problem
until some one writes such a module.
I would be interested in the technique you used to form the connections,
because I think native DX format will turn out to be the only way I can get
satisfaction.
P.S. I'm a relative newby, so don't put too much weight on my advice.
Regards,
Allen H. Nugent
Graduate School of Biomedical Engineering
University of New South Wales
Sydney NSW 2052 Australia
Tel: +61 2 9385 3916 Fax: +61 2 9663 2108
