Slick Forums

Matthias and I have been trying to track down what seems to be a bug in the thread posted below. I'm hoping somebody can help take a look and maybe help figure out what's going on.

"...somehow getGraphics() leaves a wrong GL_VIEWPORT size active at the time the LWJGLRenderer is syncing it's display size (eg at creation time, can manually sync later - eg for resizing support)."

viewtopic.php?f=18&t=4375

Hi,

I have encountered a similar problem (or I guess it's the same problem in a different guise). TWL rendering breaks after calling Image.createOffscreenImage(); for more details look here: . (I found this thread only afterwards.)

Calling getGraphics().flush() afterwards indeed solves the problem. I just report this so that others with similar problems can see this.

Since I have no idea how OpenGL works exactly (that's why I decided to use Slick and TWL in the first place), I can only hope that this won't have any side effects. Or will calling getGraphics() after the createOffscreenImage lead to memory leaks again?

-Kylearan

createOffscreenImage will not lead to a leak; you can then call getGraphics without any extra textures being allocated.

flush() is necessary after you're done with the offscreen image, regardless of whether you are using TWL.