IHateMyKite
commented
2 years ago These errors might seems bad, but they are really not. What is it saying is that Devious Strike tried to lock device which occupy slot which is already occupied by other device. This is little complicated to explain and even DD didn't have this safety check. In general every render device takes some slot. And all slots have associated some devious keyword. But every device have only one "major" keyword, which is used to check if device is not in conflict.
But lets have following example: Player will get locked in pair of plugs. It will be device which takes both Anal and Vaginal slot, but doesn't have vaginal keyword. But the major keyword will be only zad_deviouspluganal. Now lets say that another device will try to be locked on. Simple vaginal plug, which have major keyword zad_deviousplugvaginal. DD will actually allow the device to be locked on, because they have different major keywords. And the skyrim engine works in a way that if there is attempt to equip armor in to slot which is already occupied, it will swap the armor. But in this case that is not possible because devices are equipped with function actor.equipitem() with argument to prevent armor unequip. This makes DD to add render device on to actor but not equip it. This is very bad for UD, because all information is stored in Render device. So I had to add check to see if device can be even equipped.
But, now back to the issue. It's strange that it is calling LockDevice when they are despawned. Did you just kill them or did they despawned because they defeated you? It's also possible that issue is unrelated to them despawning, maybe some just spawned outside your view.
BreadDain
Description: When Devious Strike despawns one of the mods enemies (Strikers) and strips them from bondage, UD produces a lot of errors both in message popup area and console
Version of skyrim: SE Version of mod: 2.0b13