Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting FixedTimeStamp=30 and UpdateFrequency=60 breaks the Cursor module. Is it ok? #47

Open
ProgrammingLife opened this issue Aug 9, 2024 · 0 comments

Comments

@ProgrammingLife
Copy link

ProgrammingLife commented Aug 9, 2024

I just set to the game.project:

fixed timestamp = 30
update frequency = 60
use fixed update = true

And now looks some Defold messages are lost and removing objects feature now works not every click. Sometimes it works every click, sometimes not.

Is it a correct behaviour?

Why do I need settings like this?
Only for consistency purpose. I wanna have physics update running 30 FPS on every device no matter it can render now on 30FPS or 60FPS, I just wanna slow down the physics updates. I think it's too overhead to run physics on 60FPS if device can render only 30FPS like iPhone does in HTML5 (low power mode). But if I use default physics settings then my physics running two times slower on iPhones in low power mode.

@ProgrammingLife ProgrammingLife changed the title Use FixedTimeStamp=30 while UpdateFrequency=60 breaks the Cursor module. Is it ok? Setting FixedTimeStamp=30 and UpdateFrequency=60 breaks the Cursor module. Is it ok? Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant