LÖVE

MadByte wrote:Seems to be a problem with your system. Can you post your specs, especially graphics card/chip and drivers.

btw. the way you use classes seems to be pretty weird. You create a new object table inside your Asteroid class to handle them but the sense of a class is to be able to create an instance of it - so if you set up an asteroid object it shouldn't create it's own table objects and update/draw them. You didn't asked for it but I want to suggest you to look at this piece here.

Asteroid.love

You create a new object table inside your Asteroid class to handle them but the sense of a class is to be able to create an instance of it - so if you set up an asteroid object it shouldn't create it's own table objects and update/draw them.

I see you create a new image every time you add an asteroid. You should try to reuse the image as much as possible.

how do I reuse the image? Again, fairly new

...
local Asteroid = Object:extend()
local image    = love.graphics.newImage("assets/asteroid.png")

function Asteroid:new(x, y)
  self.image    = image
  ...

also, not sure what you mean by...

You create a new object table inside your Asteroid class to handle them but the sense of a class is to be able to create an instance of it - so if you set up an asteroid object it shouldn't create it's own table objects and update/draw them.

function Asteroid:update(dt)
	createEnemyTimer = createEnemyTimer - 1 * dt
	if createEnemyTimer < 0 then
		createEnemyTimer = createEnemyTimerMax
		
		--random number
		randomNumber = math.random(128, love.window.getHeight() - 200)
		--end random number 
		
		newAsteroid = {x = asteroid.x, y = randomNumber, img = asteroid.img}
		table.insert(asteroid, newAsteroid)
	end
	
	for i, a in ipairs (asteroid) do
		a.x = a.x - (200 * dt)
		
		if a.x < -10 then
			table.remove(asteroid, i)
		end
	end
end

function Asteroid:draw(dt)
		for i,asteroid in ipairs(asteroid) do
			love.graphics.draw(asteroid.img, asteroid.x, asteroid.y)
	end
end

MadByte wrote:

how do I reuse the image? Again, fairly new

Actually you can see it by looking at my example above.

Code: Select all

...
local Asteroid = Object:extend()
local image    = love.graphics.newImage("assets/asteroid.png")

function Asteroid:new(x, y)
  self.image    = image
  ...

also, not sure what you mean by...

You create a new object table inside your Asteroid class to handle them but the sense of a class is to be able to create an instance of it - so if you set up an asteroid object it shouldn't create it's own table objects and update/draw them.

I mean this:

Code: Select all

function Asteroid:update(dt)
	createEnemyTimer = createEnemyTimer - 1 * dt
	if createEnemyTimer < 0 then
		createEnemyTimer = createEnemyTimerMax
		
		--random number
		randomNumber = math.random(128, love.window.getHeight() - 200)
		--end random number 
		
		newAsteroid = {x = asteroid.x, y = randomNumber, img = asteroid.img}
		table.insert(asteroid, newAsteroid)
	end
	
	for i, a in ipairs (asteroid) do
		a.x = a.x - (200 * dt)
		
		if a.x < -10 then
			table.remove(asteroid, i)
		end
	end
end

function Asteroid:draw(dt)
		for i,asteroid in ipairs(asteroid) do
			love.graphics.draw(asteroid.img, asteroid.x, asteroid.y)
	end
end

You use your Asteroid.lua as an "object handler" on it's own by letting it create new asteroids and then update and draw them inside the class. But this is the opposit to what a class is meant for. In my example the asteroid.lua creates a new asteroid and the update and draw process happens somewhere else. You need to make sure that your class just hold the object itself.

your specs shouldn't be the problem at all.

slime wrote:If you create enough images that the graphics driver runs out of VRAM to use, it could cause instabilities and seemingly random graphics glitches (on top of the obvious performance issues). I'd worry about that now rather than later.

MadByte wrote:

how do I reuse the image? Again, fairly new

Actually you can see it by looking at my example above.

Code: Select all

...
local Asteroid = Object:extend()
local image    = love.graphics.newImage("assets/asteroid.png")

function Asteroid:new(x, y)
  self.image    = image
  ...

also, not sure what you mean by...

You create a new object table inside your Asteroid class to handle them but the sense of a class is to be able to create an instance of it - so if you set up an asteroid object it shouldn't create it's own table objects and update/draw them.

I mean this:

Code: Select all

function Asteroid:update(dt)
	createEnemyTimer = createEnemyTimer - 1 * dt
	if createEnemyTimer < 0 then
		createEnemyTimer = createEnemyTimerMax
		
		--random number
		randomNumber = math.random(128, love.window.getHeight() - 200)
		--end random number 
		
		newAsteroid = {x = asteroid.x, y = randomNumber, img = asteroid.img}
		table.insert(asteroid, newAsteroid)
	end
	
	for i, a in ipairs (asteroid) do
		a.x = a.x - (200 * dt)
		
		if a.x < -10 then
			table.remove(asteroid, i)
		end
	end
end

function Asteroid:draw(dt)
		for i,asteroid in ipairs(asteroid) do
			love.graphics.draw(asteroid.img, asteroid.x, asteroid.y)
	end
end

You use your Asteroid.lua as an "object handler" on it's own by letting it create new asteroids and then update and draw them inside the class. But this is the opposit to what a class is meant for. In my example the asteroid.lua creates a new asteroid and the update and draw process happens somewhere else. You need to make sure that your class just hold the object itself.

your specs shouldn't be the problem at all.