WeaponRackActivateScript nightmare

[RuaDragonheart]

So lately my papyrus logs have been spammed to hell and back with property errors in WeaponRackActivateSCRIPT. This hasn't ever happened to me before until late, and the only changes I've made that could possibly touch upon it are the Lost Wonders of Mzark mod and the recent updates to the unofficial patches.

I don't think it's the patches causing it, but from what I've researched, it's not Mzark either. Regardless, whatever the error is, it's taking USKP into account, as some of the property errors have USKP listed in the front. I'm not sure what to make of it, but a couple minutes of gameplay (not even five minutes) is generating a papyrus log that's anywhere from 5000kb to 8000+kb, and roughly 90% of it is things like thus:

[08/31/2013 - 11:45:31PM] warning: Property ArmorMaterialDaedric on script WeaponRackActivateScript attached to  (000CAA2B) cannot be initialized because the script no longer contains that property

[08/31/2013 - 11:45:31PM] warning: Property ArmorShieldofYsgramor on script WeaponRackActivateScript attached to  (000CAA2B) cannot be initialized because the script no longer contains that property

[08/31/2013 - 11:45:31PM] warning: Property DA15Wabbajack on script WeaponRackActivateScript attached to  (000CAA2B) cannot be initialized because the script no longer contains that property

[08/31/2013 - 11:45:31PM] warning: Property USKPWeaponRackWeaponDisallowedMESSAGE on script WeaponRackActivateScript attached to  (000CAA2B) cannot be initialized because the script no longer contains that property

Can you explain to me what could possibly be happening? Whatever it is, it's using the USKP to exacerbate an already huge problem. I'm getting crashes upon exiting an interior anywhere between seconds to minutes, and this is what my logs tell me.

 

I'd upload the log files themselves, but the size limit means that's never going to happen.

 

[IsharaMeradin]

The object(s) that has the script attached has these properties filled and stored within it's ESP or ESM file. The script however has been modified to not use those properties. Thereby causing Papyrus to print out a warning.

 

In your snippet the object that has the properties is 000CAA2B which is a stock Skyrim object. Chances are it was modified by USKP and another mod overwrote the script. Although I won't rule out the possibility that the USKP team missed clearing out unused properties on that particular object form when modifying the script from an old version to a new version. It is also possible that you've added a local version of the PEX file (for whatever reason) which is overriding the modified version in the USKP BSA.

 

I suggest using a tool that can read inside your BSA files and see which mod BSAs are supplying a PEX version of that file. Also check your Skyrim/Data/Scripts directory for the PEX version of that script. If you have one, check inside your mod archives (7z, zip, & rar files) for any that supply it.

 

After you've located the sources of this script, you can then do some tests to see if the issue resolves itself when one of them is removed. However, there would be no good solution short of examining the changes made to the script by each source and combining those changes if possible.

[sclerocephalus]

First, USKP has indeed updated the weapon rack scripts. More on this can be found here (although in parts rather technical, this thread will explain what changes were made and why they had to be made):

http://afkmods.iguanadons.net/index.php?/topic/3669-overhauling-the-weapon-rack-scripts/

 

Second, we did not miss to clear out unused properties. Clearing them out is one of the reasons why those warnings appear at all. Thus, unused properties from previous versions are usually kept when a script is modified.

 

Third, what you refer to as "property errors" are warnings not errors. There's a big difference between warnings and errors, and they are prefixed in the logs with either "warning" or "error" to make a clear distinction:

 

(1) Warnings are notifications sent by the engine.Warnings do not imply that anything isn't working; most of the time, they just inform you about script updates (keep in mind that the log was conceived as a developer's tool, and its main goal was to enable developers to keep track of changes critical to their own work when a group of people was working on the same project). After the official updates, your logs were full of similar messages as a result of various script updates. Those warnings are not lasting though (unlike errors) and will disappear over time when all affected instances have switched to the new scripts.

Also, warnings are NEVER logged during gameplay (and therefore, have no impact on performance). When you scroll down in your log, you should find a "VM is thawing" message right after the warnings block. This is where you actually entered the game.

(2) Errors do always imply a malfunction and have to be taken very serious. They are exclusively logged while playing and logging alone may have a considerable impact on performance.

 

Fourth, as already suspected by IsharaMeradin, the messages are indicating that you have a mod running which overrides the USKP weapon rack scripts. Possible culprits are mods that claim to fix the ebony blade problem. If you have one of them installed, you should uninstall it, since those mods have stopped working properly after the 1.9 patch (which appears to have introduced a new sort of reference that cannot be properly handled by papyrus).

 

Fifth, scripts are not the cause of whatever is crashing your game. All modifications that are potentially leading to crashes are completely out of reach for scripting applications.

[Brandonhortman]

ever resolve this?
I have an identical problem and haven't been able to resolve it.
I've uninstalled all mods, started new game, ect ect.