Quantcast
Channel: Community | MonoGame - Latest topics
Viewing all articles
Browse latest Browse all 6821

Calling Draw() more frequently than Update()

$
0
0

@MontyHimself wrote:

I have experimented with MonoGame for a bit now and I was wondering if this is possible.

Essentially, I would like to keep my draw call frequency at the display's refresh rate while updating my game logic at a lower frequency than that. For example, think of a game where I want to update the game logic with only 30 Hz and synchronize the draw calls to my monitor's refresh rate of, say, 60 Hz with vertical sync. This way, the costly game logic update is only called as often as it needs to be, and I can use the remaining draw calls for interpolation of animations or physics, so that players with monitors that have a higher refresh rate than the game's update frequency of 30 Hz can enjoy a smoother visual appearance.

It looks like Draw() is only ever called at maximum once for every Update() call. I guess the rationale behind it is that all changes should take place in Update(), so there is no point in drawing a new frame when nothing has changed. As you can see, though, there certainly is a use case for this. Is something like this possible with Monogame without having to rewrite essential parts of the framework's game loop?

Posts: 3

Participants: 3

Read full topic


Viewing all articles
Browse latest Browse all 6821

Trending Articles