[AAF] Sex Attributes - Framework (6/26/2024)

[sinsemilla]

I love the new morph functions! Is there any way that we could ever get this to work with NPC/followers too? Its asking for alot but its such a shame when it works so good for the player xD Great job anyways!

[Nivea]

Anyway to add Cumflation to males? I am messing around with my own sliders and would love to know if that can happen?

[Church the Cat]

On 4/12/2022 at 7:26 PM, sinsemilla said:

I love the new morph functions! Is there any way that we could ever get this to work with NPC/followers too? Its asking for alot but its such a shame when it works so good for the player xD Great job anyways!

I second this, as well as having companions endure the wear and tear debuffs. Would make this mod perfect to see Piper, Cait and Curie "Cumflated" and reduced to a slow walk the same as the player, aftereffects of enduring a Super Mutant gangbang or being used as a sex toy by a Behemoth. ?

[nousernamethanks]

Any chance of an MCM option to disable willpower from being spendable on hacking & vanilla/non-sexual lockpicking? I find it severely breaks game balance and also goes outside the function of a framework/library like this. Maybe willpower hacking/picking could be broken out into a separate mod? Thanks for your work on this btw, this mod adds so much valuable thematic consistency between all the sexual mods.

[FO4Life]

On 4/9/2022 at 10:33 PM, Azroq said:

Yeah Found out whats the Problem
Its Sanity Framework

With Attributes 2.5.1 its loaded below it in the LO

But Attributes 2.5.2 is Loaded Below Sanity Framework and Breaks the Use/Registry somehow Total Strange

 

So Yeah its just a Stupid Load Order about one Position away from working or Not and for that i Bang my Head for 2 Days

Well Still Thanks for the Help and

Great Work with the Mod twisted  cant wait for More Updates and Content

Thank you very much! I was playing v2.5.2 with Sanity Framework positioned below AAF Sex Attributes Framework (and Sexual Harassment) and to begin with it seemed to be working fine. Then yesterday, I started to get problems (could not display SA stats from either keybind or from mod options window), and then today saw new version(s), downloaded and installed, placing v2.5.3 in the same position as v2.5.2. Then had same inability to display stats AND got the error message concerning Sexual Harassment not being installed correctly. Found your post, changed load order, reinstalled SA v2.5.3 (and SH v1.14.0) BUT ALSO changed esm/esp orders on MO2 right panel so that they were also higher priority than Sanity Framework. And now everything works as intended! Thanks again!

 

EDIT: I PM'ed SthanDust [Sanity Framework author] for heads up as his Nexus page shows different load order requirements, with SF being placed below AAF SA and SH.

Edited April 23, 2022 by FO4Life

[twistedtrebla]

10 hours ago, nousernamethanks said:

Any chance of an MCM option to disable willpower from being spendable on hacking & vanilla/non-sexual lockpicking? I find it severely breaks game balance and also goes outside the function of a framework/library like this. Maybe willpower hacking/picking could be broken out into a separate mod? Thanks for your work on this btw, this mod adds so much valuable thematic consistency between all the sexual mods.

There already is an MCM setting to disable that

[kazeha9]

i have hudframework do i need your mod ? and what your mod do with it ,some screenshot? 

[vaultbait]

35 minutes ago, kazeha9 said:

i have hudframework do i need your mod ? and what your mod do with it ,some screenshot? 

 

HUD Framework and Sex Attributes Framework are different mods which do completely different things. It's like you just said "I have milk, do I need bread?"

 

Whether you need Sex Attributes Framework depends on if you want to use some other mod which relies on it.

[Spaceguest991]

So playing around with Version 2.5.4 with the new arousal I'm not sure if it's intended for the mod or just a issue I'm having. but I noticed that when my extremely submissive character had a shock collar or real handcuffs on or any other DD equipped and got to the brink of orgasm stage, the brink of orgasm would stay and wouldn't go back down to a lower level of arousal as long as any Devious Devices or shock collars real handcuffs was equipped instead of just DD plugs. Since the brink of orgasm stage would stay even if I took off the plugs but other devices like a shock collar stayed on. But having DD equipped that are not plugs or nipple piercings doesn't cause my character to get a brink of orgasm state

 

And I had a small suggestion for the new arousal that perhaps if the player is a slut or even if they're not and had a chastity belt on arousal keeps building stays from sex acts or sexual harassment harasser molesting the player keeps building until about 89 or so,  with the idea that player can get to the point where nearly anything get them to the brink of orgasm from being in denial.

Edited April 24, 2022 by Spaceguest991

[Sthan Dust]

On 4/23/2022 at 7:05 AM, FO4Life said:

Thank you very much! I was playing v2.5.2 with Sanity Framework positioned below AAF Sex Attributes Framework (and Sexual Harassment) and to begin with it seemed to be working fine. Then yesterday, I started to get problems (could not display SA stats from either keybind or from mod options window), and then today saw new version(s), downloaded and installed, placing v2.5.3 in the same position as v2.5.2. Then had same inability to display stats AND got the error message concerning Sexual Harassment not being installed correctly. Found your post, changed load order, reinstalled SA v2.5.3 (and SH v1.14.0) BUT ALSO changed esm/esp orders on MO2 right panel so that they were also higher priority than Sanity Framework. And now everything works as intended! Thanks again!

 

EDIT: I PM'ed SthanDust [Sanity Framework author] for heads up as his Nexus page shows different load order requirements, with SF being placed below AAF SA and SH.

Hello!  I will check this out.  Not sure why it would conflict since its not a hard requirement.  I just called the variables via script.  So sorry it caused issues!  I'll load the new version of SA today and see if I get the same issue. ❤️

 

[FO4Life]

9 hours ago, Sthan Dust said:

Hello!  I will check this out.  Not sure why it would conflict since its not a hard requirement.  I just called the variables via script.  So sorry it caused issues!  I'll load the new version of SA today and see if I get the same issue. ❤️

 

Hey Sthan Dust, I hope that all goes well... but wait, I did a fresh install just now, and I am having the same issue with SH being displayed as not being installed with Sanity Framework in the same load order in the info I provided you; so something else seems to be happening, and when I was messing [attempting to isolate the problem and find a solution!] with the AAF mods the other day, I am now guessing that changing Sanity Framework load order in parallel with re-installing SH did not necessarily imply that Sanity Framework is "at fault"... I will try a little testing now, changing one thing at a time, to see if I can localize the issue. Thanks!

 

EDIT: I re-installed SH, no change. I thunked about it... I tested SA in game and found again that I could not display variables from either keybind or directly from MCM Debug option so I am now guessing that the problem is related to SA [and not SH]. I ran AAF_GFV,  no issues. I re-installed AAF Sex Attributes Framework, no change. I re-installed AAF 1.66 beta, no change. It seems that somehow AAF Sex Attributes Framework gets stuck [somehow]. I may search this forum again... which I did and found some other players have seen "similar" issues but I do not think the problem(s) is fully understood.

 

EDIT2... for clarity; BOTH AAF 1.66 beta and AAF Sexual Attributes are installed and AAF SA stat adjustments are displayed in STATS/STATUS with Q) Show Effects, and AAF animations are working fine. HOWEVER, I get a AAF Sexual Harassment warning when something triggers in AAF SH [like the wonderful new SLAP ASS] which states that there is a problem with either AAF SAF or AAF 1.66 beta. As far as I can see/tell, the only feature from AAF SA that it not working is the display stats option [either via keybind or via MCM Debug option]... this makes me think that the issue is linked to the stats part, which is causing AAF SH to show warnings (maybe because it cannot update the stats?). Some coordinated effort would be appreciated.

 

Further note: I first detected this issue some days ago, when starting a new playthrough/fresh install using AAF SA v2.5.2; the problem persists in a second fresh install using SA v2.5.3. I initially was swayed to believe it could be an incompatibility with AAF Sanity Framework as that was the only AAF mod new to my game. I somehow fixed the issue when using v2.5.2 by re-installing mods and swapping load orders (with a focus on Sanity Framework due to a prior post on this forum). I am now not so sure that Sanity Framework is/was to blame; but to be perfectly honest, I am lost at sea.

 

Additional Info... I drank some coffee and launched FO4Edit and checked my entire mod list for conflicts. The only AAF mod to show any conflicts was Sanity Framework and these few were Worldspace conflicts with either the some of the 6 original Masters (game+DLCs) or the Unofficial Patch (latest) or with PRP (v0.59.4). I hesitantly add that a few minor conflicts were found to exist in Real Handcuffs (v0.4.12) but I cannot believe these cause any issues.

Edited April 25, 2022 by FO4Life

[twistedtrebla]

10 hours ago, Spaceguest991 said:

So playing around with Version 2.5.4 with the new arousal I'm not sure if it's intended for the mod or just a issue I'm having. but I noticed that when my extremely submissive character had a shock collar or real handcuffs on or any other DD equipped and got to the brink of orgasm stage, the brink of orgasm would stay and wouldn't go back down to a lower level of arousal as long as any Devious Devices or shock collars real handcuffs was equipped instead of just DD plugs. Since the brink of orgasm stage would stay even if I took off the plugs but other devices like a shock collar stayed on. But having DD equipped that are not plugs or nipple piercings doesn't cause my character to get a brink of orgasm state

 

And I had a small suggestion for the new arousal that perhaps if the player is a slut or even if they're not and had a chastity belt on arousal keeps building stays from sex acts or sexual harassment harasser molesting the player keeps building until about 89 or so,  with the idea that player can get to the point where nearly anything get them to the brink of orgasm from being in denial.

Yea thats a known bug. Wearing any restraints (DD or RH) as a submissive can help prevent arousal from going down. The intention is that non-plug restraints will only increase arousal up until 60. Anything beyond 60 requires physical stimulation to the genetals. 

 

For now, if you set the "arousal gained from DD" setting to 0, then this will resolve the bug. But of course it means you wont get the increase to 60 either.

[FO4Life]

I'm going to recap: problem with AAF Sexual Harassment [v1.14.0] due to either an incorrect installation of AAF [v1.66 beta] or AAF Sex Attributes Framework [v2.5.3]

Reminder: had same warning when using SA v2.5.2 and SH v1.11.5.

 

I have no conflicts in any AAF mods (validated by AAF_GFV and FO4Edit).

 

3 screenshots below showing [1] AAF SH warning, [2] AAF SA stat effects in Pipboy, and [3] AAF warnings (mainly lack of creature support; I have no idea why).

 

The only "problem" I encounter with AAF SA is the inability to "Show Sex Attributes" either by the MCM keybind or the MCM Debug option.

 

PLEASE NOTE that I did uncheck AAF Sexual Harassment in MO2, launched the game, saved a NEW game, exited, re-checked SH then relaunched game, and still received same warning as per first image.

 

I understand that the warning is associated with SH and not [directly] SA but intuition makes me think that the issue is linked to SA. Any suggestions would be very much appreciated!

 

EDIT: something I didn't think of... I did a fresh install yesterday BUT I am using existing saves. Would this [not being a new game] be a possible cause? Even if the playthrough saves were initiated with both AAF SA and SH installed?

 

EDIT Further Testing: uninstalled AAF SA, AAF SH and Sanity Framework and launched game. Created New Save, changed location and did stuff. Re-installed AAF SA v2.5.3 but still no ability to Show Sex Attributes and now STAT/STATUS/SHOW EFFECTS only displays Sex Reputation. Mmm... decided to wear a collar [purely for test purposes!] but no change in self-esteem. Will download v2.5.4 and see I can get that to work.

 

EDIT Further results: re-installed AAF Sexual Harassment v1.14.0 and started NEW Game... same AAF SH warning (either/both AAF SA and/or AAF not properly installed). I did not get prompt from AAF SA to define dom/sub start. I will try and re-install F4SE and dependencies + every single AAF mod and retry.

 

Edited April 25, 2022 by FO4Life

[nousernamethanks]

On 4/24/2022 at 5:06 AM, twistedtrebla said:

There already is an MCM setting to disable that

Ah, I thought I'd gone through all the menus first but I hadn't! Sorry for taking your time with the dumb question, thanks again for your work

[FO4Life]

2 hours ago, nousernamethanks said:

Ah, I thought I'd gone through all the menus first but I hadn't! Sorry for taking your time with the dumb question, thanks again for your work

The more problems you encounter, the more you research stuff, the more you learn... and then, just when you start getting comfortable, something else happens. I had a similar thing last year, though I knew the option existed somewhere, but I just couldn't see it anywhere in the MCM options; it drove me crazy. It took me a few days to finally find it... it's like not being able to see the woods from the trees.

[Spaceguest991]

9 hours ago, twistedtrebla said:

Yea thats a known bug. Wearing any restraints (DD or RH) as a submissive can help prevent arousal from going down. The intention is that non-plug restraints will only increase arousal up until 60. Anything beyond 60 requires physical stimulation to the genetals. 

 

For now, if you set the "arousal gained from DD" setting to 0, then this will resolve the bug. But of course it means you wont get the increase to 60 either.

Mmhm, Thanks for the reply. Looks like the easiest thing to for me then is to just turn arousal gain from DD on and off depending on whats going on.

[cmdrtomalak]

12 hours ago, FO4Life said:

I'm going to recap: problem with AAF Sexual Harassment [v1.14.0] due to either an incorrect installation of AAF [v1.66 beta] or AAF Sex Attributes Framework [v2.5.3]

Reminder: had same warning when using SA v2.5.2 and SH v1.11.5.

 

I have no conflicts in any AAF mods (validated by AAF_GFV and FO4Edit).

 

3 screenshots below showing [1] AAF SH warning, [2] AAF SA stat effects in Pipboy, and [3] AAF warnings (mainly lack of creature support; I have no idea why).

 

The only "problem" I encounter with AAF SA is the inability to "Show Sex Attributes" either by the MCM keybind or the MCM Debug option.

 

PLEASE NOTE that I did uncheck AAF Sexual Harassment in MO2, launched the game, saved a NEW game, exited, re-checked SH then relaunched game, and still received same warning as per first image.

 

I understand that the warning is associated with SH and not [directly] SA but intuition makes me think that the issue is linked to SA. Any suggestions would be very much appreciated!

 

EDIT: something I didn't think of... I did a fresh install yesterday BUT I am using existing saves. Would this [not being a new game] be a possible cause? Even if the playthrough saves were initiated with both AAF SA and SH installed?

 

EDIT Further Testing: uninstalled AAF SA, AAF SH and Sanity Framework and launched game. Created New Save, changed location and did stuff. Re-installed AAF SA v2.5.3 but still no ability to Show Sex Attributes and now STAT/STATUS/SHOW EFFECTS only displays Sex Reputation. Mmm... decided to wear a collar [purely for test purposes!] but no change in self-esteem. Will download v2.5.4 and see I can get that to work.

 

EDIT Further results: re-installed AAF Sexual Harassment v1.14.0 and started NEW Game... same AAF SH warning (either/both AAF SA and/or AAF not properly installed). I did not get prompt from AAF SA to define dom/sub start. I will try and re-install F4SE and dependencies + every single AAF mod and retry.

 

I'm facing with your exact problem and still can't figured it out.
I updated for SA 2.5.1 to 2.5.3 and in another attempt to 2.5.4 and still had the same problem. In an existing save (were both SA an SH were functioning without problem for the last 20 hours of gameplay) and also have the same problem with a complete new game. In that case, the prompt that ask you for your dom / sub condition isn't trigger.

The only difference i've spotted is that my mod list doesn't have the Sanity Framework installed. So I can rule that out.

I'm not with my game computer right now, but... do you try to uninstall the SA HUD from the MCM? I didn't make the test to uninstall with my working version of SA (2.5.1), but with the 2.5.3 and 2.5.4 the "Uninstall" option in the MCM menu doesn't don anything. Neither try a new game without the SA HUD.

Another thing that caught my attention is that with the new versions I can't execute function from the console. Following the example from this post

 With the version 2.5.1 the command execute correcty, but with 2.5.3 o 2.5.4 I get the error that the function is not registered. It's appears that the FPA_Main Quest is active but not any of its functions.

[twistedtrebla]

Make sure you're not combining the newer version with patches for any older versions, such as sanity framework or gender neutral dialogue.

 

That's going to cause a bunch of issues. Patches are made for a specific version and will only work for that version.

 

As such, use patches at your own risk. I don't create patches so it's out of my control if a certain patch breaks things 

Edited April 25, 2022 by twistedtrebla

[Sthan Dust]

16 hours ago, FO4Life said:

Hey Sthan Dust, I hope that all goes well... but wait, I did a fresh install just now, and I am having the same issue with SH being displayed as not being installed with Sanity Framework in the same load order in the info I provided you; so something else seems to be happening, and when I was messing [attempting to isolate the problem and find a solution!] with the AAF mods the other day, I am now guessing that changing Sanity Framework load order in parallel with re-installing SH did not necessarily imply that Sanity Framework is "at fault"... I will try a little testing now, changing one thing at a time, to see if I can localize the issue. Thanks!

 

EDIT: I re-installed SH, no change. I thunked about it... I tested SA in game and found again that I could not display variables from either keybind or directly from MCM Debug option so I am now guessing that the problem is related to SA [and not SH]. I ran AAF_GFV,  no issues. I re-installed AAF Sex Attributes Framework, no change. I re-installed AAF 1.66 beta, no change. It seems that somehow AAF Sex Attributes Framework gets stuck [somehow]. I may search this forum again... which I did and found some other players have seen "similar" issues but I do not think the problem(s) is fully understood.

 

EDIT2... for clarity; BOTH AAF 1.66 beta and AAF Sexual Attributes are installed and AAF SA stat adjustments are displayed in STATS/STATUS with Q) Show Effects, and AAF animations are working fine. HOWEVER, I get a AAF Sexual Harassment warning when something triggers in AAF SH [like the wonderful new SLAP ASS] which states that there is a problem with either AAF SAF or AAF 1.66 beta. As far as I can see/tell, the only feature from AAF SA that it not working is the display stats option [either via keybind or via MCM Debug option]... this makes me think that the issue is linked to the stats part, which is causing AAF SH to show warnings (maybe because it cannot update the stats?). Some coordinated effort would be appreciated.

 

Further note: I first detected this issue some days ago, when starting a new playthrough/fresh install using AAF SA v2.5.2; the problem persists in a second fresh install using SA v2.5.3. I initially was swayed to believe it could be an incompatibility with AAF Sanity Framework as that was the only AAF mod new to my game. I somehow fixed the issue when using v2.5.2 by re-installing mods and swapping load orders (with a focus on Sanity Framework due to a prior post on this forum). I am now not so sure that Sanity Framework is/was to blame; but to be perfectly honest, I am lost at sea.

 

Additional Info... I drank some coffee and launched FO4Edit and checked my entire mod list for conflicts. The only AAF mod to show any conflicts was Sanity Framework and these few were Worldspace conflicts with either the some of the 6 original Masters (game+DLCs) or the Unofficial Patch (latest) or with PRP (v0.59.4). I hesitantly add that a few minor conflicts were found to exist in Real Handcuffs (v0.4.12) but I cannot believe these cause any issues.

I apologise.  You can move Sanity Framework above Sex Attributes in the load order.  It also looks like one of the Forms I am calling has changes its FormID.  The only known conflicts I have are mods that edit the area around Rabbit Hole.  Also, I don't use an Keybinds for my MCM.  So that shouldn't be colliding with anything there.

 

I'll give it a look tonight and upload a cleaned ESP.  Let me know if changing load order addresses the issue.

 

I have Sex Attributes, Sexual Harassment loaded with no issues, so this is a bit perplexing because, if my mod doesn't get the values from Sex Attributes, it's just uses default values.

 

Thank you! ❤️

[Sthan Dust]

21 hours ago, FO4Life said:

Hey Sthan Dust, I hope that all goes well... but wait, I did a fresh install just now, and I am having the same issue with SH being displayed as not being installed with Sanity Framework in the same load order in the info I provided you; so something else seems to be happening, and when I was messing [attempting to isolate the problem and find a solution!] with the AAF mods the other day, I am now guessing that changing Sanity Framework load order in parallel with re-installing SH did not necessarily imply that Sanity Framework is "at fault"... I will try a little testing now, changing one thing at a time, to see if I can localize the issue. Thanks!

 

EDIT: I re-installed SH, no change. I thunked about it... I tested SA in game and found again that I could not display variables from either keybind or directly from MCM Debug option so I am now guessing that the problem is related to SA [and not SH]. I ran AAF_GFV,  no issues. I re-installed AAF Sex Attributes Framework, no change. I re-installed AAF 1.66 beta, no change. It seems that somehow AAF Sex Attributes Framework gets stuck [somehow]. I may search this forum again... which I did and found some other players have seen "similar" issues but I do not think the problem(s) is fully understood.

 

EDIT2... for clarity; BOTH AAF 1.66 beta and AAF Sexual Attributes are installed and AAF SA stat adjustments are displayed in STATS/STATUS with Q) Show Effects, and AAF animations are working fine. HOWEVER, I get a AAF Sexual Harassment warning when something triggers in AAF SH [like the wonderful new SLAP ASS] which states that there is a problem with either AAF SAF or AAF 1.66 beta. As far as I can see/tell, the only feature from AAF SA that it not working is the display stats option [either via keybind or via MCM Debug option]... this makes me think that the issue is linked to the stats part, which is causing AAF SH to show warnings (maybe because it cannot update the stats?). Some coordinated effort would be appreciated.

 

Further note: I first detected this issue some days ago, when starting a new playthrough/fresh install using AAF SA v2.5.2; the problem persists in a second fresh install using SA v2.5.3. I initially was swayed to believe it could be an incompatibility with AAF Sanity Framework as that was the only AAF mod new to my game. I somehow fixed the issue when using v2.5.2 by re-installing mods and swapping load orders (with a focus on Sanity Framework due to a prior post on this forum). I am now not so sure that Sanity Framework is/was to blame; but to be perfectly honest, I am lost at sea.

 

Additional Info... I drank some coffee and launched FO4Edit and checked my entire mod list for conflicts. The only AAF mod to show any conflicts was Sanity Framework and these few were Worldspace conflicts with either the some of the 6 original Masters (game+DLCs) or the Unofficial Patch (latest) or with PRP (v0.59.4). I hesitantly add that a few minor conflicts were found to exist in Real Handcuffs (v0.4.12) but I cannot believe these cause any issues.

Hello there 

I think I've found the error.  It seems I've not had anyone else have this issue, but I realized I inadvertently referenced the wrong form id, which would collide based on the load order.  The game is rather unforgiving.  However, I shall release a minor update tomorrow that should fix this.  

 

Thank you for your patience. ❤️

[DTESSurvivor]

Updated Sex attributes, added SAHud (Hud framework already installed), and no longer see my sex attributes via hotkey, hud never showed up.  Uninstalled hud-add-on and still could not get the attributes via hot key, even though re-assigned and re-assigned back.  Effects are still visible in pip-boy, but cannot bring up the attributes.

[twistedtrebla]

2.5.5

• Added a new experimental mode with arousal, called "dynamic stimulation mode".
  • Traditionally, arousal was processed at the end of the sex scene. But if this mode is enabled, player will slowly increase in arousal from the ongoing sex every second while the sex scene is playing.
  • If the player reaches 100 arousal during sex scene, they will climax, which will reset the arousal back to 0.
  • Player has about 15 sec of blissful period after orgasm where they won't gain any arousal. But after 15 sec the player is still in a sex scene, they will start getting arousal again
  • This means if you jump into a sex scene On the Brink of Orgasm, you'll probably orgasm within first few seconds of sex. And then start getting aroused again. If your arousal gain setting is high, it's possible you could orgasm more than once during one sex
• Fixed a bug where players were able to masturbate and lower arousal while chastity belt was on. Now, arousal will not decrease from masturbation if belt is worn.
• Fixed a bug where wearing non-plug devices would prevent player's arousal from subsiding down to 60.

[worik]

One question about a moaning sound effect and this mod with the 2.5.3 version:

 

When I did wear a DD plug, I got a repeating (and annoying) moaning sound effect. Until now, I couldn't see where it from and where I could toggle that off.

If it is part of this mod here, a toggle in the MCM would be very welcome

If not, ignore me, I'll keep searching the other mods support threads, too

[twistedtrebla]

21 minutes ago, worik said:

One question about a moaning sound effect and this mod with the 2.5.3 version:

 

When I did wear a DD plug, I got a repeating (and annoying) moaning sound effect. Until now, I couldn't see where it from and where I could toggle that off.

If it is part of this mod here, a toggle in the MCM would be very welcome

If not, ignore me, I'll keep searching the other mods support threads, too

 

Moan sound from wearing plugs is from Devious Devices. 

You can download latest devious devices RC8 that lets you customize how often the moan happens. It makes it more.. enjoyable, bc it doesnt happen every 20sec.

[worik]

3 hours ago, twistedtrebla said:

You can download latest devious devices RC8 that lets you customize how often the moan happens. It makes it more.. enjoyable, bc it doesnt happen every 20sec.

Thank you!

 

Edit: Note to myself and all others with the same issue:

Link to DD RC8 https://www.loverslab.com/topic/73925-devious-devices/page/137/#comment-3572600

 

Edited April 26, 2022 by worik