Unhealthy Craving

[vaultbait]

22 hours ago, Dersta said:

SUP F4SE AE 1.11.221 at Fallout 4 Nexus - Mods and community SUP has now been updated by lelslie. I have my game and mods updated, and the new SUP seems to work well with unhealthycraving.😍

 

Wow, I didn't expect it would happen. Thanks for letting us all know!!!

[rubber_duck]

Hi there again!

Posting here because this seems like the best place to ask for such support, I've been at this problem for days. Hopefully some of you may offer some more valuable insights...

 

I'm running CBBE-3BBB body. The body is not the problem, but I'm running into issues with additional morphing.

I'm using Rad Morphing Redux (RMR) and Unhealthy Craving (this one where I'm posting this; UC) as the one and only trigger. But, I also use Wasteland Eggspansion (WLEGG).

 

As the 'issue' (well, I prefer the term 'challenge') is not strictly UC-related, I'm writing it in the following spoiler (beware: it's somewhat long):

Spoiler

RMR + UC = morph the configured body sliders based on trigger (UC) value

WLEGG = also morphs configured body sliders, but based on internal mod stats

 

For example - using slider 'Belly':

RMR config (RadMorphingRedux.ini):

[Slider39]
sSliderName=Belly
iSex=1
fTargetMorph=200.000000
iTriggerNameIndex=0
sTriggerName=UnhealthyCraving
fThresholdMin=30.000000

→ from my understanding, that part of the config reads: Morph slider 'Belly' (sSliderName) on female characters (iSex=1) by 200% (fTargetMorph) when trigger 'UnhealthyCraving' (sTriggerName) reaches value of 30 (fThresholdMin). In other words: when UC trigger reaches value 30, morphing starts; and when UC trigger reaches maximum value (100), the slider 'Belly' will be morphed to its initial value + 200 (because that's what's configured).

 

 

 

WLEGG, on the other hand, works by the principle of internal mod stats (history tracking) and uses values from BodySlide XML (it parses the values from the specific XML). WLEGG actually has 2 values: temporary morphs (that increase and decrease during the pregnancy period), and permanent morphs (the ones that add up little by little over the count of total pregnancies; but limited by configuration). My 'problem' is related to those permanent morphs.

 

WLEGG XML (config) - but only for permanent morphs:

<SetSlider name="Belly" size="big" value="60"/>

 

I've also set the WLEGG pregnancies threshold to 30.

Meaning: when player has had 30 pregnancies in total (that threshold value), slider 'Belly' will have a value of 60 + initial value.

 

Now here's the problematic/questionable part: at maximum UC value of 100 (maximum weight; Morbidly Obese), the character's slider 'Belly' is morphed by +200. But, if that same character also had 30 WLEGG pregnancies that morph the same slider 'Belly' to 60 - what's the slider's final value: 200, 260 or 260 (RMR + WLEGG combined) + initial slider value (the value the character's body has been built with)?

 

I'm asking because I was confident that the answer is 260 + initial slider value: the two mods don't share any internal stats for tracking, but it's about how LooksMenu body morphs are coded.

 

The oddity happened with multiple sliders, but one slider stood out in particular.

To simplify the explanation, let's say it's slider 'MySlider' - configured in both RMR/UC + WLEGG:

• RMR + UC config: 80
  • ThresholdMin: 30 --> means that morphing starts at trigger value 30 and continues up until trigger reaches 100
• WLEGG: -500
  • Pregnancy count: 30 --> means that morphing will reach target value of -500 only when player reaches 30 total pregnancies

But it didn't work that way...

 

At the moment, my character has 35 total pregnancies. With the total counter set to 30, the character is morphed by WLEGG to the max. It all works well while UC trigger is < 30, because the moment UC trigger reaches value of 30, RMR morphing starts.

 

The problem is:

• At 35 WLEGG pregnancies, the character has reached maximum morphs by WLEGG. So the 'MySlider' is at -500 value. Because We have to take into the account the base MySlider value (+50), the slider's final value ends up at -450.
• However, because I just recently reached RMR/UC trigger value that's > 30, that seems to have overriden the slider: it seems as the slider is back at its default value (+50) and, at least that's what I think, will continue morphing until it reaches value 130 (50 base + 80 RMR config)
• Is this true? Or is it supposed to work by stacking, so the end value (visible on the character's body) is -370 (-450 from max WLEGG + 80 (maximum RMR when UC trigger = 100)?

It's a complex problem, but TL;DR:

• Do LooksMenu body morphs stack up to one another?
  • For example:
    • Base body slider: 50
    • Mod A: morphs slider +20
    • Mod B: morphs slider +5
    • Total end result: 50 + 20 + 5 = 75 --> character has this value on that body slider
• Or, does it work differently?
  • And if so - how exactly?

 

If you've made it this far - thanks! I sincerely hope someone with more knowledge finds this and is able to provide (correct) answers! If you have additional questions, don't hesitate to reach out - I'd like to have this '1-in-1000000' questions answered and the 'issue' solved!

 

Again - sorry for cluttering this mod's page, but this seemed like the best and most active/up-to-date place to ask. If you want me to remove this post from here, say the word and I'll move it elsewhere.

 

Really hoping someone with more info and knowledge has the time to answer! Thanks in advance!

 

Edited August 18 by rubber_duck
Typos, grammar

[vaultbait]

2 hours ago, rubber_duck said:

Hi there again!

Posting here because this seems like the best place to ask for such support, I've been at this problem for days. Hopefully some of you may offer some more valuable insights...

 

I'm running CBBE-3BBB body. The body is not the problem, but I'm running into issues with additional morphing.

I'm using Rad Morphing Redux (RMR) and Unhealthy Craving (this one where I'm posting this; UC) as the one and only trigger. But, I also use Wasteland Eggspansion (WLEGG).

 

As the 'issue' (well, I prefer the term 'challenge') is not strictly UC-related, I'm writing it in the following spoiler (beware: it's somewhat long):

  Hide contents

RMR + UC = morph the configured body sliders based on trigger (UC) value

WLEGG = also morphs configured body sliders, but based on internal mod stats

 

For example - using slider 'Belly':

RMR config (RadMorphingRedux.ini):

[Slider39]
sSliderName=Belly
iSex=1
fTargetMorph=200.000000
iTriggerNameIndex=0
sTriggerName=UnhealthyCraving
fThresholdMin=30.000000

→ from my understanding, that part of the config reads: Morph slider 'Belly' (sSliderName) on female characters (iSex=1) by 200% (fTargetMorph) when trigger 'UnhealthyCraving' (sTriggerName) reaches value of 30 (fThresholdMin). In other words: when UC trigger reaches value 30, morphing starts; and when UC trigger reaches maximum value (100), the slider 'Belly' will be morphed to its initial value + 200 (because that's what's configured).

 

 

 

WLEGG, on the other hand, works by the principle of internal mod stats (history tracking) and uses values from BodySlide XML (it parses the values from the specific XML). WLEGG actually has 2 values: temporary morphs (that increase and decrease during the pregnancy period), and permanent morphs (the ones that add up little by little over the count of total pregnancies; but limited by configuration). My 'problem' is related to those permanent morphs.

 

WLEGG XML (config) - but only for permanent morphs:

<SetSlider name="Belly" size="big" value="60"/>

 

I've also set the WLEGG pregnancies threshold to 30.

Meaning: when player has had 30 pregnancies in total (that threshold value), slider 'Belly' will have a value of 60 + initial value.

 

Now here's the problematic/questionable part: at maximum UC value of 100 (maximum weight; Morbidly Obese), the character's slider 'Belly' is morphed by +200. But, if that same character also had 30 WLEGG pregnancies that morph the same slider 'Belly' to 60 - what's the slider's final value: 200, 260 or 260 (RMR + WLEGG combined) + initial slider value (the value the character's body has been built with)?

 

I'm asking because I was confident that the answer is 260 + initial slider value: the two mods don't share any internal stats for tracking, but it's about how LooksMenu body morphs are coded.

 

The oddity happened with multiple sliders, but one slider stood out in particular.

To simplify the explanation, let's say it's slider 'MySlider' - configured in both RMR/UC + WLEGG:

• RMR + UC config: 80
  • ThresholdMin: 30 --> means that morphing starts at trigger value 30 and continues up until trigger reaches 100
• WLEGG: -500
  • Pregnancy count: 30 --> means that morphing will reach target value of -500 only when player reaches 30 total pregnancies

But it didn't work that way...

 

At the moment, my character has 35 total pregnancies. With the total counter set to 30, the character is morphed by WLEGG to the max. It all works well while UC trigger is < 30, because the moment UC trigger reaches value of 30, RMR morphing starts.

 

The problem is:

• At 35 WLEGG pregnancies, the character has reached maximum morphs by WLEGG. So the 'MySlider' is at -500 value. Because We have to take into the account the base MySlider value (+50), the slider's final value ends up at -450.
• However, because I just recently reached RMR/UC trigger value that's > 30, that seems to have overriden the slider: it seems as the slider is back at its default value (+50) and, at least that's what I think, will continue morphing until it reaches value 130 (50 base + 80 RMR config)
• Is this true? Or is it supposed to work by stacking, so the end value (visible on the character's body) is -370 (-450 from max WLEGG + 80 (maximum RMR when UC trigger = 100)?

It's a complex problem, but TL;DR:

• Do LooksMenu body morphs stack up to one another?
  • For example:
    • Base body slider: 50
    • Mod A: morphs slider +20
    • Mod B: morphs slider +5
    • Total end result: 50 + 20 + 5 = 75 --> character has this value on that body slider
• Or, does it work differently?
  • And if so - how exactly?

 

If you've made it this far - thanks! I sincerely hope someone with more knowledge finds this and is able to provide (correct) answers! If you have additional questions, don't hesitate to reach out - I'd like to have this '1-in-1000000' questions answered and the 'issue' solved!

 

Again - sorry for cluttering this mod's page, but this seemed like the best and most active/up-to-date place to ask. If you want me to remove this post from here, say the word and I'll move it elsewhere.

 

Really hoping someone with more info and knowledge has the time to answer! Thanks in advance!

 

 

The short answer is that LM (BodyGen API) keyword morph sliders are not additive. In some older LM versions up to a few years ago, the last keyword slider added by a mod would "win" even if its value was lower than other keyword values for the same slider name, so e.g. Sex Attributes "cumflation" could hide pregnancy visuals. In more recent LM releases, the highest keyword value for the same slider is what gets rendered, so if your pregnancy progresses past the point that cumflation ends at, you'd see the belly continue to grow to normal pregnant proportions eventually.

 

The basic recommendation is just don't configure multiple mods to adjust the same sliders if you want to be able to see them all. That's the main reason I like to configure UC to only drive FG's BodyFat slider, because none of the other mods I play with collide over that.

 

Edit: The HBD_MorphDebug utility is really helpful for investigating these sorts of things, and its description gets into a lot of detail about this problem/misunderstanding.

Edited August 18 by vaultbait

[Itsjustgary]

I am currently running the game on version 1.11.240.0 and the only issue I am running into is that this mod doesn't detect "SUP F4SE". I have tried both the original linked version and the SUP F4SE AE, which is supposed to work with my current version of the game, however I still get the same notification every time I try to reload the mod in-game. The main issue this has caused is that consumables have no impact on my character's weight score. Is there something I missed?

[vaultbait]

16 hours ago, Itsjustgary said:

I am currently running the game on version 1.11.240.0 and the only issue I am running into is that this mod doesn't detect "SUP F4SE". I have tried both the original linked version and the SUP F4SE AE, which is supposed to work with my current version of the game, however I still get the same notification every time I try to reload the mod in-game. The main issue this has caused is that consumables have no impact on my character's weight score. Is there something I missed?

 

Modern versions of LooksMenu (those supporting FO4 AE) broke the check for LM in UC 1.7.1, you can just okay the warning and everything will still work, make sure you're not confusing that warning for one about SUP F4SE.

 

If it's really SUP F4SE you're still getting a warning about, that check isn't broken, the DLL for it is really not loaded as far as UC can tell, which would explain consumables not having any effect (the routine that reads the lists of them from files relies on functions specific to SUP F4SE). Check your f4se.log for lines that mention SUP_F4SE.dll and see if it was found and loaded correctly, or if there are error messages about it.

 

At the moment, the only working version I know of for 1.11.240 is the SUP F4SE all AE version AI assisted download at https://www.nexusmods.com/fallout4/mods/107607?tab=files . Just to reassure you, I'm currently using UC 1.7.1 in a test run on FO4 1.11.240 and it's working fine, so you've got something broken somewhere.

 

Edit: Okay, you know what? I'm a total airhead ditz, sorry about that! I see that I too started getting the error you're seeing. In looking at my f4se.log I see that the registered plugin name has changed from "SUP_F4SE" to "SUP F4SE" (space instead of underscore), so it's a false negative same as the F4EE (LooksMenu) plugin name change caused. If your f4se.log says that SUP_F4SE.dll (SUP F4SE) loaded correctly then Unhealthy craving should still work fine.

 

Let me go ahead and compile a patched UC:Main script correcting those checks. I'll attach it in a bit.

 

Yet still moar edit: Try this patch, it updates the checks to also recognize newer SUP F4SE and LooksMenu versions, silencing the warnings for me. (It also makes the checking more robust, warning about each missing dependency instead of stopping after the first missing one.) If you installed UC as loose files, overwrite them with this version or similarly give this patch higher priority in your mod manager. This will be part of the next UC version, so you can delete it at the next upgrade when that eventually happens.

 

 

Unhealthy Craving 1.7.1 dependency checker update patch.7z

Edited Friday at 10:52 PM by vaultbait

[rih123077549]

I installed this mod, but I can't select "Unhealthy Craving" on my Rad Morphing Redux Trigger.

 

[vaultbait]

12 hours ago, rih123077549 said:

I installed this mod, but I can't select "Unhealthy Craving" on my Rad Morphing Redux Trigger.

 

I've seen RMR fail to start cleanly in some cases, for example if configuration is applied from a saved MCM Settings Manager profile. The best workaound I've found is to go into MCM and disable RMR, then save your game, then load that save and re-enable RMR. Wait a bit and then see if UC has registered its trigger.