Chris,
Some years ago I made some fixes/additions to the DXtoVRML
exporter (there was a bug with PER_VERTEX colors and I added
texture mapping). Since I don't use DX anymore I haven't tried
to re-compile it under OpenDX but if you're interested I
could send you the source.
I once wrote a DX importer for Performer, but it only handles
geometry. I could provide this if anybody's interested.
-ballard
Original post from:
> Randall Hopper (mailto:[EMAIL PROTECTED])
Lockheed Martin Operation Support
EPA Scientific Visualization Center
> US EPA N127-01; RTP, NC 27711
I appreciate the offer, but I'm not sure I'm the best one to get that
code. Maybe it should be added to the code base in some way, that
either Randy (who has been working hard on this sort of thing
recently) or David T. could advise.
I'm told that our current CAVE system accepts Open Inventor "objects"
(scene graphs, whatever they call them), thus my interest in
exporting. I don't know the difference between an Open Inventor
"thing" and a VRML "thing". I'm currently exporting VRML, but our
hope is to move beyond static exported objects to dynamic CAVE-based,
multi-wall, stereo interactivity. I'm of course pushing for doing
this based on openDX (even though I don't really have a clue of how
we're going to interface to the CAVE libraries yet). Others are
pushing for other techniques, as yet undefined, though possibly VTK,
and/or python-based.
--
Chris Pelkie
Scientific Visualization Producer
618 Rhodes Hall Cornell Theory Center, Cornell University
Ithaca, NY 14853
