 Issue Data
|
|
||||||||||||||||||||||||||||||
Issue #30585: Three possible papyrus errors
Related Issues: 31503
#1: This is a bogus error which supposedly occurs when a script calls Start() on a scene that is running already.
#2: As we found out in the meantime, this is another bogus error. Animations may send animation events in specific stages of an animation. These are defined in the animation files, and when a script calls for the animation to be played on an object, the game tries to send these events to that script no matter what. If the script never registered for the events, this will fail with this error. Scripts normally register for animation events only when they need to process them. If they don't need to process them, registering anyway would be a complete waste of time, so they live with the errors instead. The errors can be avoided by letting the script register for all enimation events that can possibly be sent and add empty event handlers for each one of them. There is no gain in doing this, other than avoiding the errors, so they are best left alone [NB: we fixed this only in a few cases of "frequent spammers"].
#3: It's way better with the fix. The vanilla script always threw nine errors in a row and it's now only one occasionally.
#2: As we found out in the meantime, this is another bogus error. Animations may send animation events in specific stages of an animation. These are defined in the animation files, and when a script calls for the animation to be played on an object, the game tries to send these events to that script no matter what. If the script never registered for the events, this will fail with this error. Scripts normally register for animation events only when they need to process them. If they don't need to process them, registering anyway would be a complete waste of time, so they live with the errors instead. The errors can be avoided by letting the script register for all enimation events that can possibly be sent and add empty event handlers for each one of them. There is no gain in doing this, other than avoiding the errors, so they are best left alone [NB: we fixed this only in a few cases of "frequent spammers"].
#3: It's way better with the fix. The vanilla script always threw nine errors in a row and it's now only one occasionally.
For #3, it looks like there are two events that call the Stop command which triggers the deletion calls:
Only one of these is actually required, and generally speaking OnCellDetach() is more reliable.
The issue in 13768 was caused by the same script, but was due to the presence of multiple deletion statements for invalid aliases.
Event OnUnload() DLC01_WESC03.Stop() EndEvent Event OnCellDetatch() DLC01_WESC03.Stop() EndEvent
Only one of these is actually required, and generally speaking OnCellDetach() is more reliable.
The issue in 13768 was caused by the same script, but was due to the presence of multiple deletion statements for invalid aliases.
Since we're not addressing the first two due to them being false errors, I'll comment on the 3rd. That one was addressed in a subsequent patch at some point by disabling the OnLoad() block, which led to problems because the script had a typo in the OnCellDetach() event name.
That issue has been fixed already, which means this ticket no longer has any valid things to address.
That issue has been fixed already, which means this ticket no longer has any valid things to address.
Showing Comments 1 - 3 of 3