LOVE cpu overload

[Robin]

Interesting. Can you try some more games, see what happens? Perhaps we can find out what causes the issue that way.

[Alexintosh]

I'm actually using love.timer.sleep(1000 / 50) -- for 50 FPS, it works very well anyway at least the cpu run at 80% with the game opened.

Thre is the project if anyway want to check

@Robin Why that tutorial was criticized?

[Robin]

Thre is the project if anyway want to check

Well, nothing obvious seems wrong with it.

@Robin Why that tutorial was criticized?

Several reasons. I think it might foster some misunderstandings later on, it has some examples of bad coding practice (thankfully not many, nor is it that bad), and in addition it seems to encourage to copy or type without understanding, but that might be me.

[Alexintosh]

Well, nothing obvious seems wrong with it.

Can you tell me how it run in your pc? cpu, temperature and which os is.

The tutorial was fine for me I was asking something about make a class constructor and destructor.

Can you link the thread or explane the examples of bad coding practice you talked about, I'd like to know them before carry on.

[Adamantos]

Hi,
this is a little codeblock I use in every project. The routine tries to regulate the delay between frames, to reach the destination framerate.

Code: Select all

function love.run()

  if love.load then love.load(arg) end

  local dt  = 0        -- time for current frame
  local tau = 36       -- initial value for delay between frames
  local runtime = 0
  
  -- Main loop time.
  while true do
      
      
    love.timer.step()
    dt = math.min(0.1, love.timer.getDelta() ) 
    runtime = runtime + dt
    
    -- do regular stuff
    love.graphics.clear()
    love.update(dt) 
    love.draw()
    love.graphics.print("FPS: ["..love.timer.getFPS().."] delay: ["..math.floor(tau).."ms] idle:["..math.floor(100 * (tau/1000)/dt).."%]", 10, 10)  
        
    -- correct delay
    if(runtime > 2) then
      tau = tau + (love.timer.getFPS()-25)*0.2*dt
    end
      

    -- Process events
    if love.event then
      for e,a,b,c in love.event.poll() do
        if e == "q" then
          if love.audio then love.audio.stop() end
          return
        end
        love.handlers[e](a,b,c)
      end
    end

    -- sleep
    if love.timer then love.timer.sleep(tau) end
    if love.graphics then love.graphics.present() end

  end

end

[Robin]

Well, nothing obvious seems wrong with it.

Can you tell me how it run in your pc? cpu, temperature and which os is.

CPU and temperature normal, I'm on Linux.

Can you link the thread or explane the examples of bad coding practice you talked about, I'd like to know them before carry on.

Unfortunately, I don't remember where it was.

[Alexintosh]

@Adamantos Thanks for sharing

@Robin Thanks for informationm I will upgrade to ubuntu 10.10 in these days, maybe works better

[sharpobject]

@Adamantos where do you define and modify the variable named runtime?

Setting it to 0 and incrementing it each frame seems to work pretty well. It takes about four seconds to converge on 60fps for me, though.
Edit: Oh, nevermind about that. Initializing tau to a better guess (like 13) fixes it.

[Adamantos]

@Adamantos where do you define and modify the variable named runtime?

Ups sorry... i deleted the part for incrementing the runtime.
In the startup phase LÖVE doesn't calculate the FPS rate right, so i had to skip the first seconds.