Question on Native Functions : V

» Tue Dec 18, 2012 6:22 am

According to the CreationKit Wiki...

Last but not least, OnUpdate is a very frequent cause of savegames bloat and general bugs, forcing the user to abandon their current game and restart a new one. This occurs when the OnUpdate handler takes more time to run than the update interval it was registered with. The result is that new calls are queued faster than they are processed, preventing other scripts to run, consuming increasing memory and can lead to savegames as large as one gigabyte! Unfortunately, since almost every call to a native function suspends a function's execution for one whole frame, the phenomenon is bound to happen if the handler contains more native calls than the number of frames between each handler's call

The part in Bold is what I am interested in. Specifically, what IS a Native Function?

My script upses a lot of .SetValue() and .GetValue() for various things, with 5-6 Scripts (right now) tracking and updating them. Will this have that sort of slowdown, and how concerned should I be?

I know this is related to RegisterForUpdate and I am using RegisterForSingleUpdate, so the long-queue shouldn't matter, btu what I am concerned about is it affecting the running-time of my Script.

» Tue Dec 18, 2012 2:52 am

This is related to the risk of of native functions delaying a registerforupdate type structure. But Registerforupdate can be delayed by other scripts, by processes in the background in your computer, temperature increases in your CPU...

Native functions are functions that are defined by hard code (most official functions). Basically the idea here is that using Registerforupdate is really a bad idea as it will launch a new event instance regardless the previoius one or ones not being finished. Registerforsingleupdate, if it's called in again in it's last line, won't be launched until the previous call is finished, so, no danger here.