Critter script bugfix

Xubarku · August 2, 2013

Tested, and you're right, it works perfect now. Thanks for the speedy fix; I couldn't of asked for anything better. :)

steve40 · August 2, 2013

@MarkusFox: the reason that some critters won't spawn reliably when only using the USKP version of the critter fixes is that USKP changed CritterSpawn.psc to use "OnCellAttach" instead of "OnLoad" to trigger spawning because they claimed it is "more reliable". I still use the "OnLoad" event in these scripts and it works very well, so I don't understand why they changed it.

pillullis · August 3, 2013

Everyone, please note that it is very important that you never ever run "Skyrim Save Cleaner" on your savegames. Objects such as critters place hidden markers in the game to calculate the coordinates required for landing on plants and stuff. Mods like "Skyrim Save Cleaner" may unintentionally delete these hidden markers causing the critter scripts to break. While you might think that you are "cleaning up" broken scripts from your save game, you are in fact making the problem worse! If you get a lot of "none object" type errors in your logs, it could well be the product of "cleaning" your save.

What if I use the ClearInvalidRegistrations of SKSE?

steve40 · August 3, 2013

What if I use the ClearInvalidRegistrations of SKSE?

That won't have any effect on critters.

Nearox · September 4, 2013

hey steve40 thanks for these fixes. I used to have a vatiation of critter spam throughout the log.

I have installed your fixes and put them right after USKP 1.3.3c in Mod Organizer. All the previous critter spam is gone. However, I now encounter a new error

[09/04/2013 - 01:12:34AM] Error: Argument variable "bPrintDebug" was not successfully looked up
stack:
	[ (0010A2B2)].critterspawn.OnLoad() - "<savegame>" Line ?
[09/04/2013 - 01:12:34AM] Error: Argument variable "recursions" was not successfully looked up
stack:
	[ (0010A2B2)].critterspawn.OnLoad() - "<savegame>" Line ?
[09/04/2013 - 01:12:34AM] Error: Attempting to manipulate variable "recursions" was not successfully looked up
stack:
	[ (0010A2B2)].critterspawn.OnLoad() - "<savegame>" Line ?
[09/04/2013 - 01:12:34AM] Error: Argument variable "bPrintDebug" was not successfully looked up
stack:
	[ (000CB032)].critterSpawn01.OnLoad() - "<savegame>" Line ?
[09/04/2013 - 01:12:34AM] Error: Argument variable "bPrintDebug" was not successfully looked up
stack:
	[ (000CB032)].critterspawn.OnLoad() - "<savegame>" Line ?
[09/04/2013 - 01:12:34AM] Error: Argument variable "recursions" was not successfully looked up
stack:

After playing the game for 10minutes, the papyrus log is already 150kb and is filled with this error hundreds of times (there are no other recurring errors in the log).

I am running a full Skyrim Revisited install (I suppose you know it, it's sort of an advanced version of STEP). This is the last error of the papyrus log that I'm having to deal with. If I solve this my game will be 100% clean. The test run of this Papyrus log was done on a clean savegame, with a level 1 character running around the wider riverwood area.

I was hoping you could help me out. If you need more information let me know.

mindw0rk2 · September 18, 2013