devious skyrim Unforgiving Devices

[girmrad]

5 hours ago, ihatemykite said:

I tried to replicate the bug but didn't manage to. UD was running without issue. Can you share the whole Papyrus log ? If you have trace enabled, it should also print some additional info which might help to figure out what is wrong. I also updated the script which is not loading so it will now also print what exact submodules are having issue. Please, try new NB and let me know what it is saying.

I've attached the full log. I'll try the new nightly build a report back soon.

Papyrus.0.log

[girmrad]

I tried the new nightly build and it still failed to launch. The end of my Papyrus log had the following. I've also attached the entire log from the new attempt.

Spoiler

[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.663002]: !!FATAL ERROR!! = Error loading Unforgiving devices. One or more of the modules are not ready. Please contact developrs on LL or GitHub
[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.663002]: !!FATAL ERROR!! = Error loading Unforgiving devices. One or more of the modules are not ready. Please contact developrs on LL or GitHub
[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.727005]: UDPatcher=TRUE
[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.743004]: UDPatcher=TRUE
[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.775009]: UDCD_NPCM=False
[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.791008]: UDCD_NPCM=False
[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.807007]: UDEM=TRUE
[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.823006]: UDEM=TRUE
[03/28/2023 - 12:44:14PM] ERROR: Cannot call GetBaseDamage() on a None object, aborting function call
stack:
    [alias NPCSlot_Player on quest UD_NPCSlotsManager_Quest (D714E7EB)].ud_playerslotscript.OnItemAdded() - "UD_CustomDevice_NPCSlot.psc" Line 1680
[03/28/2023 - 12:44:14PM] WARNING: Assigning None to a non-object variable named "::temp553"
stack:
    [alias NPCSlot_Player on quest UD_NPCSlotsManager_Quest (D714E7EB)].ud_playerslotscript.OnItemAdded() - "UD_CustomDevice_NPCSlot.psc" Line 1680

Papyrus.0.log

[ihatemykite]

2 hours ago, girmrad said:

I tried the new nightly build and it still failed to launch. The end of my Papyrus log had the following. I've also attached the entire log from the new attempt.

  Hide contents

[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.663002]: !!FATAL ERROR!! = Error loading Unforgiving devices. One or more of the modules are not ready. Please contact developrs on LL or GitHub
[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.663002]: !!FATAL ERROR!! = Error loading Unforgiving devices. One or more of the modules are not ready. Please contact developrs on LL or GitHub
[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.727005]: UDPatcher=TRUE
[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.743004]: UDPatcher=TRUE
[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.775009]: UDCD_NPCM=False
[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.791008]: UDCD_NPCM=False
[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.807007]: UDEM=TRUE
[03/28/2023 - 12:44:14PM] [UD,INFO,T=112.823006]: UDEM=TRUE
[03/28/2023 - 12:44:14PM] ERROR: Cannot call GetBaseDamage() on a None object, aborting function call
stack:
    [alias NPCSlot_Player on quest UD_NPCSlotsManager_Quest (D714E7EB)].ud_playerslotscript.OnItemAdded() - "UD_CustomDevice_NPCSlot.psc" Line 1680
[03/28/2023 - 12:44:14PM] WARNING: Assigning None to a non-object variable named "::temp553"
stack:
    [alias NPCSlot_Player on quest UD_NPCSlotsManager_Quest (D714E7EB)].ud_playerslotscript.OnItemAdded() - "UD_CustomDevice_NPCSlot.psc" Line 1680

Papyrus.0.log 450.4 kB · 0 downloads

Thank you for sharing. I still don't know what exactly is causing it, but I did number of adjustment so I hope that it will now work. Try the new NB once the commit https://github.com/IHateMyKite/UnforgivingDevices/commit/cfd447518fe37400cc9e1e6b7e29e757f135604f is build. I also fixed the error which was showing at the end of the log with the OnItemAdded event

[greatwulf]

Ok maybe i'm just dumb but how do you get the extra animations from the SLAL packs (billy, leito etc.) to work with UDAnimations ? Do you just install them and activate them with the anim loader or do you need some extra steps for it to be recognized by UD ?

[ihatemykite]

4 minutes ago, greatwulf said:

Ok maybe i'm just dumb but how do you get the extra animations from the SLAL packs (billy, leito etc.) to work with UDAnimations ? Do you just install them and activate them with the anim loader or do you need some extra steps for it to be recognized by UD ?

From my understanding, no more steps are required. Only install the animation package and run FNIS. It should then show in UD MCM animation tab. But UD only support few packs which were made explicitly compatible by @iivanvv. For now it supports following packages

[iivanvv]

17 hours ago, greatwulf said:

Do you just install them and activate them with the anim loader or do you need some extra steps for it to be recognized by UD ?

 

Install and activate in mod list. No need to register animations in SexLab or anything.

 

- DD 5.2 beta (solo struggle, horny/orgasm animations).
- Zaz Animation Pack 8.0+ (probably 7.0 too) (solo struggle, horny/orgasm animations).
- Babo Human SLAL Pack version 25.06.2022 or later (paired struggle).
- Billyy SLAL Pack version 5.9 or later (paired struggle).

- Leito SLAL Pack version 1.6 (paired struggle).

 

The struggle animations from SLAL packs are probably look unconvincing. And their use is limited to a small number of situations for obvious reasons. You could play with queries on animation tab in mod's MCM menu to see them. And there is xls file in mod folder (./docs/UD_Anim_FromMods.xls) with list of all used animations and their mappings.

[greatwulf]

Thanks for the help. I got it working.

 

But for some unknown reason i now get the fatal error at making a new character aswell. Not sure what to do here. I've tried to filter it and attached the whole log aswell.

 

Spoiler

[03/30/2023 - 02:07:30AM] Cannot open store for class "fnissmquestscript", missing file?
[03/30/2023 - 02:07:30AM] Cannot open store for class "fnissmconfigmenu", missing file?
[03/30/2023 - 02:07:30AM] Cannot open store for class "thwtreasurehunterscript", missing file?
[03/30/2023 - 02:07:30AM] Cannot open store for class "thw_mcmconfig", missing file?
[03/30/2023 - 02:07:30AM] Cannot open store for class "thwplayeraliasbasescript", missing file?
[03/30/2023 - 02:07:30AM] Cannot open store for class "UD_Patch_Init", missing file?
[03/30/2023 - 02:07:30AM] ERROR: Unable to bind script UD_Patch_Init to US_Suits_Quest (2315D5E7) because their base types do not match

[03/30/2023 - 02:07:40AM] WARNING: Property UDOM on script udcustomdevicemain attached to UD_CustomDevice_Quest (2015E73C) cannot be initialized because the script no longer contains that property
[03/30/2023 - 02:07:40AM] Property UDRRM on object UD_PatchInit is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDRRM on object UD_API is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDPP on object UD_API is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDLLP on object UD_API is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDlibs on object UD_API is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDItem on object UD_API is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDCDmain on object US_Suits is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDCDmain on object us_libs is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDlibs on object us_libs is read-only, property skipped.

[03/30/2023 - 02:07:40AM] [UD,INFO,T=8.134001]: MCM Ready
[03/30/2023 - 02:07:40AM] [ud_mcm_script <UD_MCM (20112724)>] INITIALIZED

[03/30/2023 - 02:07:41AM] [ud_widgetbase <UD_DeviceCondWidget (2000F1E9)>] INITIALIZED
[03/30/2023 - 02:07:41AM] [ud_widgetbase <UD_DeviceMainWidget (20139EAC)>] INITIALIZED
[03/30/2023 - 02:07:41AM] [ud_widgetbase <UD_OrgasmWidget (201553CE)>] INITIALIZED
[03/30/2023 - 02:07:43AM] [ud_mcm_script <UD_MCM (20112724)>]: Registered Unforgiving Devices at MCM.

[03/30/2023 - 02:07:46AM] Property UDCDmain on object us_libs is read-only, property skipped.
[03/30/2023 - 02:07:46AM] Property UDlibs on object us_libs is read-only, property skipped.

[03/30/2023 - 02:08:09AM] [UD,INFO,T=35.036003]: !!FATAL ERROR!! = Error loading Unforgiving devices. One or more of the modules are not ready. Please contact developrs on LL or GitHub
[03/30/2023 - 02:08:09AM] [UD,INFO,T=35.070004]: UDlibs=TRUE
[03/30/2023 - 02:08:09AM] [UD,INFO,T=35.104000]: UDCDmain=TRUE
[03/30/2023 - 02:08:09AM] [UD,INFO,T=35.138000]: config=TRUE
[03/30/2023 - 02:08:09AM] [UD,INFO,T=35.172001]: ItemManager=TRUE
[03/30/2023 - 02:08:09AM] [UD,INFO,T=35.206001]: UDLLP=False
[03/30/2023 - 02:08:09AM] [UD,INFO,T=35.240002]: UDOM=TRUE
[03/30/2023 - 02:08:19AM] [UD,INFO,T=45.167004]: UD_LeveledList_Patcher - Forms added to LeveledLists: 11

 

Papyrus.0.log

[ihatemykite]

5 hours ago, greatwulf said:

Thanks for the help. I got it working.

 

But for some unknown reason i now get the fatal error at making a new character aswell. Not sure what to do here. I've tried to filter it and attached the whole log aswell.

 

  Reveal hidden contents

[03/30/2023 - 02:07:30AM] Cannot open store for class "fnissmquestscript", missing file?
[03/30/2023 - 02:07:30AM] Cannot open store for class "fnissmconfigmenu", missing file?
[03/30/2023 - 02:07:30AM] Cannot open store for class "thwtreasurehunterscript", missing file?
[03/30/2023 - 02:07:30AM] Cannot open store for class "thw_mcmconfig", missing file?
[03/30/2023 - 02:07:30AM] Cannot open store for class "thwplayeraliasbasescript", missing file?
[03/30/2023 - 02:07:30AM] Cannot open store for class "UD_Patch_Init", missing file?
[03/30/2023 - 02:07:30AM] ERROR: Unable to bind script UD_Patch_Init to US_Suits_Quest (2315D5E7) because their base types do not match

[03/30/2023 - 02:07:40AM] WARNING: Property UDOM on script udcustomdevicemain attached to UD_CustomDevice_Quest (2015E73C) cannot be initialized because the script no longer contains that property
[03/30/2023 - 02:07:40AM] Property UDRRM on object UD_PatchInit is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDRRM on object UD_API is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDPP on object UD_API is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDLLP on object UD_API is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDlibs on object UD_API is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDItem on object UD_API is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDCDmain on object US_Suits is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDCDmain on object us_libs is read-only, property skipped.
[03/30/2023 - 02:07:40AM] Property UDlibs on object us_libs is read-only, property skipped.

[03/30/2023 - 02:07:40AM] [UD,INFO,T=8.134001]: MCM Ready
[03/30/2023 - 02:07:40AM] [ud_mcm_script <UD_MCM (20112724)>] INITIALIZED

[03/30/2023 - 02:07:41AM] [ud_widgetbase <UD_DeviceCondWidget (2000F1E9)>] INITIALIZED
[03/30/2023 - 02:07:41AM] [ud_widgetbase <UD_DeviceMainWidget (20139EAC)>] INITIALIZED
[03/30/2023 - 02:07:41AM] [ud_widgetbase <UD_OrgasmWidget (201553CE)>] INITIALIZED
[03/30/2023 - 02:07:43AM] [ud_mcm_script <UD_MCM (20112724)>]: Registered Unforgiving Devices at MCM.

[03/30/2023 - 02:07:46AM] Property UDCDmain on object us_libs is read-only, property skipped.
[03/30/2023 - 02:07:46AM] Property UDlibs on object us_libs is read-only, property skipped.

[03/30/2023 - 02:08:09AM] [UD,INFO,T=35.036003]: !!FATAL ERROR!! = Error loading Unforgiving devices. One or more of the modules are not ready. Please contact developrs on LL or GitHub
[03/30/2023 - 02:08:09AM] [UD,INFO,T=35.070004]: UDlibs=TRUE
[03/30/2023 - 02:08:09AM] [UD,INFO,T=35.104000]: UDCDmain=TRUE
[03/30/2023 - 02:08:09AM] [UD,INFO,T=35.138000]: config=TRUE
[03/30/2023 - 02:08:09AM] [UD,INFO,T=35.172001]: ItemManager=TRUE
[03/30/2023 - 02:08:09AM] [UD,INFO,T=35.206001]: UDLLP=False
[03/30/2023 - 02:08:09AM] [UD,INFO,T=35.240002]: UDOM=TRUE
[03/30/2023 - 02:08:19AM] [UD,INFO,T=45.167004]: UD_LeveledList_Patcher - Forms added to LeveledLists: 11

 

Papyrus.0.log 51.5 kB · 0 downloads

The not working UDLLP is using normal wait function, so its blocking if menu is open. So my guess is that you immediately opened some menu after starting the game, which caused the module to not initialize. I will replace it with waitmenumode so it will work also if menu is not open. Test NB once I merge the changes.

[Guest]

Not sure if I am missing somethig, but after starting a new game (DD5.2, UD most recent nightly build) I keep getting "DCL patch has to be loaded after main mod", even if the DCL patch is indeed loaded after the main mod in my load order.

 

EDIT: Does not happend with 2.1b1 (downloaded from github)

Edited March 30, 2023 by RandomPufferFish

[greatwulf]

10 hours ago, ihatemykite said:

The not working UDLLP is using normal wait function, so its blocking if menu is open. So my guess is that you immediately opened some menu after starting the game, which caused the module to not initialize. I will replace it with waitmenumode so it will work also if menu is not open. Test NB once I merge the changes.

 

The only thing that opens after i start a new game is Racemenu ( i use it with Live another Life for quickstarting) because i always used it for starting a new game and UD always worked with it fine so far. I get the fatal error after like ~10 seconds in Racemenu. I'll try the new NB out and see if it fixes it.

Edited March 30, 2023 by greatwulf

[greatwulf]

Ok, no fatal error anymore with NB Release @ 20230330. I dont know if it was Racemenu or something else in the background at fault cuz i barely have anything installed (switched from Skyrim LE to SE).

[The Longest John]

Have a significant issue to report.

 

I tried installing the latest NB (@ 20230330), and am getting a fomod validation error.

 

I am trying to install via Vortex (I know, I know, MO2 is better and all that), but am unable to do so. The error pane is spitting out the below-copied text:

 

"

 

Invalid XML: The element 'dependencyType' has invalid child element 'type'. List of possible elements expected: 'defaultType'. (Line 53, Pos 38)
The element 'dependencyType' has invalid child element 'type'. List of possible elements expected: 'defaultType'. (Line 85, Pos 38)
The element 'dependencyType' has invalid child element 'type'. List of possible elements expected: 'defaultType'. (Line 117, Pos 38)
The element 'dependencyType' has invalid child element 'type'. List of possible elements expected: 'defaultType'. (Line 162, Pos 38)
The element 'dependencyType' has invalid child element 'type'. List of possible elements expected: 'defaultType'. (Line 194, Pos 38)
The element 'dependencyType' has invalid child element 'type'. List of possible elements expected: 'defaultType'. (Line 226, Pos 38)

 

"

 

I am not sure if there is something wrong being done on my end. Thought I'd bring it up in case anybody else is experiencing the same issue.

[ihatemykite]

11 hours ago, RandomPufferFish said:

Not sure if I am missing somethig, but after starting a new game (DD5.2, UD most recent nightly build) I keep getting "DCL patch has to be loaded after main mod", even if the DCL patch is indeed loaded after the main mod in my load order.

 

EDIT: Does not happend with 2.1b1 (downloaded from github)

That is because the check was not implemented in that version. 2.1b1 is veeery old version. Try to do following things (assuming you are using MO2). It is important that the patch have to be loaded both after the UD and after patched mod (DCL in this case). Also try to run the LOOT. It should correctly order all patches. You can do it by clicking this button if you use MO2

 

Spoiler

 

26 minutes ago, greatwulf said:

Ok, no fatal error anymore with NB Release @ 20230330. I dont know if it was Racemenu or something else in the background at fault cuz i barely have anything installed (switched from Skyrim LE to SE).

That issue is not relevant to Racemenu itself. It was relevant to menus (cause RaceMENU). Before, the UD was loading all the time. Even if user have opened any menu (inventory, options etc...) immediately after starting game. Then in my attempt at increasing performance I remade it, so it can only load if a menu is no open. So if you for example open MCM right after starting the game, the mod will stop loading (well, not fully, only the part which reports error). After the reports with mod not loading correctly, I tried to reverse it back, but forget about one part, which was causing again the issue you reported. It should no longer cause an issue (hopefully) and the combination of mods you have should have no effect on it. It is really dependent on user actions after starting the game.

[ihatemykite]

12 minutes ago, The Longest John said:

Have a significant issue to report.

 

I tried installing the latest NB (@ 20230330), and am getting a fomod validation error.

 

I am trying to install via Vortex (I know, I know, MO2 is better and all that), but am unable to do so. The error pane is spitting out the below-copied text:

 

"

 

Invalid XML: The element 'dependencyType' has invalid child element 'type'. List of possible elements expected: 'defaultType'. (Line 53, Pos 38)
The element 'dependencyType' has invalid child element 'type'. List of possible elements expected: 'defaultType'. (Line 85, Pos 38)
The element 'dependencyType' has invalid child element 'type'. List of possible elements expected: 'defaultType'. (Line 117, Pos 38)
The element 'dependencyType' has invalid child element 'type'. List of possible elements expected: 'defaultType'. (Line 162, Pos 38)
The element 'dependencyType' has invalid child element 'type'. List of possible elements expected: 'defaultType'. (Line 194, Pos 38)
The element 'dependencyType' has invalid child element 'type'. List of possible elements expected: 'defaultType'. (Line 226, Pos 38)

 

"

 

I am not sure if there is something wrong being done on my end. Thought I'd bring it up in case anybody else is experiencing the same issue.

Lets say I tried update the fomod xml config without tool. And this is the result. Strangely, I use the MO2, and don't have said issue. Or well, better said, it shows same errors but works anyway. Perhaps the MO2 is more ignorant and just prints the errors and calls it a day without doing anything. I will give it a look and try to fix it.

 

EDIT: Found the issue. Fixed the fomod and manually started NB. Test it once it finish

Edited March 30, 2023 by ihatemykite

[Guest]

1 hour ago, ihatemykite said:

That is because the check was not implemented in that version. 2.1b1 is veeery old version. Try to do following things (assuming you are using MO2). It is important that the patch have to be loaded both after the UD and after patched mod (DCL in this case).

 

Attached the load order, it seems to be correct, right?

 

> Also try to run the LOOT. It should correctly order all patches. You can do it by clicking this button if you use MO2

I tend to avoid running loot, it gave me issues in the past, so if I can I try to create a load order myself. In any case, running loot does not seem to change the load order of DCL, UD and related patches unfortunately

 

> That is because the check was not implemented in that version. 2.1b1 is veeery old version.

Huh, I searched in the source code and saw the same function that I believe is used in the NB, my bad!

[ihatemykite]

8 hours ago, RandomPufferFish said:

Attached the load order, it seems to be correct, right?

 

> Also try to run the LOOT. It should correctly order all patches. You can do it by clicking this button if you use MO2

I tend to avoid running loot, it gave me issues in the past, so if I can I try to create a load order myself. In any case, running loot does not seem to change the load order of DCL, UD and related patches unfortunately

 

> That is because the check was not implemented in that version. 2.1b1 is veeery old version.

Huh, I searched in the source code and saw the same function that I believe is used in the NB, my bad!

Yeah, Im stupid. I somehow confused 2.0b1 with 2.1b1... Sorry about that. You are correct, the check should be present in the version you use. I tried to replicate the bug by installing DCL again with patch, but didn't get the error. Do you use clean save or existing save ?

[Guest]

1 hour ago, ihatemykite said:

Yeah, Im stupid. I somehow confused 2.0b1 with 2.1b1... Sorry about that. You are correct, the check should be present in the version you use. I tried to replicate the bug by installing DCL again with patch, but didn't get the error. Do you use clean save or existing save ?

Clean save, yes. I started a new game multiple times, it happens consistently

 

I don't have a papyrus log atm, but I can try to provide one later if it can help

 

Edit: decided I could spare 10 mins and loaded the game with logging. I do not see any error related to UD (I filtered the log by UD,INFO). Let me know if I can help!

Edited March 31, 2023 by RandomPufferFish

[ihatemykite]

21 minutes ago, RandomPufferFish said:

Clean save, yes. I started a new game multiple times, it happens consistently

 

I don't have a papyrus log atm, but I can try to provide one later if it can help

 

Edit: decided I could spare 10 mins and loaded the game with logging. I do not see any error related to UD (I filtered the log by UD,INFO). Let me know if I can help!

Found the issue! Issue was not in the UD itself, but in the patch. I wrongly named one property, so it was actually not checking load order of patch, but of DCL itself. Try to move the DCL after UD, and it should work. I have fixed it and will merge it shortly. NB should be available a short time after.

[greatwulf]

NB @ 20230401: THW Patch.esp wants the DeviouslyPink.esp as Master. Don't know about anything else since THW is the only optional mod i have active atm with UD.

[ihatemykite]

11 hours ago, greatwulf said:

NB @ 20230401: THW Patch.esp wants the DeviouslyPink.esp as Master. Don't know about anything else since THW is the only optional mod i have active atm with UD.

Forget to clean the masters after adding the patch script from Devious Pink. Will fix shortly.

[Mamango]

So i can have widget icons only in SE since iwantwidget is for it?

[kurotatsu]

1 hour ago, Mamango said:

So i can have widget icons only in SE since iwantwidget is for it?

iwantwidget has version for LE too, I use it.

[Nova4]

Hello I'm loving this update, but not sure if it is only me but the khajiit rope blindfold doesn't work properly: it doesn't show in my character.

[dirtybrains]

First off, great mod!

 

As I haven't seen this reported yet, I figured I would bring it up in case anyone else is seeing the same?

 

I've seen a bug here with trying to remove certain devices (there's one I can get it to reproduce on pretty reliably here), which is the red ebonite armbinder... it just unequips and re-equips with no dialog.  Then eventually it gives an error saying:

 

[UD, !ERROR!, T-504.237030]: getDeviceScriptByRender timeout for [Armor < (190110F1)>]

[UD, !ERROR!, T-510.862030]: getDeviceScriptByRender timeout for [Armor < (190110F1)>]

 

This is on SE with just DD 5.2 and DCL 9.0 installed, although I have seen this with just DD 5.2 installed as well.

 

Not all devices do this though, so like the black ebonite armbinder works fine, for instance.

Edited April 7, 2023 by dirtybrains

[ihatemykite]

On 4/6/2023 at 10:32 AM, Nova4 said:

Hello I'm loving this update, but not sure if it is only me but the khajiit rope blindfold doesn't work properly: it doesn't show in my character.

Do you use SE or LE. Do you use correct patch ? (BRRF or BRRF + For Him)

6 hours ago, dirtybrains said:

First off, great mod!

 

As I haven't seen this reported yet, I figured I would bring it up in case anyone else is seeing the same?

 

I've seen a bug here with trying to remove certain devices (there's one I can get it to reproduce on pretty reliably here), which is the red ebonite armbinder... it just unequips and re-equips with no dialog.  Then eventually it gives an error saying:

 

[UD, !ERROR!, T-504.237030]: getDeviceScriptByRender timeout for [Armor < (190110F1)>]

[UD, !ERROR!, T-510.862030]: getDeviceScriptByRender timeout for [Armor < (190110F1)>]

 

This is on SE with just DD 5.2 and DCL 9.0 installed, although I have seen this with just DD 5.2 installed as well.

 

Not all devices do this though, so like the black ebonite armbinder works fine, for instance.

Most likely caused by Devious Devices SE patch.esp. Check if the SE patch is loaded before UD patch.