Difference between revisions of "User:DavidJCobb/Stack dumping"
m
→How do update events work?
imported>DavidJCobb |
imported>DavidJCobb |
||
| Line 39: | Line 39: | ||
*'''Possibility 1:''' when you call RegisterForSingleUpdate(''x''), Skyrim queues an update event to fire in ''x'' seconds. No new stacks are created. | *'''Possibility 1:''' when you call RegisterForSingleUpdate(''x''), Skyrim queues an update event to fire in ''x'' seconds. No new stacks are created. | ||
*'''Possibility 2:''' when you call RegisterForSingleUpdate(''x''), Skyrim immediately creates a call stack for OnUpdate, and suspends it for ''x'' seconds. | *'''Possibility 2:''' when you call RegisterForSingleUpdate(''x''), Skyrim immediately creates a call stack for OnUpdate, and suspends it for ''x'' seconds. | ||
**If this one is the case, then you would not be able to use update events to minimize generated stacks. | **If this one is the case, then you would not be able to use update events to minimize generated stacks. Like, I seriously doubt it, but AFAIK this sort of thing is documented ''so little.'' | ||
*'''Test procedure:''' RegisterForSingleUpdate(20.0), and then DumpPapyrusStacks using the debug console. See if an OnUpdate stack is dumped. | *'''Test procedure:''' RegisterForSingleUpdate(20.0), and then DumpPapyrusStacks using the debug console. See if an OnUpdate stack is dumped. | ||