This line of code is inside the love.run already, so you don't have to put it anywhere manually (expect if you want to change the love.run). The purpose of this line is to tell the OS that it has some free time to take care of other processes than LÖVE. That way, the OS itself does not freeze, while...

Tom Francis talked about Efficiency for Game Designers on this years GDC. He mentions something that I call the "most bang for the buck"-technique: Always tackle those issues first that give you the most value per hour of work you put in. Besides this, my favorite technique for being effic...

Hi and welcome to the community! If I understand correctly, then the top code in your post is your current project. In this code you are not using love.physics. The second code you posted is a different project and you are trying to learn from it. It uses love.physics. This is one way for dealing wi...

Could you please upload a .love file of you code, so that we can try to reproduce the laggy behavior?

I cannot provide the fixed code for you, but here is what you can do to fix the issue: First, get used to the fact that you have two types of coordinates: world-coordinates and screen-coordinates. These can even have different units (for example meters or tiles vs. pixels). For camera implementation...

Some time ago, I read an article about a performance comparison of LÖVE with some other game frameworks, and LÖVE performed slowest among the tested ones. Unfortunately, I don't have the link to the article at hand. But the important question is: Is the performance only lower than in other framework...

I think that undef's solution is the best one, because it runs in constant time (as opposed to the loop solution of T-Bone) and it is probably more robust against rounding errors (as opposed to davisdudes solution). I haven't tested it though, so if someone can prove me wrong, I am happy to learn. f...

I am just new to programming and it was pretty much the first thing that I learned in class. Not to use global's, that is. It is a good rule of thumb to avoid globals, because globals tend to couple code that should not be coupled. More often than not, variables are only used locally and so it is a...

Hi and welcome to the forum. You need to replace the function declaration of the love.update by this: function love.update(dt) Otherwise the variable dt is not define inside this function. By the way: You can make your code much more readable by putting it into code-tags (mark your code and press th...

That depends on you framerate. dt is usually not 1, but a different number. So if you multiply something with dt, the value will change. If you want to keep the same apparent behavior, then you multiply by dt and then divide by the dt that you have on your computer at the moment. Usually that will b...