g_SetUpdateMode

[Andrew Beery]

g_SetUpdateMode?

I pulled this function name from a previous thread... how do we try out these new update modes?

[kornalius]

Using g_SetUpdateMode() is very easy, all you have to do is call this function after you have just initialized the GameAPI and PPL will take care of everything for you. You don't have to do anything manually.

There are three modes:

UM_WHOLESCREEN (default)

Every update of the screen, the whole screen is updated.

UM_MULTIPLE

Every update, all parts (rectangles) of the screen that have been changed are updated. This could prove to speed up your game a great deal if you only have a few things moving between each update.

UM_SINGLE

Every update, a single rectangle area is calculated that includes all rectangles of the screen that have changed since the last update. If you have lots of things moving of the screen within the same area, this is the best mode to use.

[zehlein]

Alain, which mode is the one GameAPI uses by default?
Edit: Sorry, I should read more carefully :-) , default is mentioned.
UM_SINGLE is causing problems by the way (sprite disappearing from the screen)

[PointOfLight]

I have updated the help file.

[kornalius]

zehlein, send me a quick code sample so I can verify what is going on. support@arianesoft.ca

[zehlein]

Done.

[kornalius]

Got it, will look at it tomorrow.