Difference between revisions of "StartStackProfiling - Debug"

From the CreationKit Wiki
Jump to navigation Jump to search
imported>Rhavlovick
m (1 revision: Clobber re-import by Henning)
 
imported>JLundin
Line 1: Line 1:
[[Category:Scripting]]
[[Category:Scripting]]
[[Category:Papyrus]]
[[Category:Papyrus]]
[[Category:Non-delayed Native Function]]
'''Member of:''' [[Debug Script]]
'''Member of:''' [[Debug Script]]



Revision as of 08:08, 12 September 2012

Member of: Debug Script

Starts profiling a single Papyrus stack until stopped or until the last function exits. The profile files are stored in "<game folder>/Logs/Script/Profiling". This will also cycle the older profiling logs (so log 0 becomes 1, 1 becomes 2, etc). If the stack is already profiled nothing will change. Profiling requests are not saved and will be reset if you load a save game.

Syntax

Function StartStackProfiling() native global

Parameters

None.

Return Value

None.

Examples

; Starts profiling this current stack
Debug.StartStackProfiling()
; Lots of slow script here

Notes

Profiling requires the "bEnableProfiling" flag in the "[Papyrus]" section of the ini file to be set to 1. Consoles will never profile in release final builds. If you start profiling in a function that is called multiple times in the same stack and stop profiling at the end of the function, only the most recent calls are saved to disk as the logs will continue to cycle.

See Also