Joerg 'Herkules' Plewe wrote:
> BUT, doing a 800x600 double buffer consumes about 50% CPU of a
> Pentium/350Mhz when running with 25fps only! The big image about the same
> time! So WHY is drawImage THAT slow? Are there any means to speed that up?
> How can I understand that? There is no alpha nor transparency involved.
A lot of this has to do with the way that Java2D has been implemented. I
remember at the Java2D BOF the Sun people stating that all of the 2D
routines were moved from native code in 1.1 to pure java in 1.2.
Obviously, without hardware accel on simple things like line drawing and
polygon fills, things become a lot slower. They stated that the intent
was to move back to native code for 1.3.
As for the image blitting, there are a number of potential reasons for
this. You might want to check out the bug fix list for JDK 1.3. IIRC,
there was a bunch of bugs where loops were doing things differently
depending on how many components the image had and therefore the number
of loop iterations tha were being done. Supposedly drawImage is much
faster in 1.3 (Haven't checked to confirm).
--
Justin Couch Author, Java Hacker
Snr Software Engineer [EMAIL PROTECTED]
ADI Ltd, Systems Group http://www.vlc.com.au/~justin/
Java3D FAQ: http://tintoy.ncsa.uiuc.edu/~srp/java3d/faq.html
-------------------------------------------------------------------
"Look through the lens, and the light breaks down into many lights.
Turn it or move it, and a new set of arrangements appears... is it
a single light or many lights, lights that one must know how to
distinguish, recognise and appreciate? Is it one light with many
frames or one frame for many lights?" -Subcomandante Marcos
-------------------------------------------------------------------
===========================================================================
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".
