JDK-6613062 : D3D: improve on-screen rendering responsiveness
  • Type: Bug
  • Status: Closed
  • Resolution: Fixed
  • Component: client-libs
  • Sub-Component: 2d
  • Priority: P3
  • Affected Version: 6u5
  • OS: windows_xp
  • CPU: x86
  • Submit Date: 2007-10-04
  • Updated Date: 2010-10-14
  • Resolved Date: 2007-10-23
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availabitlity Release.

To download the current JDK release, click here.
JDK 6
6u10 b06Fixed
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 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

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

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