Help, 64 errors / second on my papyrus log (always the same errors)&#3

[juanjux]

Hi,

 

Yesterday while playing I noticed some slugginess after I left a dwemer dungeon. I enabled the papyrus log and I see that I'm getting about 64 errors every single second after the game has loaded the save and until I close. The game doesn't CTDs. The errors are related to three dwemer thresher traps with ids 00052475, 00052474 and 00052455:

 

[02/06/2013 - 09:03:22AM] warning: (00052475): currently does not have 3d and cannot register for animation callbacks. Returni.

stack:

[ (00052475)].TrapDweThresher.WaitForAnimationEvent() - "<native>" Line ?

[ (00052475)].TrapDweThresher.fireTrap() - "TrapDweThresher.psc" Line 71

[ (00052475)].TrapDweThresher.OnCellAttach() - "MovingTrap.psc" Line 76

[02/06/2013 - 09:03:22AM] warning: (00052474): currently does not have 3d and cannot register for animation callbacks. Returni.

 

(and this is repeated for the other two traps, 00052474 and 00052455).

 

I've tried to do a "trid 00052475" and "disable" and saving on the console, but the errors won't go away even if I restart the game.

[steve40]

Those traps are in cell "Bthardamz02".

Use the console to COC to that cell and then make a new save. Visiting that cell should make the traps reload their 3D and the errors should hopefully go away. If it works, play using the new save.

Edited February 6, 2013 by steve40

[juanjux]

THAT did it, thanks! After doing it the errors didn't stop, so I also did a resetinterior Bthardamz02, but after a pcb-save-qqq and reopen the errors stopped.

 

Where can you search what cell an id belongs to?

 

Those traps are in cell "Bthardamz02".

Use the console to COC to that cell and then make a new save. Visiting that cell should make the traps reload their 3D and the errors should hopefully go away. If it works, play using the new save.

[juanjux]

I spoke too fast. On the next reload, the errors are back :(

 

I also tried to do a MarkForDelete and disable of the trap ids, but nothing seems to work.

[steve40]

I've had a look at the TrapDweThresher.psc script. Manually disabling the trap will actually cause the problem!

 

You see, the script has a loop that waits for the trap firing animation to finish. If the cell detaches while the loop is running, a flag is set that should force the loop to quit.

However, if the 3D of the trap is forced to unload by any means other than a "cell detach" event (such as by disabling the trap via console), the flag won't get set, so the loop will continue to run and will spam the log with errors (because some script functions won't work if the 3D is not loaded).

 

What needs to be done to fix the problem:

 

a) if the trap is disabled, it needs to be re-enabled. If it's possible to use the trap's ID to enable it using the console, then do so.

b) the "isLoaded" flag needs to be set to false. I'm not sure if this console command will work (I haven't tried it before), but use "SetPapyrusVariable" on the problem traps. You want to set the variable "isLoaded" to "false". That should kill the loop that is spamming your log.

 

This is all theoretical, btw, so no guarantees it will work. Good luck.

[juanjux]

That worked, this time for good (saved and reloaded several times, changed cell, etc). I also installed Creation Kit and changed the script to check if it has the 3d loaded or parent cell, my first scripting change in Skyrim :) Anyway the trap is bugged because when you enable it and then try to disable it again with the lever, only two of the four "theshers" disable, two are left running until you disable them with the console.

 

Thanks for your help!

 

 

 

I've had a look at the TrapDweThresher.psc script. Manually disabling the trap will actually cause the problem!

 

You see, the script has a loop that waits for the trap firing animation to finish. If the cell detaches while the loop is running, a flag is set that should force the loop to quit.

However, if the 3D of the trap is forced to unload by any means other than a "cell detach" event (such as by disabling the trap via console), the flag won't get set, so the loop will continue to run and will spam the log with errors (because some script functions won't work if the 3D is not loaded).

 

What needs to be done to fix the problem:

 

a) if the trap is disabled, it needs to be re-enabled. If it's possible to use the trap's ID to enable it using the console, then do so.

b) the "isLoaded" flag needs to be set to false. I'm not sure if this console command will work (I haven't tried it before), but use "SetPapyrusVariable" on the problem traps. You want to set the variable "isLoaded" to "false". That should kill the loop that is spamming your log.

 

This is all theoretical, btw, so no guarantees it will work. Good luck.