"Script no longer contains property" all over the place, how do I fix this?

[moddingnoob]

So, I can start a new game and play for a pretty long time now. But if I quit the game, or it crashes, and I go back to load the save, it ctds. And the only thing that seems to be the problem is these "script no longer contains that property" messages. Papyrus logs for new games don't show any of these issues.  

[Ashal]

You don't. This this a problem with mod authors not properly removing script properties that have been bound via the esp. (they remove it in the script, but don't unset it in the esp.)

 

It's annoying if you look at papyrus logs, but it's completely harmless otherwise. 

[moddingnoob]

You don't. This this a problem with mod authors not properly removing script properties that have been bound via the esp. (they remove it in the script, but don't unset it in the esp.)

 

It's annoying if you look at papyrus logs, but it's completely harmless otherwise. 

Then why is my game crashing all the time? The memory block usage only gets to around 138 or so before the crashes happen, everything seems to be in order correctly. I can start new games and play those, but I can't load anything.

[yatol]

And the only thing that seems to be the problem is these "script no longer contains that property" messages. Papyrus logs for new games don't show any of these issues.  

 

it's because of that you don't mess with your load order without restarting the game

 

you had mod x 1.0

you have upgrade it to mod x 1.2

stuff from 1.0 that is in the save, stay in the save

result is a mashup between 1.0 and 1.2

[Ashal]

That's an entirely different can of worms that's impossible to answer without first knowing when/where the game crashes, posting the papyrus log in question, your load order and/or mod install order (from MO's left pane, right pane is load order), and if you can successfully load the crashing save after first starting a new game and then loading the save once you've successfully loaded that new game - which in my experience is a very common problem+fix for saves that crash on load pretty regularly.

 

First recommendations regardless though, I think, are pretty standard and solve things the majority of times for this sort of issue. 

1. Clean your vanilla ESM files if you haven't yet.
2. Run a save game script cleaner, such as papyrus script scalpel, to remove any unused and/or stuck scripts in your save file. 

[moddingnoob]

 

And the only thing that seems to be the problem is these "script no longer contains that property" messages. Papyrus logs for new games don't show any of these issues.  

 

it's because of that you don't mess with your load order without restarting the game

 

you had mod x 1.0

you have upgrade it to mod x 1.2

stuff from 1.0 that is in the save, stay in the save

result is a mashup between 1.0 and 1.2

 

 

I haven't upgraded anything.

[moddingnoob]

 

That's an entirely different can of worms that's impossible to answer without first knowing when/where the game crashes, posting the papyrus log in question, your load order and/or mod install order (from MO's left pane, right pane is load order), and if you can successfully load the crashing save after first starting a new game and then loading the save once you've successfully loaded that new game - which in my experience is a very common problem+fix for saves that crash on load pretty regularly.

 

First recommendations regardless though, I think, are pretty standard and solve things the majority of times for this sort of issue. 

1. Clean your vanilla ESM files if you haven't yet.
2. Run a save game script cleaner, such as papyrus script scalpel, to remove any unused and/or stuck scripts in your save file. 

 

Ok, I did that, and it seems that cleaning the esm files worked to, some extent. I was able to play for almost an hour. But then the game crashed, and I couldn't even start a new game without it crashing after the load screen. Running LOOT allowed me to start a new game, and then I tried to load my old game, but it crashed. Same deal with the new games, and same deal with LOOT. It's a weird problem. Attached is the most recent papyrus log.

Papyrus.0.log