There's also another overall limitation on how long the engine will dedicate to the Papyrus VM per frame, shared across all currently running scripts, which is typically 1.2-2.4ms (fUpdateBudgetMS + fExtraTaskletBudgetMS ini settings). If there were a 10-call (A) and 100-call (B) function in the same circumstances, calls from functions A and B will behave similarly: A/1, B/1, A/2, B/2.until A/10 finishes around frame 20, and function B is free to run B/11, B/12 etc uninterrupted, finishing around frame 110. Multiple scripts on the same object are even worse, basically each delayed function call takes a 'ticket' and the engine handles each call in the order it was made so, two 10-function scripts that start running on the player simultaneously, for example, will typically run 'function A, call 1', 'function B, call 1', A/2, B/2, A/3, B/3.and so on to A/10, B/10. If you're at 10 FPS that'll be 1.0 second, 60 FPS it's 0.167s, 144 is it's 0.069s and so on. If you have some script that runs 10 delayed functions, you guessed it, that'll cost a minimum of 10 frames, provided no other scripts are running on the same objects. More accurately, the engine can do one native delayed function call per object per frame. any native function call that is not non-delayed, which is to say like 80-90% of them), the script has to wait until the next frame for that function call to finish. Basically any time a script has to either request/submit some data from/to the engine (i.e.

Fallout 4 fps fix mod