I have seen similar behavior under Windows 2000 where a Java 3D program
runs with software rendering while an OpenGL program runs with hardware
acceleration. In addition the Java 3D program causes all the windows on
the screen to redraw frequently at random intervals (maybe some weird
artifact of the software OpenGL implementation). For me these problems
always occurs in 16 bit color mode. Try switching to 32 bit color mode.
On the systems I have tried this on Java 3D runs fine in 32 bit color mode.
None the less this is odd behavior, and seems like a bug in Java 3D. It
should generally be easier for the hardware acceleration to kick in in
16 bit color, not harder, since a 16 bit display uses less video memory
and requires less video memory bandwidth. For example I am currently
using an Nvidia TNT2 M64 card, essentially a gaming card, which if
anything should be happier with 16 bit versus 32 bit color. However it
is actually many times faster in 32 bit color than 16 bit color with
Java 3D applications. Maybe Java 3D is asking OpenGL for some weird
setting that doesn't mix with 16 bit color, which causes the OpenGL
driver to fall back to software rendering. This is what OpenGL is
supposed to do whenever the application asks for something that the
hardware doesn't support. As I said, seems like a bug in Java 3D.
Karl Fischer
Mauricio Vives wrote:
> Hey folks,
>
> I am developing a Java 3D-based applet, and this applet is running on a
> variety of Windows 2000 systems that support OpenGL hardware acceleration
> (which I have been able to detect with C++ code). However, my applet seems
> to always use the Microsoft software implementation of OpenGL instead of
> hardware-accelerated OpenGL. This results in very slow rendering, even for
> simple geometry. The slow rendering is particularly noticeable when
> textures are used. Since it is very easy for me to get a C++ application to
> use hardware-accelerated OpenGL on these machines, I am almost certain the
> problem lies with Java 3D.
>
> Why would an applet use software-based OpenGL instead of
> hardware-accelerated OpenGL? Is there even a way to direct an applet to use
> hardware-accelerated OpenGL? (I did not see any mention of this in the Java
> 3D spec) If not, is it at least possible to detect for sure whether an
> applet is using hardware-accelerated OpenGL?
>
> Thanks in advance for any info you can give me.
>
> - Mauricio
>
> ===========================================================================
> 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".
