-
Notifications
You must be signed in to change notification settings - Fork 66
Description
The problem is difficult to explain, so here's what I'd like to point out
Begin ScriptEffectUpdate
PrintD "ScriptEffectUpdate1"
; This script effect can be interrupted by a Quest Script here
PrintD "ScriptEffectUpdate2"
; Or here...
PrintD "ScriptEffectUpdate3"
; Or here...
; etc.
End
I don't know if this is the expected behaviour, but I find it abnormal for a script to be interrupted in the middle of execution by something other than Events. The problem occurs randomly but is obviously much easier to reproduce with Low Processing Delay.
One of the other disadvantages of the problem I'm describing is that when the console logs are saved, there's a good chance that the data in the Log file will be erased. Using ‘PrintD’ deletes the logs whereas ‘WriteStringToFile’ keeps them.
I therefore created a very simple mod ‘TestLog.esp’ in order to isolate the problem and reproduce it easily.
TestLog.zip
Here are the logs I get when I use WriteStringToFile (cause PrintD deletes the contents of the log file when the problem occurs):

Note : This result was generated with NVSE 6.3.5b and only FalloutNV.esm and TestLog.esp loaded.