Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 7.8K All Categories
- 11 Help with translations
- 4.2K General questions
- 107 Roadmap
- 358 Game & application design
- 316 Plugins
- 70 User experience
- 75 Marketplace
- 291 Code snippets
- 34 Building a team?
- 269 Suggestions & requests
- 352 Announce your apps made with Gideros.
- 90 Step by step tutorials
- 668 Bugs and issues
- 195 Introduce yourself
- 239 Announcements
- 106 Forum talk
- 404 Relax cafe
In this Discussion
Working with time based stuff
antix
Member
Hey everyone 
In my descent games the players score is basically based on the amount of time they have been playing. In my EnterFrame code I just added the event.deltaTime to a currentDepth variable and that worked. Some time after release, I got an email saying that if a user paused the game and then resumed some time later, their score would increase a lot while they were not even playing.
The problem here is that when the app is in a suspended state, event.deltaTime still increases so when the app resumes normal operation the event.deltaTime has accumulated and depending on the suspend duration, may be very large.
To resolve the issue I added the following code into my game scene..
So I was curious how other people manage this issue, or if they have even faced this issue at all?
If there is no other solution than polling every frame (ughhh) then would it be possible to..
a) Introduction a new application:resetDT() function to Gideros so on resuming from a suspended state you could call this to reset deltaTime back to 0.
b) Have a project setting in Gideros Studio to choose if deltaTime will be reset automatically on resuming from a suspended state.
What do you think?
In my descent games the players score is basically based on the amount of time they have been playing. In my EnterFrame code I just added the event.deltaTime to a currentDepth variable and that worked. Some time after release, I got an email saying that if a user paused the game and then resumed some time later, their score would increase a lot while they were not even playing.
The problem here is that when the app is in a suspended state, event.deltaTime still increases so when the app resumes normal operation the event.deltaTime has accumulated and depending on the suspend duration, may be very large.
To resolve the issue I added the following code into my game scene..
function Game:onApplicationSuspend() --print('entered a suspended state') self.suspendStart = os.timer() -- save time at start of suspend end function Game:onApplicationResume() --print('resumed from a suspended state') self.suspendDuration = os.timer() - self.suspendStart -- calculate suspend duration self.resumed = true end -- update every frame function Game:update(e) local dt = e.deltaTime -- manage issue when resuming from suspended state causes dt value to be accumulated (very large) if self.resumed then dt -= self.suspendDuration -- correct dt self.resumed = false end local currentDepth = self.currentDepth + dt -- this is now correct after resuming from suspended state end |
If there is no other solution than polling every frame (ughhh) then would it be possible to..
a) Introduction a new application:resetDT() function to Gideros so on resuming from a suspended state you could call this to reset deltaTime back to 0.
b) Have a project setting in Gideros Studio to choose if deltaTime will be reset automatically on resuming from a suspended state.
What do you think?
Likes: SinisterSoft
Tagged:
+1 -1 (+1 / -0 )Share on Facebook
Comments
Three words for you: Frames don't lie.
Likes: antix, Apollo14