Hello, welcome to the forums.
Actually, I notice that the dino also flickers when moving left and right. The flicker comes from the nearest filter, the non-integer scaling factor and the drawing at non-integer coordinates.
The occasional jerking of some enemies seems to be due to skipping the update of the next enemy whenever you delete an enemy from the allEnemies table. Imagine your allEnemies table contains 2 elements: allEnemies[1] is about to be deleted, and allEnemies[2] is still in the table. Now you loop through allEnemies. i is set to 1 and enemy is set to allEnemies[1]. The code finds that allEnemies[1] needs to be deleted, therefore it goes ahead and deletes it.
That deletion makes allEnemies[2] become allEnemies[1]. On the next iteration, i is set to 2. Now allEnemies[2] does no longer exist and the loop ends. As a result, the enemy after the one deleted isn't updated.
An easy solution is to loop backwards, i.e. instead of this:
Code: Select all
for i, enemy in ipairs(allEnemies) do
...
use this:
Code: Select all
for i = #allEnemies, 1, -1 do
local enemy = allEnemies[i]
....
In your case, you don't care about the checking/deletion order, so you can ignore the rest of the post. I'm adding it just because if the need arises (which happens rarely but I've run into a few cases), it's good to know what to do.
If the checking order is important, the procedure would require a more involved solution: to use your own loop variable, and to increment it only if you are not deleting an element. Something along these lines:
Code: Select all
local i = 1
local numEnemies = #allEnemies -- cache the item count, to avoid calculating it every time
while i <= numEnemies do
local enemy = allEnemies[i]
if hasToBeDeleted(enemy) then
table.remove(allEnemies, i)
numEnemies = numEnemies - 1 -- update the item count
-- don't increment i here
else
-- increment i here
i = i + 1
end
end
Dino_Game.love
