5 replies to this topic

[oldbone]

I'm using my own timer based upon variables, switches & parallel common events.

And it works great!

However, the parallel process seems to "pause" when the player is accessing game menus. It does resume just fine when the player is out of the menus... but I'd like to keep the parallel process going while in menus, talking to npc's, etc.

is this an imposibility?

[regendo]

You could simply add your timer's update function to Graphics#update, that way, the timer will be updated on every frame, regardless of what scene you are in.

[oldbone]

sorry.. still new. Where is "Graphics#update"? is there a "master" one somewhere?

Thanks!

[BigEd781]

module Graphics
  class << self
    alias :timer_gupdate :update
    def update(*args)
      timer_gupdate(*args)
      (@my_timer ||= 0) += 1  # frame.  To convert to time you will need to use the frame rate    
    end
  end
end

Remember; Graphics.update is called once per frame. To convert this to time (seconds) you will need to divide by the frame rate.

However, even though you posted this in the RGSS section, you seem to be using only events at this point. Should I move this to general support? On a side note, there is nothing an even can do which will allow you to continue processing from another scene (the map and the menu are two completely different scenes, which is why map events do not update when you are in the menu, just as events from map A would not execute if the player were on map .

[oldbone]

Thanks BigEd - will take a look.

My event that keeps "counting down" is a common event, so it survives thru a scene change, game save/load, etc.

I'm pretty sure the answer (in the end) will be scripting, so if it's all the same to you - let's leave this here for now.

[Rixis]

solved and closed :]