Hi Paul,

Very nice to hear from you and, as last year, much appreciate your
illustrative example.

OK ! The reason why I was a little curious about the getIndexedGeometryArray()
taking a longer time when one sets the USE_COORD_INDEX_ONLY bit is
because of the following:

1. I am feeding in only unindexed tri-coordinates to GeometryInfo. Actually,
   if you see my immediately preceding post today, it gives you the
   code snippet.
2. I am running NormalGenerator on GeometryInfo which would automatically
   converted un-indexed tris to indexed ones.
3. So, at the time when I call the getIndexedGeometryArray(), everything
   is already in place with respect to the indices. All now this
   method has to do is grab everything from Step 2. In fact, it should
   be faster to the extent that it doesn't have to create an indices
   array for the normals and set it on the IndexedTriangleArray.

Good luck with everything, and hope to see you on this Forum
more frequently.

Regards

Raj








>On Thu, 11 Apr 2002 12:59:14 -0700, Paul Pantera <[EMAIL PROTECTED]> wrote:

>> Date:    Wed, 10 Apr 2002 17:20:11 +0300
>> From:    Asaf Dafner <[EMAIL PROTECTED]>
>> Subject: Re: Signed auto-installation JAR from Sun
>>
>> Hi,
>>
>> This is for Paul Pantera or anyone from Sun: Any chance you could provide
>> <something> saying you are still working on the "auto-install" ?
>> A date will be great, a deadline would be helpful, a general vicinity would be
>> appreciated, a no-later-than-September will be fine and a "Please continue
>> being patient" will also do.
>>
>> Thanx,
>> Asaf.
>>
>> P.S, Godlets from "J3d": The process described in Paul's
>> http://www.j3d.org/tutorials/quick_fix/auto_install.html article apparently
>> doesn't work (as Daniel Selman says in his book <Thanx Daniel>), and is illegal
>> anyhow, so why publish it, and why tell everybody here on the list to try it?
>
>I don't work for Sun any more.  I'm currently looking for a new project.
>
>Yes, the auto_install.html document should probably be removed from
>j3d.org.  There's currently no way to automatically install Java 3D
>over the internet, as far as I know.  The signed jar method could be
>used on an Intranet, however, but without reverse-ip address lookup,
>it can't go an the Internet.
>
>> Date:    Wed, 10 Apr 2002 20:38:17 +0200
>> From:    Artur Biesiadowski <[EMAIL PROTECTED]>
>> Subject: GeometryInfo - CoordIndexOnly and other problems
>>
>> Is this possible to force GeometryInfo to output IndexedGeometryArray
>> with USE_COORDINATE_INDEX_ONLY set ? I can use it to give only single
>> array of indices to GeometryInfo, they are processed correctly, but on
>> creation of IndexedGeometryArray this state seems to be lost.
>>
>> It seems that
>>
>> if (prim == POLYGON_ARRAY) {
>>           if (tr == null) tr = new Triangulator();
>>           tr.triangulate(this);
>>        } else changeBackToOldPrim();
>>
>> always changes format to normal index. ChangeBackToOldPrim calls
>> convertToIndexedTriangles() which in turns calls indexify() which means
>> indexify(false) - and usecoordonly bit is cleared. IMHO
>> indexify(coordOnly) should be called in convertToIndexedTriangles() to
>> not loose state.
>
>If you are using the stripifier then it won't change the primitive
>back to what it was originally.  The stripifier calls forgetOldPrim(),
>so changeBackToOldPrim() will do nothing.  So USE_COORD_INDEX_ONLY
>should work perfectly if you're using the stripifier.
>
>If you're not calling the stripifier, then it has to change to normal
>indexed triangles because the routines that convert back to the
>original primitive only know how to convert from indexed triangles
>to the original primitive.
>
>So there is a bug, but it's different from what you said.  For
>the case where the geometry is being converted back to the
>original primitive, indexify(useCoordIndexOnly) should be called
>after changeBackToOldPrim().
>
>>
>> Next problem is that compact does not compact identical
>> vertex/normal/tex/color sets.
>
>True.  This is noted in the TODO comment above compactData.  Note that
>the javadoc for compact() doesn't say it removes duplicates.
>
>> Currently I do it by hand before passing
>> data to GeometryInfo, but I suppose that most people are not aware of
>> this problem. I also do not understand why USE_INDEX_COORD_ONLY
>> geometries do not have to be compacted - it is perfectly legal for them
>> to have unused entries also - if they were specified with coord_only
>> from every start (as opposed to converted to this format later).
>
>True.  Support for USE_COORD_INDEX_ONLY should be added to compact().
>
>> I
>> suppose that calling indexify(false) and then indexify(true) should have
>> same effect, but this should be documented.
>
>You'd have to call compact() inbetween the two calls to indexify.
>
>> Date:    Wed, 10 Apr 2002 12:58:04 -0600
>> From:    Raj Vaidya <[EMAIL PROTECTED]>
>> Subject: Re: GeometryInfo - CoordIndexOnly and other problems
>>
>[. . .]
>> What I did find though was that if you specified the COORD_INDEX_ONLY
>> flag while retrieving the IndexedGeometryArray, it takes a much
>> longer processing time than if you didn't. This is surprising since
>> the geometry would have already been converted to indexed triangles.
>>
>> Don't know.....someone else probably does
>
>It takes a long time because it has to copy all of your data around.
>Take an example of two triangles:
>
>3 __2
>|\  |
>| \ |
>|__\|
>0   1
>    Coord     Color
>0   (0,0,0)   (1,0,0)
>1   (1,0,0)   (0,1,0)
>2   (1,1,0)   (0,0,1)
>3   (0,1,0)
>
>    CoordIdx  ColorIdx
>0     0        0
>1     1        1
>2     3        2
>3     1        1
>4     2        1
>5     3        2
>
>Convert to USE_COORD_INDEX_ONLY:
>
>    Coord     Color
>0   (0,0,0)   (1,0,0)
>1   (1,0,0)   (0,1,0)
>2   (0,1,0)   (0,0,1)
>3   (1,1,0)   (0,1,0)
>4   (0,1,0)   (0,0,1)
>
>    Idx
>0     0
>1     1
>2     2
>3     1
>4     3
>5     4
>
>Notice how the Coord and Color tables needed to be rebuilt to accomidate
>the new index table.  Through the Magic of Java you don't have to actually
>copy the data, but you do have to build new tables.
>
>-Paul
>
> ==========================================================================
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff JAVA3D-INTEREST".  For general help, send email to
>[EMAIL PROTECTED] and include in the body of the message "help".

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to