Jump to content

CritterSpawn causing CTD's?


mvplayer277

Recommended Posts

So I've been getting CTD's for the past few months now and have yet to stop them. Almost after 5 minutes of playing in game, whether I save or go to a menu or talk with an NPC, I would CTD. I think I've found the problem but I need help in solving it. I have this reoccurring message in my script logs:

 

[ (6A011526)].critterspawn.OnCellAttach() - "<savegame>" Line ?
[01/20/2014 - 09:45:29AM] Error: Argument variable "::bLooping_var" was not successfully looked up
stack:
[ (6A011527)].critterSpawn01.OnCellAttach() - "<savegame>" Line ?
[01/20/2014 - 09:45:29AM] Error: Argument variable "::bLooping_var" was not successfully looked up
stack:
[ (6A011526)].critterSpawn01.OnCellAttach() - "<savegame>" Line ?
[01/20/2014 - 09:45:29AM] Error: Argument variable "::bLooping_var" was not successfully looked up
stack:
[ (6A011527)].critterspawn.OnCellAttach() - "<savegame>" Line ?
[01/20/2014 - 09:45:30AM] Error: Argument variable "::bLooping_var" was not successfully looked up
stack:
[ (6A011526)].critterspawn.OnCellAttach() - "<savegame>" Line ?
[01/20/2014 - 09:45:31AM] Error: Argument variable "::bLooping_var" was not successfully looked up
stack:

 

Now I'm pretty sure that my game is CTD'ing because of script overload. The good part is is that I'VE FOUND THE CRITTER SPAWNERS THAT ARE CAUSING THESE PROBLEMS. They were added by a mod I'm using. Now…..

 

what do I do from here???? Any suggestions would be really helpful!

Link to comment
Share on other sites

  • 3 years later...
Same problem here. Found the thread by googling so I'm sorry for reviving. Have tried numerous fixes. Cleaned the .esms, tried the critter script fixes, have the unofficial patch installed. Last few lines of my papyrus log as follows:


[06/07/2017 - 03:51:43AM] error: Argument variable "bPrintDebug" was not successfully looked up

stack:

[ (000E930E)].critterSpawn01.OnCellAttach() - "<savegame>" Line ?

[06/07/2017 - 03:51:43AM] error: Argument variable "bPrintDebug" was not successfully looked up

stack:

[ (000E930E)].critterspawn.OnCellAttach() - "<savegame>" Line ?

[06/07/2017 - 03:51:43AM] error: Argument variable "recursions" was not successfully looked up

stack:

[ (000E930E)].critterSpawn01.OnCellAttach() - "<savegame>" Line ?

[06/07/2017 - 03:51:43AM] error: Attempting to manipulate variable "recursions" was not successfully looked up

stack:

[ (000E930E)].critterSpawn01.OnCellAttach() - "<savegame>" Line ?

[06/07/2017 - 03:51:43AM] error: Argument variable "recursions" was not successfully looked up

stack:

[ (000E930E)].critterspawn.OnCellAttach() - "<savegame>" Line ?

[06/07/2017 - 03:51:43AM] error: Attempting to manipulate variable "recursions" was not successfully looked up

stack:

[ (000E930E)].critterspawn.OnCellAttach() - "<savegame>" Line ?

[06/07/2017 - 03:51:43AM] error: Argument variable "bPrintDebug" was not successfully looked up

stack:

[ (000D213D)].critterspawn.OnCellAttach() - "<savegame>" Line ?

[06/07/2017 - 03:51:43AM] error: Argument variable "recursions" was not successfully looked up

stack:

[ (000D213D)].critterspawn.OnCellAttach() - "<savegame>" Line ?

[06/07/2017 - 03:51:43AM] error: Attempting to manipulate variable "recursions" was not successfully looked up

stack:

[ (000D213D)].critterspawn.OnCellAttach() - "<savegame>" Line ?



Edit: Despite the log pointing at critterspawn errors, the ctd is not because of this. Tested it a few times again, ran into the ctd cell before the critterspawn could even throw errors...the log is painfully useless to be honest.

Edited by Revyn
Link to comment
Share on other sites

  • 11 months later...
  • 3 months later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...