My program was blowing up horribly (That is, it ran, but the geometry was completely screwed up, and the CPU usage went through the roof) when one of my IndexedTriangleArrays got more than 10924 triangles, but not when it had 10922.
(And it took a hell of a lot of effort to work out that that was what was happening, rather than a bug in my geometry creation code.) That looked like a random number, until I remembered that triangles have 3 vertices, and so the critical numbers are 32772 and 32766 vertices. 2^15 = 32768. So it seems that geometry arrays are getting indexed by a signed short somewhere along the way, and this is overflowing. Does this ring a bell with anyone? Is it documented anywhere? Any workarounds? (Well, obviously, put the geometry in more than one Array, I suppose.) Thanks, Tim. =========================================================================== 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".
