Jerky gameplay

[underww]

I heard that old games like Super Mario Bros stored subpixels in a separate integer.
So you might also use an another variable for the decimal units of the velocity.
But I don't know this is good for modern game dev or not.

as I know on it is also a kind of limit of pure 2D graphics.
You need to use 3D graphics (means directly use OpenGL) to solve this problem completely.

[Jycerian]

Well let me try to explain it in more detail:

When I stand still there is no problem, no flashy things or screen tearing (only visible on the sprite.) When I move the character it moves in the given direction but then it becomes slightly jerky like it seems to skip a couple of pixels so it isn't smooth maybe because it skips a couple of frames? Or just skips the pixels in general maybe due to using floats? Also another effect appears where it looks like the Sprite is tearing for instance when I move to the right the top half would be something like 2 pixels to the left and the bottom half 2 pixels to the right and then it becomes normal again. It seems this tearing and jerkiness appear at random intervals.

It seems like other people have no problems with my code? I have updated SFML and my graphics driver so maybe it is a bug that has to do this the support of my video-card / processor? Games like League of Legends run fine for instance. I posted my computer stats in an earlier post.

[Hapax]

It sounds like you're having two issues. One with tearing, and another with skipping.
The tearing can only (as far as I'm aware) be fixed by using vertical sync.. Unfortunately, the graphics card is in charge of that and its drivers are in charge of that card so they could easily be ignoring SFML's request for v-sync.
The skipping does sound like it's skipping frames; it's been mentioned on the forum a few times already and I've seen it on my own projects. You should make sure you've tried a release build instead of a debug build first as that often makes a difference.
You also mentioned that it could be skipping pixels because of using floats. I don't think floats would directly be the cause. It would only be if the two draw positions are two pixels apart. If you're rounding and the two positions are 2.49 and 3.5 (distance of about 1), the rounded positions would be 2 and 4 (distance of 2).

Comparing with League Of Legends is an odd thing to do. It's rendering in 3D for a start 

[Jycerian]

Thanks for the input, just tested without frame-rate limit and then it is pretty much smooth and the tearing doesnt happen that often. Also the borders of the square become kinda fuzzy when moving and sharp when not moving but that is because you are moving using floating points I guess. So it seems like the program is skipping frames, is this normal or is it just me?

[Jesper Juhl]

Thanks for the input, just tested without frame-rate limit

You should never use both vsync and frame-rate limit both in the same program. They interact badly and if that's what you were doing (which I get the impression you were, since vsync is usually the best way to counter tearing), it is not surprising that you were having issues. This is well documented btw.

[Jycerian]

Thanks for the input, just tested without frame-rate limit

You should never use both vsync and frame-rate limit both in the same program. They interact badly and if that's what you were doing (which I get the impression you were, since vsync is usually the best way to counter tearing), it is not surprising that you were having issues. This is well documented btw.

I know about this, I am not using both, enabling v-sync doesn't work for me anyways even though my display driver is setup properly.