I used to have the same problem with the TNT and GeForce 256 based
graphics cards. The problem comes from that fact the not all the color
depth setting are hardware accelerated or Java3D only supports hardware
acceleration with 32bits color depth?
Here are the steps I would recommend to solve the problem:
1. Check if your graphics card driver support hardware accelerated OpenGL.
If you are using nVidia's chips(TNT or GeForce, etc.), download the
latest
driver. The driver comes with W2K doesn't support hardware acceleration.
2. Set the color depth to 32bits to see if the problem goes away.
3, For W2K, disable as many Visual Effects as possible. Those effects
consumes a lot of CUP resources and might cause flickering.
Hong
----- Original Message -----
From: "Jim Schatzman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, May 14, 2000 11:46 PM
Subject: [JAVA3D] Java 3D 1.2 Beta 2 vs 1.1.3 Issues
> We have observed some real show-stopper problems with all versions of J3D
1.2
> to the point where we find it unusable. Specific problems with Beta 2
include:
>
> 1. Performance. Although in some cases static compiled scenes give higher
> frame rates (about 2x) vs J3D 1.1.3, dynamically changing scenes
(primarily
> making heavy use of point arrays) run about TEN TO TWENTY TIMES SLOWER
> than J3D 1.1.3.
>
> 2. Lightweight popups. J3D 1.2 Beta 2 does not fix the lightweight popup
> problem
> where Swing popups are hidden by a Canvas 3D. Furthermore, with SOME
> video drivers, turning the lightweight popup off results in MASSIVE
FLICKERING
> which makes the final product nearly unusable. For example, we see severe
> flickering with NT4.0/Creative Annihilator Pro (GeForce256) but none with
> NT4.0/Diamond Fire GL 1 - all with JDK 1.3. Flickering also occurs in J3D
1.1.3
> but is much less severe. Letting the lightweight popup default kills the
> flickering
> but results in invisible popups.
>
> 3. When a Shape3D is removed from a live tree in J3D 1.1.3 and earlier it
can
> then be modified. In all versions of J3D 1.2, Java throws an exception
claiming
> that the Shape3D is still live. A go-around is to place the Shape3D in a
> BranchGroup
> before adding it to the tree, and then removing the BranchGroup from the
tree.
> This appears to work, but why is it necessary? It is hard to tell what is
> causing
> the performance problem (above) but this may be part of it.
>
> 4. Behaviors use SUBSTANTIAL CPU TIME when they should be idle. For
example,
> when a RotationInterpolator is added to a live tree CPU usage goes to
> nearly 100%
> on a very fast Wintel machine even though the RotationInterpolator is
disabled,
> and therefore should not be doing anything. Under J3D 1.1.3 and earlier,
> CPU is 0%
> under this circumstance.
>
> ANY IDEAS, WORK AROUNDS, PATCHES?????
>
> Thank you!!
>
> Jim Schatzman
>
>
===========================================================================
> 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".
