Re: [JAVA3D] Memory Issues

r 06, 2000 6:09 PM To: [EMAIL PROTECTED] Subject: RE: [JAVA3D] Memory Issues Ah, OK. So give me more. In the first case you are using indexed triangles with vertex and normal data? Or do you have texture coordinates and colors also? You seem to be assuming that the extra memory usage is comi

Re: [JAVA3D] Memory Issues: same number of normals and coordinate s, even for indexed Geometry?

n Behalf Of Kevin Rushforth > > Sent: Monday, November 06, 2000 11:29 AM > > To: [EMAIL PROTECTED] > > Subject: Re: [JAVA3D] Memory Issues: same number of normals and > > coordinate s, even for indexed Geometry? > > > > This is a known limitation of the Indexed

Re: [JAVA3D] Memory Issues: same number of normals and coordinate s, even for indexed Geometry?

, 2000 9:55 AM To: [EMAIL PROTECTED] Subject: Re: [JAVA3D] Memory Issues: same number of normals and coordinates, even for indexed Geometry? I would vote for this one ... it would be very useful to introduce this feature - it would simplify life a bit :) just a bit . I VOTE Peter. Adam Tegen

Re: [JAVA3D] Memory Issues: same number of normals and coordinate s, even for indexed Geometry?

e that sometime *soon*, J3D should take a hard look at memory consumption. -Lee -Original Message- From: Mark Ferneau [mailto:[EMAIL PROTECTED]] Sent: Monday, November 06, 2000 2:08 PM To: [EMAIL PROTECTED] Subject: Re: [JAVA3D] Memory Issues: same number of normals and coordinates, e

Re: [JAVA3D] Memory Issues: same number of normals and coordinates, even for indexed Geometry?

ntinued dialog. Adam -Original Message- From: Discussion list for Java 3D API [mailto:[EMAIL PROTECTED]]On Behalf Of Kevin Rushforth Sent: Monday, November 06, 2000 11:29 AM To: [EMAIL PROTECTED] Subject: Re: [JAVA3D] Memory Issues: same number of normals and coordinate s, even for indexed

Re: [JAVA3D] Memory Issues: same number of normals and coordinates, even for indexed Geometry?

; From: Discussion list for Java 3D API > > [mailto:[EMAIL PROTECTED]]On Behalf Of Kevin Rushforth > > Sent: Monday, November 06, 2000 11:29 AM > > To: [EMAIL PROTECTED] > > Subject: Re: [JAVA3D] Memory Issues: same number of normals and > > coordinate s, even for inde

Re: [JAVA3D] Memory Issues: same number of normals and coordinates, even for indexed Geometry?

om: Discussion list for Java 3D API > [mailto:[EMAIL PROTECTED]]On Behalf Of Kevin Rushforth > Sent: Monday, November 06, 2000 11:29 AM > To: [EMAIL PROTECTED] > Subject: Re: [JAVA3D] Memory Issues: same number of normals and > coordinate s, even for indexed Geometry? > > This is

Re: [JAVA3D] Memory Issues: same number of normals and coordinates, even for indexed Geometry?

> > Adam > > -Original Message- > From: Discussion list for Java 3D API > [mailto:[EMAIL PROTECTED]]On Behalf Of Kevin Rushforth > Sent: Monday, November 06, 2000 11:29 AM > To: [EMAIL PROTECTED] > Subject: Re: [JAVA3D] Memory Issues: same number of normals and > coordinate s,

Re: [JAVA3D] Memory Issues: same number of normals and coordinate s, even for indexed Geometry?

Monday, November 06, 2000 12:15 PM > To: [EMAIL PROTECTED] > Subject: Re: [JAVA3D] Memory Issues: same number of normals and > coordinate s, even for indexed Geometry? > > Thanks for responding. > > Does anyone else listening to this discussion thi

Re: [JAVA3D] Memory Issues: same number of normals and coordinate s, even for indexed Geometry?

: Re: [JAVA3D] Memory Issues: same number of normals and coordinate s, even for indexed Geometry? This is a known limitation of the IndexedGeometryArray API. The lengths of the coordinates, colors, normal, texcoord arrays must be the same even for IndexedGeometryArray objects. We could look into

Re: [JAVA3D] Memory Issues: same number of normals and coordinate s, even for indexed Geometry?

quot;J. Lee Dixon" <[EMAIL PROTECTED]> >Subject: Re: [JAVA3D] Memory Issues: same number of normals and coordinate > s, > even for indexed Geometry? >To: [EMAIL PROTECTED] > >Yep, I can definitely agree with you there. If you are using an

Re: [JAVA3D] Memory Issues: same number of normals and coordinate s, even for indexed Geometry?

an exception. This makes no sense for indexing. Can somebody at Sun PLEASE address this design issue??? -Lee -Original Message- From: Adam Tegen [mailto:[EMAIL PROTECTED]] Sent: Friday, November 03, 2000 5:34 PM To: [EMAIL PROTECTED] Subject: Re: [JAVA3D] Memory Issues: same number

Re: [JAVA3D] Memory Issues: same number of normals and coordinate s, even for indexed Geometry?

hing. XSG, for instance, doesn't care. Thanks much, Adam -Original Message- From: Discussion list for Java 3D API [mailto:[EMAIL PROTECTED]]On Behalf Of J. Lee Dixon Sent: Friday, November 03, 2000 4:55 PM To: [EMAIL PROTECTED] Subject: Re: [JAVA3D] Memory Issues: same number

Re: [JAVA3D] Memory Issues: same number of normals and coordinate s, even for indexed Geometry?

PROTECTED] Subject: Re: [JAVA3D] Memory Issues: same number of normals and coordinate s, even for indexed Geometry? A further question: A "Vertex" is a combination of coordinate, normal, etc. right? If you have an IndexedGeometryArray, why does the number of normals need to equal the number

Re: [JAVA3D] Memory Issues: same number of normals and coordinate s, even for indexed Geometry?

like cubes. -Lee -Original Message- From: Adam Tegen [mailto:[EMAIL PROTECTED]] Sent: Friday, November 03, 2000 12:11 PM To: [EMAIL PROTECTED] Subject: [JAVA3D] Memory Issues: same number of normals and coordinates, even for indexed Geometry? Hello- I'm doing some tests with Jav

Re: [JAVA3D] Memory Issues: same number of normals and coordinate s, even for indexed Geometry?

]] Sent: Friday, November 03, 2000 12:11 PM To: [EMAIL PROTECTED] Subject: [JAVA3D] Memory Issues: same number of normals and coordinates, even for indexed Geometry? Hello- I'm doing some tests with Java3D and notices something: The number of coordinates must equal the number of normals

[JAVA3D] Memory Issues: same number of normals and coordinates, even for indexed Geometry?

Hello- I'm doing some tests with Java3D and notices something: The number of coordinates must equal the number of normals (when enabled) etc. At least this is how it seems to be when I use commands like IndexedTriangleArray.setNormalRefFloat(...) While this makes sense for non-indexed geometry