Ken Warner wrote:
I thought the first notice that was sent out about the D3D pipeline said
that the OpenGl pipeline was turned on for D3D.
"the OpenGl pipeline was turned on for D3D" - this doesn't
make any sense. Not sure how something like this
can be concluded from what have been written.
I must have misunderstood what was said. The D3D pipeline and
the OpenGL pipelines are two different pipelines with two
entirely different sets of problems mostly caused by poorly
implemented video card drivers. Am I finally understanding
this?
Yes.
And the OpenGL pipeline has nothing to do with the hardware
acceleration of Java2D which uses the D3D pipeline? Is that correct?
Yes.
So it was said that the D3D pipeline will be disabled *BY DEFAULT*
on some OS's. Will it be possible to *ENABLE* the D3D pipeline with
-Dsun.java2d.d3d=true on the Win200* OS's that are going to have
the D3D pipeline disabled by default from using the D3D pipeline?
The D3D pipeline is enabled by default on all
platforms. That means that it will try to get initialized
on all systems during the startup. However, as a part of the
initialization process it will check for the driver
and operating system requirements, as well as hardware
capabilities. If any of these checks fail the
pipeline will not be used.
Currently the check for OS will fail on server class
operating systems, so the pipeline will not be used.
Unfortunately you will not be able to force it
using -Dsun.java2d.d3d=true .
In all the emails that have been flying around, people talk of
"...the pipeline..." and I get confused about which pipeline
is being talked about.
Depends on the context, of course, but at least in this
thread it is most likely in reference to the Direct3D
pipeline.
Thank you,
Dmitri
Dmitri Trembovetski wrote:
Just in case this hadn't been replied to:
yes, we'd seen this behavior on certain video boards
only on Vista with Aero enabled.
I'm pretty sure this is a Vista bug, but we'll
try to work around it.
Thanks,
Dmitri
[EMAIL PROTECTED] wrote:
Hello,
I've been playing a few hours with the 6u5 and the D3D pipeline.
(I'm quite sure it is enabled, as a full-screen drawing framerate
drops by a factor of about 20 when disabled, with CPU usage jumping
to about 70%)
Marvelous performance (thank you all for your work), however I have
found something annoying :
(I did my tests on Windows Vista, with an nVidia GeForce 8600M GT,
recent drivers (Aero enabled))
If I create an empty resizable JFrame (I tested with
SystemLookAndFeel, SubstanceLookAndFeel and Metal), and start
resizing it, I will most of the time see its content flickering (the
client rectangle becoming black before being repainted).
Obviously, all reverted to normal when I ran the application with
-Dsun.java2d.d3d=false.
Someone has an idea about what is happening ?
[Message sent by forum member 'artscoop' (artscoop)]
http://forums.java.net/jive/thread.jspa?messageID=245249
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in
the body
of the message "signoff JAVA2D-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 JAVA2D-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 JAVA2D-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 JAVA2D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
