Jump to content

Papyrus Script CTD


hentaishinri

Recommended Posts

  On 3/28/2013 at 5:07 PM, ragnaroklucifer said:

 

  On 3/28/2013 at 4:55 PM, hentaishinri said:

what does that mean D:

I'm not good with any of this stuff, I only know how to install mods and how to clean them (ripple taught me :biggrin:), but idk what that means -_-

Have you checked where footprintsAddFootstepsScript, _WetCloakAttach, DuelAddAbilityScript these 3 scripts come from?

how exactly do i do that :/

 

 

  On 3/28/2013 at 5:12 PM, ripple said:

I'd still like to see your BOSS log, just because I have a fetish for BOSS logs, so humour me.

 

I love that phrase, lol.

ANyway, here you go, hope it helps

 

  Reveal hidden contents

Link to comment
Share on other sites

  • Replies 53
  • Created
  • Last Reply

Top Posters In This Topic

  On 3/28/2013 at 5:23 PM, ripple said:

Actually, the waiting time displayed (at least on my end) is '20 seconds', but it won't start and keeps asking me to sign up for a free account.

Oh yea, it's 20 seconds . And yea I did not realise I'm logged in. lol

 

  Quote

how exactly do i do that :/

Well, I use mod organizer so I can easily find which folder (mod) the script file belong to...

Edited by ragnaroklucifer
Link to comment
Share on other sites

  On 3/28/2013 at 5:26 PM, ragnaroklucifer said:

 

  Quote

how exactly do i do that :/

Well, I use mod organizer so I can easily find which folder (mod) the script file belong to...

well if u meant to search the mods folder - i just did. The only thing that came out was 'DuelAddAbilityScript' from 'Duel - combat realism' mod

Link to comment
Share on other sites

The stack dumps in your papyrus log are due to too many calls to check the same event(s) on the same object at one time. I had similar stack dumps with a bag of holding mod that I'd been working on which used the OnItemAdded & OnItemRemoved events. I found if I moved items in large groups that I'd get stack dumps because not only was my mod checking the OnItemAdded & OnItemRemoved events so too was Hearthfire. In my case the game kept working, then again I didn't have as many stack dumps as frequently as your log indicates.

 

I do not know if you've used these mods before. If you have, then it may be due to an update in one or more of the mods which changed how things were scripted. I do see evidence at the top of your log about missing scripts. That indicates uninstalled mods or updated mods that dropped scripts for some reason. Unfortunately that can cause some unintended side effects too.

 

Since you are re-installing the game, I would recommend picking your mods with caution. Test them individually for any issues. Test them together for compatibility issues. Then when satisfied start a fully new game. Many issues are caused by changing mods mid-game and trying to continue playing. Not every mod can just be dropped out of the game. Sticking with a fixed load order & fixed versions for the life of a playthrough lends itself to a more stable game.

Link to comment
Share on other sites

  On 3/28/2013 at 5:48 PM, IsharaMeradin said:

The stack dumps in your papyrus log are due to too many calls to check the same event(s) on the same object at one time. I had similar stack dumps with a bag of holding mod that I'd been working on which used the OnItemAdded & OnItemRemoved events. I found if I moved items in large groups that I'd get stack dumps because not only was my mod checking the OnItemAdded & OnItemRemoved events so too was Hearthfire. In my case the game kept working, then again I didn't have as many stack dumps as frequently as your log indicates.

 

I do not know if you've used these mods before. If you have, then it may be due to an update in one or more of the mods which changed how things were scripted. I do see evidence at the top of your log about missing scripts. That indicates uninstalled mods or updated mods that dropped scripts for some reason. Unfortunately that can cause some unintended side effects too.

 

Since you are re-installing the game, I would recommend picking your mods with caution. Test them individually for any issues. Test them together for compatibility issues. Then when satisfied start a fully new game. Many issues are caused by changing mods mid-game and trying to continue playing. Not every mod can just be dropped out of the game. Sticking with a fixed load order & fixed versions for the life of a playthrough lends itself to a more stable game.

Yes, these are the mods I've always been using (plus-minus a few added, but most of them I'm using for a long time.). The ctd started mostly with the unofficial patches. Al thought I already did that, I suppose it won't hurt to do it again, so I will install each of them individually and test them.. -sigh- it's going to be a long night...

Link to comment
Share on other sites

[03/28/2013 - 05:21:44PM] Cannot open store for class USKP_YsoldaBelethorWorkaround", missing file?
[03/28/2013 - 05:21:44PM] warning: Unable to get type USKP_YsoldaBelethorWorkaround referenced by the save game. Objects of this type will not be loaded.
[03/28/2013 - 05:21:44PM] Cannot open store for class "USKP_QF_ChangeLocation06_02015A54", missing file?
[03/28/2013 - 05:21:44PM] warning: Unable to get type USKP_QF_ChangeLocation06_02015A54 referenced by the save game. Objects of this type will not be loaded.
[03/28/2013 - 05:21:45PM] warning: Could not find type USKP_QF_ChangeLocation06_02015A54 in the type table in save
[03/28/2013 - 05:21:45PM] warning: Could not find type USKP_YsoldaBelethorWorkaround in the type table in save

Have you uninstalled anything? Have you, at any point, turned off USKP and made a savegame without it?

 

[03/28/2013 - 05:23:24PM] Suspended stack count is over our warning threshold, dumping stacks:

I would think this would be responsible for your CTDs only if too many scripts were suspended over a short period of time. Well...it does repeat a few times before your game finally choked....

 

I think you should delete the change you made to your ini. Papyrus is not good at handling anything large and increasing the value of 'MaxAllocatedMemoryBytes' isn't necessarily going to make the script engine perform better. I seem to recall reading a forum thread on this that I can't find any more, which eventually degenerated into a 'war' between the users who offered anecdotal 'evidence' on its performance improvements and the 'it's just a placebo effect...' folks.

 

You can also try starting a new game without 'Duel' (I know you said you didn't want to trim the load order, but.....). You are using the Mod Organizer now, you don't need to 'reinstall' anything or 'clean install' the game (MO does not install mods into the game data folder, so the game data folder is/should be already 'clean). Just uninstall any mod(s) you don't want to use from the 'mod installed' menu in MO, rebuild your compatibility patches (e.g. Bashed Patch), then start a new game. And make sure all of your mods are updated to the latest version. If testing, just temporarily disable 'installed mods' by unchecking them. The mod plugin and any associated resources will no longer appear in the MO virtual data folder.

 

And can you post your game ini files already?

Edited by ripple
Link to comment
Share on other sites

  On 3/28/2013 at 5:48 PM, IsharaMeradin said:

The stack dumps in your papyrus log are due to too many calls to check the same event(s) on the same object at one time. I had similar stack dumps with a bag of holding mod that I'd been working on which used the OnItemAdded & OnItemRemoved events. I found if I moved items in large groups that I'd get stack dumps because not only was my mod checking the OnItemAdded & OnItemRemoved events so too was Hearthfire. In my case the game kept working, then again I didn't have as many stack dumps as frequently as your log indicates.

 

I do not know if you've used these mods before. If you have, then it may be due to an update in one or more of the mods which changed how things were scripted. I do see evidence at the top of your log about missing scripts. That indicates uninstalled mods or updated mods that dropped scripts for some reason. Unfortunately that can cause some unintended side effects too.

 

Since you are re-installing the game, I would recommend picking your mods with caution. Test them individually for any issues. Test them together for compatibility issues. Then when satisfied start a fully new game. Many issues are caused by changing mods mid-game and trying to continue playing. Not every mod can just be dropped out of the game. Sticking with a fixed load order & fixed versions for the life of a playthrough lends itself to a more stable game.

try removing those mods first. Then use SKSE to clearinvalidregistrations. And load those mods back.

 

EDIT: since you deleted the game save, this wouldn't help anymore ...

Edited by ragnaroklucifer
Link to comment
Share on other sites

  On 3/28/2013 at 6:05 PM, ripple said:

 

[03/28/2013 - 05:21:44PM] Cannot open store for class USKP_YsoldaBelethorWorkaround", missing file?
[03/28/2013 - 05:21:44PM] warning: Unable to get type USKP_YsoldaBelethorWorkaround referenced by the save game. Objects of this type will not be loaded.
[03/28/2013 - 05:21:44PM] Cannot open store for class "USKP_QF_ChangeLocation06_02015A54", missing file?
[03/28/2013 - 05:21:44PM] warning: Unable to get type USKP_QF_ChangeLocation06_02015A54 referenced by the save game. Objects of this type will not be loaded.
[03/28/2013 - 05:21:45PM] warning: Could not find type USKP_QF_ChangeLocation06_02015A54 in the type table in save
[03/28/2013 - 05:21:45PM] warning: Could not find type USKP_YsoldaBelethorWorkaround in the type table in save

Have you uninstalled anything? Have you, at any point, turned off USKP and made a savegame without it?

 

[03/28/2013 - 05:23:24PM] Suspended stack count is over our warning threshold, dumping stacks:

I would think this would be responsible for your CTDs only if too many scripts were suspended over a short period of time. Well...it does repeat a few times before your game finally choked....

 

I think you should delete the change you made to your ini. Papyrus is not good at handling anything large and increasing the value of 'MaxAllocatedMemoryBytes' isn't necessarily going to make the script engine perform better. I seem to recall reading a forum thread on this that I can't find any more, which eventually degenerated into a 'war' between the users who offered anecdotal 'evidence' on its performance improvements and the 'it's just a placebo effect...' folks.

 

You can also try starting a new game without 'Duel' (I know you said you didn't want to trim the load order, but.....). You are using the Mod Organizer now, you don't need to 'reinstall' anything or 'clean install' the game (MO does not install mods into the game data folder, so the game data folder is/should be already 'clean). Just uninstall any mod(s) you don't want to use from the 'mod installed' menu in MO, rebuild your compatibility patches (e.g. Bashed Patch), then start a new game. And make sure all of your mods are updated to the latest version. If testing, just temporarily disable 'installed mods' by unchecking them. The mod plugin and any associated resources will no longer appear in the MO virtual data folder.

 

And can you post your game ini files already?

Thanks, ripple (again), for your input ^^.

I'll try the game without 'Duel' and then I'll try it with it, see if any changes occur.

Okay, geez, here are the ini files :biggrin: (you really love to be throughout, hm? Nothing wrong with that, actually, very objective)

Skyrim.ini

 

  Reveal hidden contents

 

SkyrimPrefs.ini

 

  Reveal hidden contents

 

Edit: I will restore the ini files to default and not mess with them, by your reference. Doing a clean start anyway, might as well do it right.

And yes, I understand that MO doesn't store the files directly into skyrim folders... but I like to be throughout sometimes too xD

Edited by hentaishinri
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...