VSync affecting physics?

[Tesselode]

Open this .love file, and try setting vsync to true and false in conf.lua. Observe the differences.

Why?

[Motig]

Open this .love file, and try setting vsync to true and false in conf.lua. Observe the differences.

Why?

The .love file is a lie!

(You forgot to post it)

[Tesselode]

Open this .love file, and try setting vsync to true and false in conf.lua. Observe the differences.

Why?

The .love file is a lie!

(You forgot to post it)

Facepalm. Fixed.

[TechnoCat]

Not much better.

trace.PNG (83.92 KiB) Viewed 1691 times

[ninwa]

I got it running and observed the difference you are talking about. My initial expectation was that you were including game logic somewhere within love.graphics.draw (which would typically be limited to 60fps by v-sync) but the code exhibits pretty good structure and separation of game-logic from rendering. That said, no fucking idea. Good luck.

(Edit: This may be related to some sort of bug in LOVE where Box2D / Particle Engine calls are limited internally by v-sync, but you would have to ask a LOVE developer about that.)

[Robin]

(Edit: This may be related to some sort of bug in LOVE where Box2D / Particle Engine calls are limited internally by v-sync, but you would have to ask a LOVE developer about that.)

That makes sense, because there is a single game loop: love.run() (it's even implemented in Lua and everything).

[bartbes]

Note that I didn't actually do it, but if your code is affected by how many times love.update is called (especially when it still is 60 Hz!) you must be doing something wrong.

[Robin]

I've read the thing, and he doesn't use dt *ever* (as in, no argument to love.update), but he does use getDelta when calling world:update().

[Tesselode]

Will it help if I use dt? I tried using it before. I could get it to work in the love.update loop, but when I tried to pass it to other functions, it didn't work. Is there a difference between dt and love.timer.getDelta?

Some people have been reporting performance problems with the game and I'm thinking this VSync issue might have something to do with it.

[bartbes]

dt is obtained from love.timer.getDelta(), so that shouldn't change anything, you might want to limit the timesteps. (i.e. use a fixed timestep, and use that enough times to 'fill' dt)