You should have a look at the parameters of the JVM, especially the -Xmx parameter.
On Wed, 15 Oct 2003 15:35:23 -0400, Nicholas Pappas <[EMAIL PROTECTED]> wrote:
Hello all!
I have just started working with Java3D and am wondering about any limitations in objects, in terms of memory, and ways I can improve (i.e., decrease) any memory requirements of a viewer I am writing. The program I am using decodes an existing game file. It then reconstructs the model so you can interact with it. Just like the many viewers for Quack model files. These files define several planes which are then textured. In one case, there are 14,581 planes with textures -- this file I can render and show. But two others I've tried have 25,554 and 21,964 -- both of which give me a OutOfMemery error, or just crash my computer. :( There are 16 texture files, loaded into 16 Appearance nodes (1 each). I am using QuadArray for the Geometry. Is there a limit to the number of Shape3D objects I can safely place? Does anyone have any suggestions on how I can save on memory requirements?
Thanks for any 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".
-- -- Virtual Worlds Productions Software Development Group http://www.virtualworlds.de
=========================================================================== 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".
