Jump to content
  • 0

Enabling Papyrus Logs causes CTD on Game Load


Question

Posted

Whenever I enabled Papyrus logging in my skyrim.ini, my game instant crashes at main menu. As soon as I disable logging I can load and play again, whats going on? I saw over at the STEP guide Troubleshooting page to enable logging by instead creating a skyrimcustom.ini in the my gamesskyrim folder, but when I do that no log is generated. In the short time the game loads up and then crashes with logging enabled I do get the following in my Papyrus log:[09/20/2014 - 12:39:31PM] Papyrus log opened (PC)[09/20/2014 - 12:39:31PM] error: Native function GetUseSound in empty state does not match existing signature on linked type Potion. Function will not be bound.[09/20/2014 - 12:39:31PM] Update budget: 1.200000ms (Extra tasklet budget: 1.200000ms, Load screen budget: 500.000000ms)[09/20/2014 - 12:39:31PM] Memory page: 128 (min) 512 (max) 76800 (max total)[09/20/2014 - 12:39:40PM] Cannot open store for class "EXP_PRKF_CommandFollower_0100BAA0", missing file?[09/20/2014 - 12:39:40PM] Error: Unable to bind script EXP_PRKF_CommandFollower_0100BAA0 to (0D000F11) because their base types do not match[09/20/2014 - 12:39:40PM] Cannot open store for class "fissinterface", missing file?[09/20/2014 - 12:39:40PM] Cannot open store for class "_arissa_inpc_behavior", missing file?[09/20/2014 - 12:39:40PM] Cannot open store for class "chherdingquestscript", missing file?

 

The reason I want Papyrus logging enabled is cause I am getting some random CTD. They aren't too bad considering the Mod setup I got going (STEP Extended, stuff from Skyrim Revisted Legendary Edition, STEP Immersion Packs, STEP Weather and Lighting Pack, and Skyrim Redone, interesting NPC's, and Expanded Towns and Cities)

 

Anyway, I am still relatively at the beginning of a new game and want to get rid of these CTD's before I get too far in. I would also really just like for Papyrus logging to work in case I need it later on.

3 answers to this question

Recommended Posts

  • 0
Posted (edited)

As I believe apollo said, disable papyrus debugging and never turn it on. Your problem is not from papyrus.

Well, okay I paraphrased but it's most likely random error reference inside an old skyre patch....

Edited by hishutup
  • 0
Posted

Ah, found the quote:

"For the third time this week, and 9 trillionth time this year:

TURN OFF YOUR PAPYRUS LOGGING. THERE IS NEVER A REASON TO TURN IT ON IF YOU DON'T KNOW WHAT YOU ARE DOING. LEAVING IT ON MEANS THAT YOU DON'T." -Apollodown

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

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

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.