Mark,
I have taken care of the java.lang.IllegalStateException:
GeometryDecompressorRetained: error.
Its because I was using the decompressor sample (cgview.java) which
after
reading the Compressed node , also expects a default material property.
I assigned a default property and it works fine now.
About the OutofMemory issue, the exact trace is :
java obj2cg /tmp/a.obj /tmp/a.cg
Exception in thread "main" java.lang.OutOfMemoryError
344 at
com.sun.j3d.utils.compression.CompressionStream.addGeometryArray (
Compiled Code )
345 at com.sun.j3d.utils.compression.CompressionStream. < init > (
Compiled Code )
346 at ObjectFileCompressor.getStream ( Compiled Code )
If I turn on the Stripify option
java -Xmx20000000 obj2cg /tmp/a.obj /tmp/a.cg
Exception in thread "main" java.lang.OutOfMemoryError
at com.sun.j3d.utils.geometry.Stripifier.howFar(Compiled Code)
at com.sun.j3d.utils.geometry.Stripifier.stripify(Compiled Code)
at CaddsObjFile.addScene(Compiled Code)
at CaddsObjFile.readEnd(Compiled Code)
at CaddsObjFile.readFile(Compiled Code)
at CaddsObjFile.load(Compiled Code)
at CaddsObjFile.load(Compiled Code)
at ObjectFileCompressor.getScene(Compiled Code)
at ObjectFileCompressor.compress(Compiled Code)
at obj2cg.main(Compiled Code)
Turn off the Stripify, Triangulate options.
java -Xmx40000000 obj2cg /tmp/a.obj /tmp/a.cg
Exception in thread "main" java.lang.OutOfMemoryError
at
com.sun.j3d.utils.compression.CompressionStream.addVertex(Compiled Code)
at
com.sun.j3d.utils.compression.CompressionStream.addGeometryArray(Compiled
Code)
at
com.sun.j3d.utils.compression.CompressionStream.<init>(Compiled Code)
at ObjectFileCompressor.getStream(Compiled Code)
at ObjectFileCompressor.compressScene(Compiled Code)
at ObjectFileCompressor.compress(Compiled Code)
at obj2cg.main(Compiled Code)
I guess , I will have to rewrite the compressor /decompressor for my
specific format.
This is because the compressor creates reads all the triangle info
(15MB) and keeps
it in the memory Array. What I have done is broken the triangle info
into smaller Meshes and create sepeate Sahpe3D objects for them. The
compressor should output them to a file when it hits the end of a mesh
and clear of the memory.
I can send u a sample format file or a large real world file in case u
want to
try out this.
Also can u tell me what are the tips to increase the performance in
1. Creating such a scene graph
2. Rendering the scene graph ( Compiled branch nodes ??)
Thanx for all the help.
--
Rajesh Jain ([EMAIL PROTECTED])
Parametric Technology Corp
http://www.ptc.com
Mark Hood wrote:
>
> > Date: Sat, 9 Oct 1999 17:19:22 +0530
> > From: Rajesh Jain <[EMAIL PROTECTED]>
> >
> > I tried to write a compresser and decompressor for this.
> > The compressor , derived from my Loader class, works fine
> > in compressing the data.
> >
> > During decompressor I have a error message thats thown up
> > during the scene rendering
> >
> > java.lang.IllegalStateException: GeometryDecompressorRetained:
> > unexpected color in compressed buffer
> > at
> > javax.media.j3d.GeometryDecompressorRetained.outputColor(Compiled Code)
> > at javax.media.j3d.GeometryDecompressor.processSetColor(Compiled
> > Code)
> >
> > [..]
> >
> > I have no color information in my format.
>
> This error results when the GeometryArray that the decompressor was trying
> to output was created with a format that didn't specify colors, yet what
> appeared to be a color was nonetheless encountered in the compressed data.
>
> This could be a bug either in the Java 3D decompressor or in your compressor
> implementation; it's not possible to tell with the given information. If
> your compressor was derived from the ObjectFileCompressor example code, then
> it's possible that you may be getting default colors provided by the
> ObjectFile superclass which you're not accounting for in creating the
> compressed data. Try using the CompressedGeometryFile class to write out a
> .cg file of one of your smaller models and send it to me, and I'll take a
> look at it.
>
> We hope to have some compression verification tools available in a future
> release of Java 3D.
>
> > Also during compression of huge models (20MB data) I sometimes get error
> > OutOfMemmory
> > I am working on a Sun Ultra 60/1GB RAM
>
> I haven't tried compressing anything that large myself yet. I'll try a few
> larger models with the Java 3D compressor and see what the memory
> consumption looks like. Try using the -Xmx switch to the Java interpreter
> to increase the size of the virtual machine if you're not doing that
> already.
>
> We're actively maintaining and improving the Java 3D compressed geometry
> utilities. If you can verify memory leaks, performance problems, or other
> bugs in the Java 3D compressor, let us know and we'll try to fix them.
>
> -- Mark Hood
>
> ===========================================================================
> 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".
