gavioto / playn

Automatically exported from code.google.com/p/playn
0 stars 0 forks source link

Blank screen using SurfaceLayer (lwjgl) #205

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Compile and run the attached Java class - MyTestsGameJava (copied/used from 
playn-tests-java project).
2. Using the hasRun check in the paint method to only render once to the 
surface, the intended output (two squares) is displayed.  
3. Removing the hasRun check, thereby rendering to the surface in each call to 
the paint method, only a blank screen is shown.

What is the expected output? What do you see instead?
The expected output should be shown even if surface rendering is done on each 
paint call. 

What version of the product are you using? On what operating system?
1.5-SNAPSHOT (checked out a couple of days ago). Mac OS X Snow Leopard 
(10.6.8). Using 64-bit Eclipse and JVM if relevant (e.g. wrt the native lwjgl 
lib)...

Please provide any additional information below.
I am a novice on OpenGL programming but I am guessing that the binding of frame 
buffers is not working as intended. 

Original issue reported on code.google.com by par.ekl...@gmail.com on 31 Jul 2012 at 4:24

Attachments:

GoogleCodeExporter commented 9 years ago
This problem has also been detected by another user, as detailed here: 

http://stackoverflow.com/questions/11705458/cannot-render-surfacelayer-during-pa
int-method

I have also verified (as had the other user in question) that this problem is 
not present in PlayN 1.3.1. 

Original comment by par.ekl...@gmail.com on 31 Jul 2012 at 7:24

GoogleCodeExporter commented 9 years ago
(Sorry for the huge delay in addressing this. I'm trying to ship a game. :)

This is fixed in 
https://github.com/threerings/playn/commit/137ce50dddd2716f84c38ec1568d7ae5a3684
34b

I'll try to get this and a bunch of other commits merged into the Google Code 
repository when I can, but in the meanwhile you can either apply the fix 
locally or use the Github code.

Original comment by m...@samskivert.com on 3 Oct 2012 at 12:44