This solved my gc problem and now the geometry changes are very fast !
Thank you very very much ;-)
Alessandro
Tarlton Mark-CMT041 escreveu:
I ran into a similar problem earlier this year and the advice from Justin and Kevin Chung was to be sure to use the "IndexedTriangleArray.USE_COORD_INDEX_ONLY" with "GeometryArray.BY_REFERENCE"The reasoning is that IndexedGeometryArray is implemented using OpenGL vertex array calls or the DirectX equivalent. The OGL vertex array calls assume that a single index is used to select vertex coordinates, normals, texture coords, colors, etc. Java3D must generate a data structure that meets this requirement from the data that you supply. If you edit the coordinate values, Java3D will discard the old array and gen up a new array. I was seeing massive garbage collection in my app until I converted my data structures to use only the single index for all vertex information. That solved my problem. Mark -----Original Message----- From: Dirk L. van Krimpen [mailto:[EMAIL PROTECTED]] Sent: Monday, August 18, 2003 3:02 AM To: [EMAIL PROTECTED] Subject: Re: [JAVA3D] excessive GC on GeometryUpdate ----- Original Message ----- From: "Alessandro borges" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, August 17, 2003 2:04 PM Subject: [JAVA3D] excessive GC on GeometryUpdate Hi Allesandro, Although I am using by_reference with IndexedGeometryArray a lot I never checked the resulting GC, so I cannot give you a useful answer. Maybe this would be a good one for Florin Herinean to answer. So, I tought this would be a good moment to mention that it is good to have some experienced guys like you and Florin around. As a matter of fact, I learned most 3D tricks and methods from both of you. Have you got an idea if Florin is still on the list? Perhaps he is away on such a usual long German vacation. Anyhow, I am willing to measure my amounts of GC under various conditions if you only tell me how to check this. Have fun, DirkHi, I am doing some geometry updates in a by_reference IndexedGeometryArry, but there are excessive GC. I did some memory debugs and found tons of Point3d and BoundingBox garbages. Of course this objects are generated/garbage collected by GeometryArray after I call geometryUpdater ... The strange point is by using Morph does happen ANY GC !!! Should I use a kind of Morph to have less gc ? Any comment will be very welcome. Alessandro _______________________________________________________________________ Conheça o novo Cadê? - Mais rápido, mais fácil e mais preciso. Toda a web, 42 milhões de páginas brasileiras e nova busca por imagens! http://www.cade.com.br===========================================================================To unsubscribe, send email to [EMAIL PROTECTED] and include in thebodyof 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". =========================================================================== 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".
