United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6613062 D3D: improve on-screen rendering responsiveness
JDK-6613062 : D3D: improve on-screen rendering responsiveness

Details
Type:
Bug
Submit Date:
2007-10-04
Status:
Closed
Updated Date:
2010-10-14
Project Name:
JDK
Resolved Date:
2007-10-23
Component:
client-libs
OS:
windows_xp
Sub-Component:
2d
CPU:
x86
Priority:
P3
Resolution:
Fixed
Affected Versions:
6u5
Fixed Versions:
6u10 (b06)

Related Reports

Sub Tasks

Description
Initial feedback on the d3d pipeline indicates that we need to improve
the way we handle on-screen rendering. 

For application rendering to the screen (without a back-buffer)
100ms update time is too slow.

Also, some apps use BufferedImages as back-buffers. They also
suffer from 100ms delay because we only force onscreen updates
on VI-> screen copes.

See this thread for more:
  http://www.javagaming.org/forums/index.php?topic=17491.0

                                    

Comments
EVALUATION

We should at least decrease the update rate to 50ms and
force the updates on BI->screen copies.

We can also devise some adaptive mechanism for when there's
lots of on-screen rendering.
                                     
2007-10-04
SUGGESTED FIX

http://sa.sfbay.sun.com/projects/java2d_data/6u5/6613062.0
                                     
2007-10-11
EVALUATION

We have determined that it is sufficient to just run update
thread after any blit to the screen, there is no benefit in 
increasing the update rate since most applications which
require specific frame rate are double-buffered (either
with BufferedImage or VolatileImage). 

We can revise this decision if there are issues.
                                     
2007-10-11



Hardware and Software, Engineered to Work Together