Construction Set Master Error Crashing CS, NiControllerSequence:StoreTargets Options

[mALX]

*

Please note: This is not effecting the game at all, just the Construction Set =

It is presenting 8 errors per every NPC in every cell, overwhelming the CS and crashing it in any areas with many NPC's (and making it impossible to move around in the CS).


Here is the error message:


NiControllerSequence:StoreTargets 'Characters\_Male\idle.kf'failed to find target with the following identifiers:

m_pcAVObjectNameBip01 Tackle
m_pcCtrlr Type NiTransformController
m_pcPropertyType (null)


Continue Playing?

"Yes to all" will disable all Warnings this session.


Ditto above except line 3 =

m_pcAVObjectNameBip01 Tackle1
m_pcAVObjectNameBip01 Tackle2
m_pcAVObjectNameBip01 Tackle3
m_pcAVObjectNameBip01 Tackle4
m_pcAVObjectNameBip01 Tackle5
m_pcAVObjectNameBip01 Tackle6
m_pcAVObjectNameBip01 Tackle7


I deleted every mod related .kf file (moved the folder to desktop) - didn't fix the issue.

I downloaded and installed a new "Universal Skeleton" - didn't fix the issue.

Urk - does anyone know any other solutions?


The odd part about this is - haven't added/modified any NPC's or animations before this started happening; this just popped up out of the blue.


*

[ghastley]

It's not totally clear whether that's the .kf file having entries for non-existent bones, or the other way round. It could be that the CS is telling you it doesn't have a controller for moving the new bone. Either way, it's just a warning, but it appears it's the flood that causes the problem.

If it doesn't happen without the new skeleton, I'd assume the latter.

Add one new thing at a time, and see which one triggers it.

If you downloaded a new skeleton which replaces skeleton.nif, rather than adding an extra one with a different name, that could be a problem. There's a good reason that skeletonbeast.nif has a separate name, rather than just live in a separate folder as skeleton.nif, like the creature ones.

This post has been edited by ghastley: Oct 24 2013, 04:46 PM

[mALX]

It's not totally clear whether that's the .kf file having entries for non-existent bones, or the other way round. It could be that the CS is telling you it doesn't have a controller for moving the new bone. Either way, it's just a warning, but it appears it's the flood that causes the problem.

If it doesn't happen without the new skeleton, I'd assume the latter.

Add one new thing at a time, and see which one triggers it.

It was happening already, I downloaded the new skeleton trying to fix the issue.

(Also tried removing all the mod added .kf files by moving them to the desktop in an attempt to fix the issue)

This just started kind of out of the blue, the only thing I added was a bunch of MEO static food nifs.




This post has been edited by mALX: Oct 24 2013, 04:51 PM