Could not enable OpenGL pipeline error

Java 2D
#1

Hello,

I’m trying to run java application using -Dsun.java2d.opengl=True, but I
always get “Could not enable OpenGL pipeline for default config on screen 0”.

I use 1.5.0_04-b05 SE running on WinXP. The graphics controller is
Intel 82852/82855 GM/GME, driver Nr. 6.14.10.3762.

Can anyone help?

Thanx.
Milan

#2

The inhouse opengl guru Chris is in China currently giving a JavaOne talk, so I’m filling in.

I don’t think the intel chips (and their drivers) have sufficient capabilities for
running our opengl pipeline, unfortunately.

Dmitri
Java2D Team

#3

There are two specific reasons why our OGL pipeline would not startup on Intel GPUs:

  1. most of their chips/drivers do not support a PixelFormat with a stencil buffer
  2. none of their chips/drivers support the GL_WGL_render_texture extension

We’ve effectively resolved (1) as of Mustang b51 now that we use only the depth buffer (and not stencil) for complex (shape) clipping. Although (2) is still an issue, their drivers do support the GL_WGL_make_current_read extension, which we could use as an alternate way to copy pbuffers to the screen. I’ve been thinking maybe it’s time to do this so that the OGL pipeline is more useful on a wider array of GPUs out there (and Intel accounts for a pretty large majority).

Chris

#4

Any update about the solution for issue 2?

#5

I did most of the work a few weeks ago, but there were driver bugs that needed to be worked around, and at this point it’s probably too late in the release cycle to get this in for Mustang (there are other projects that take priority). Hopefully we can revisit it for Dolphin.

Chris

#6

Although I think having a broad support for the OpenGL pipeline is great (and supporting the intel chips in addition to nvidia + ati chips would make support quite broad) I am in doubt wether too many workarrounds would not cause the pipeline to become more and more unmaintable?

Wouldn’t it be better so send a small native test-case to Intel, if Sun is contacting them I am sure they will hurry a bit more than some independet guy unhappy with their drivers would contact them.

lg Clemens

#7

I’m in agreement. I’ve strived to avoid adding workarounds in the OGL pipeline. In fact, I can only think of one off the top of my head (in the Windows-specific code). I wasn’t suggesting that I would actually implement the workarounds in the JDK, it’s just that the pipeline was unusable without them. Ideally we would be able to work with Intel’s driver team to fix the problems at the source, as we’ve done with Nvidia and ATI, but I’m not holding my breath. And even if we do get the problems fixed in their drivers, I don’t know many people that are able to download new drivers easily from Intel’s website, which is why I don’t think the OGL pipeline will be a good fit on Intel for the general population. I’m willing to give it a shot, but I’m not confident.

Chris