Screen tearing with BufferStrategy

[Donald_W]

I am using BufferStrategy with 2 buffers (tried with 3 as well) but I cannot rid of screen tearing in my application (no vsync?).
I draw everything on one BufferedImage and then draw it on the graphics received from BufferStrategy.

Any ideas how to solve this problem?

This is my render method:

1   2   3   4   5   6   7   8   9   10   11   12   13   14

public void render() {         do {             do {                 Graphics2D g = (Graphics2D) bufferStrategy.getDrawGraphics();                 g.setColor(Color.BLACK);                 g.fillRect(0, 0, getWidth(), getHeight());                 g.clipRect(0, 0, getWidth(), getHeight());                 g.scale(scale, scale);                 g.drawImage(screen.getImage(), 0, 0, screen.getWidth(), screen.getHeight(), null);                 g.dispose();             } while (bufferStrategy.contentsRestored());         } while (bufferStrategy.contentsLost());         bufferStrategy.show();     }

[ra4king]

What Operating System are you using?

[ReBirth]

Seems you do triple buffering here

try remove the do..while pair.

Games published by our own members! Check 'em out!

[ra4king]

No the do-while pair is necessary. I also just noticed you have the show() call in the wrong place. It's supposed to be right after the inner do-while loop ends, not after the outer one.

[ReBirth]

Really? I never used that before.

[ra4king]

Really? I never used that before.

I have been telling people to do this since the beginning of time >.>

[Donald_W]

@ra4king: I have tearing on both Windows and Linux. Whole application is in JFrame - maybe that is an issue? Should I swap to applet?

[ra4king]

You shouldn't be seeing tearing in either Vista, 7, or 8. I don't know about Linux.

Can we see the code/JAR to run it and see for ourselves?

[Donald_W]

Here is the jar: http://dl.dropbox.com/u/1146144/reckless-skirmishers.jar

Just go to the border of the pavement floor (go to the right) and move left-right repeatedly.
Game updates every 2nd frame but with 60 FPS - 60 updates I get tearing as well so I guess it is not a problem.
 
BTW: Graphics are for test purposes (taken from Catacomb Snatch).

[ra4king]

No screen tearing here. It runs fine, but at 59 FPS? Something is wrong with your sleeping logic.

Are you using Windows 7?

Games published by our own members! Check 'em out!

[Donald_W]

Linux Ubuntu/Xubuntu and Windows 7. Now I am on the machine with Linux, tested it on friend's xubuntu as well (maybe it is a xubuntu issue then).

Game loop implementation:

1   2   3   4   5   6   7   8   9   10   11   12   13   14   15   16   17   18   19   20   21   22   23   24   25   26   27   28   29   30   31   32   33   34   35   36   37   38   39   40   41   42   43   44   45   46   47   48   49   50   51   52   53   54   55   56   57   58   59   60   61   62   63   64   65   66   67   68   69   70   71

public class FixedLengthGameLoop implements GameLoop {     private static final Logger LOGGER = LoggerFactory.getLogger(FixedLengthGameLoop.class);     // Limits the update amounts before render    private static final int MAX_UPDATES_PER_RENDER = Integer.MAX_VALUE;     private static final double NANOS_PER_SECOND = 1000000000;     // desired updates rate    private static final double UPDATES_RATE = 30;     // time between game updates    private static final double UPDATES_INTERVAL = NANOS_PER_SECOND / UPDATES_RATE;     // desired frame rate    private static final double FRAMES_RATE = 60;     // time between each render    private static final double RENDERS_INTERVAL = NANOS_PER_SECOND / FRAMES_RATE;     private GameContext context;     public FixedLengthGameLoop(GameContext context) {         LOGGER.info("Initializing default game loop");         this.context = context;     }     public void run() {         LOGGER.info("Executing main loop");         double lastUpdateTime = System.nanoTime();         double lastRenderTime = System.nanoTime();         double now;         int updatesCount;         int frames = 0;         int fps = (int) FRAMES_RATE;         double lastFpsUpdateTime = System.nanoTime();         while (context.isRunning()) {             now = System.nanoTime();             updatesCount = 0;             while (now - lastUpdateTime > UPDATES_INTERVAL && updatesCount < MAX_UPDATES_PER_RENDER) {                 context.update();                 lastUpdateTime += UPDATES_INTERVAL;                 ++updatesCount;             }             if (now - lastRenderTime > RENDERS_INTERVAL) {                 float delta = Math.min(1.0f, (float) ((now - lastUpdateTime) / UPDATES_INTERVAL));                 context.render(delta, fps);                 lastRenderTime = now;                 ++frames;             }             if (now - lastFpsUpdateTime > NANOS_PER_SECOND) {                 fps = frames;                 frames = 0;                 lastFpsUpdateTime = now;             }             try {                 Thread.sleep(1);             } catch (InterruptedException e) {                 // consume            }         }     } }

[Donald_W]

Well on my machine even Catacomb Snatch have issues with vsync so I guess it is OS fault.

[sproingie]

I'm pretty sure vsync is ignored in windowed mode for OpenGL on Windows and Linux and it uses whatever the desktop is set to.  On most recent Linux distributions, I've found you can't even get the desktop to use vsync.

[ra4king]

This is Java2D, not OpenGL.

Also, in Windows Vista and 7, you shouldn't be seeing any screen tearing due to the Desktop Window Compositor preventing any tearing.

[Donald_W]

Well it looks that I am doing something wrong. Now I/We have to figure out what is it