Jump to content

Bugfix for "LvlPredatorScript" errors. No more log spam.


steve40

Recommended Posts

  • Replies 100
  • Created
  • Last Reply

Top Posters In This Topic

I'm currently using the final v2 version in an attempt to fix the CTD's i've been experiencing with the lvlpredatorscript. However, I also have UKSP installed, and now my papyrus logs are being spammed hundreds of times with this:

 

[07/24/2013 - 10:17:13AM] warning: Property USKPPredatorEnableParent on script lvlpredatorscript attached to (00083E88) cannot be initialized because the script no longer contains that property

 

Is there any way to stop this from happening?

Yes, I'll add the new USKP properties to my scripts and it should stop those harmless warning messages.

 

Edit: OK, I've updated my scripts. The new versions shouldn't give those warning messages when you are using USKP 1.3.3. I'm still using an older version of USKP so I haven't tested this but it should work.

Edited by steve40
Link to comment
Share on other sites

This is awesome! I've just tested the new hack version (btw your archive is missing the "Scripts" subfolder but I installed it manually anyway) and it worked on every save file where I could reproduce the CTD reliably! Before, I used to crash immediately when encoutering a pack of wolves but with your script replacement the game stops for half a second and then just continues normally. I should notice that the log now creates two or three entries of this:

 

warning: Property USKPPredatorEnableParent on script lvlpredatorscript attached to (0003F8B4) cannot be initialized because the script no longer contains that property

I've just uploaded a new version of the "hack" script (v1.1) which should stop those warning messages. Cheers.

Link to comment
Share on other sites

 

 

This is awesome! I've just tested the new hack version (btw your archive is missing the "Scripts" subfolder but I installed it manually anyway) and it worked on every save file where I could reproduce the CTD reliably! Before, I used to crash immediately when encoutering a pack of wolves but with your script replacement the game stops for half a second and then just continues normally. I should notice that the log now creates two or three entries of this:

 

warning: Property USKPPredatorEnableParent on script lvlpredatorscript attached to (0003F8B4) cannot be initialized because the script no longer contains that property

I've just uploaded a new version of the "hack" script (v1.1) which should stop those warning messages. Cheers.

 

Thank you! :smile:

 

Just out of curiosity: what are the differences between the hack version and the normal one? Would be great to know for troubleshooting if new issues arise.

 

EDIT: Just played for two hours straight without a single crash. Even the logs are completly free of any warnings related to predators or critters. This is really great!

Link to comment
Share on other sites

I know this really doesn't have that much to do with the subject, but I was wondering if by some chance you have some bug fix for the script CompanionsRadiantQuest.psc, with the log errors related to the quest CR13, "Purity". I've seen many people having this problem, but without any fix. My papyrus is filleed with this errors:

 

[CR13 (000E3163)].cr13questscript.SetCurrentStageID() - "<native>" Line ?

[CR13 (000E3163)].cr13questscript.SetStage() - "Quest.psc" Line 124

[CR13 (000E3163)].companionsradiantquest.Setup() - "CompanionsRadiantQuest.psc" Line 41

[CR13 (000E3163)].cr13questscript.Setup() - "CR13QuestScript.psc" Line 26

[CR13 (000E3163)].QF_CR13_000E3163.Fragment_10() - "QF_CR13_000E3163.psc" Line 57

 

Are you familiar with this issue?

Link to comment
Share on other sites

I know this really doesn't have that much to do with the subject, but I was wondering if by some chance you have some bug fix for the script CompanionsRadiantQuest.psc, with the log errors related to the quest CR13, "Purity". I've seen many people having this problem, but without any fix. My papyrus is filleed with this errors:

 

[CR13 (000E3163)].cr13questscript.SetCurrentStageID() - "<native>" Line ?

[CR13 (000E3163)].cr13questscript.SetStage() - "Quest.psc" Line 124

[CR13 (000E3163)].companionsradiantquest.Setup() - "CompanionsRadiantQuest.psc" Line 41

[CR13 (000E3163)].cr13questscript.Setup() - "CR13QuestScript.psc" Line 26

[CR13 (000E3163)].QF_CR13_000E3163.Fragment_10() - "QF_CR13_000E3163.psc" Line 57

 

Are you familiar with this issue?

That quest is basically a horror show of bugs, both this back end garbage in the logs and gameplay bugs like Vilkas not following/talking after giving his version of the quest, or Farkas refusing to offer missions, or the heads bugging out, or not being able to use the fire to purify oneself, and so on. There's pretty much no way that quest ever went through QA.

 

http://www.uesp.net/wiki/Skyrim:Purity

 

http://www.uesp.net/wiki/Skyrim_talk:Purity

Link to comment
Share on other sites

  • 2 weeks later...
  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...