|
I have not worked with these for a while but as i understand
this, you only need to store as many color as needed, each vertice using an
index to its color, I do not see any waste there...I repeat, i may be wrong : I
have not touch this area for a while:
The only waste I can seen till now is the absence of a "grid
mode" :in java3d you need to repeat x,y,z for each points even if the x/y are at
even interval but that does not seem to be you case....
You may also want to consider strip* type of storage which may
suit you better..check these
my 2c (only) worth of advice
Olivier Fillon Minestar Project [EMAIL PROTECTED] Mincom
Limited
Ph.+61-7-3303-3344
61 Wyandra
Street Fax+61-7-3303-3232
Teneriffe Qld. 4005. Australia Company home page: http://www.mincom.com/Personal home page:
http://www.powerup.com.au/~fillon---
A word from our sponsor --- This transmission is for the intended addressee
only and is confidential information. If you have received this transmission
in error, please delete it and notify the sender. The contents of this E-mail
are the opinion of the writer only and are not endorsed by Mincom Limited
unless expressly stated otherwise.
--
Hi,
We are considering using Java3D for visualization purposes. So fare we have
relied on using iris explorer for our visualization need in our
solutions. A common need is to visualize parameters on a surface which when it
hit the visualization is composed of triangles with parameter values defined
at the vertices.
What I think is the right Geometry object to use is IndexedTriangleArray,
possible one of its subclasses depending on the meshs topology.
One problem with these classes is that the way I have understood them they
do not store data as memory eficient as one may have hoped for, related to the
fact that all the data array must be of equal length: 'number of
vertices'.
The most 'sparse' array is likely to be the color data array. Here you
store a color map which you indices into refers to as a function of which
color that vertexs parameter mapped to. This color table is going to have
fare fewer entries then there are vertices, still the length of this
array must be the number of vertices.
One question I have (given that the above understanding is right): When one
gets Java3D based on the 1.2 spec. and have the posibility to have Geometry
refer data will this change: i.e. may the data arrays be of non equal length?
If any body read this and see I have misunderstood something (I have only
now started learning Java3D) I would be happy to be told, the samething goes
for my question...
Arne Halvorsen,
BSSI
e-mail: [EMAIL PROTECTED]
| 