The belly with the pregnant morph looks broken (SOLVED)

[Qwert_yyy]

I'm using Fill Her Up, just the CBPC physics and the BHUNP body. When the character's belly grows up, it looks broken.

Here's an example: 

Spoiler

 

I wrote to the CBPC mod author page, but he replied as follows: 
"That would require gravity to be added to your belly bounce configs. That's not from default configs. I haven't seen 3BA add it either. I don't know if BHUNP adds it or not. But probably not, why would it. You can check CBPConfig****.txt files"

 

I've tried disabling all physics in "CBPConfig_belly.txt", but to no avail.

Perhaps someone has thoughts on this? It looks like sagging due to heaviness, but I can't figure out where I can turn that off.

Edited August 13, 2023 by Soldream

[traison]

To me that looks like you're using NiOverride/Racemenu to scale the node instead of the Pregnancy morph provided by BodySlide/RaceMenu.

[Qwert_yyy]

14 minutes ago, traison said:

To me that looks like you're using NiOverride/Racemenu to scale the node instead of the Pregnancy morph provided by BodySlide/RaceMenu.

 

It's kind of in the settings of the Fill Her Up mod itself, isn't it? Let me check.

[traison]

I'd say it would be in SLIF, since FHU only provides SLIF with information. SLIF is the one that interfaces with RaceMenu.

 

Edit: or at least that's how it was years ago when I last saw these mods. I made my own after that.

Edited August 13, 2023 by traison

[Qwert_yyy]

16 minutes ago, traison said:

I'd say it would be in SLIF, since FHU only provides SLIF with information. SLIF is the one that interfaces with RaceMenu.

 

Edit: or at least that's how it was years ago when I last saw these mods. I made my own after that.

 

Yes, you were right. It was what you said.

By the way, do you have any idea how we could get this mod to use with old bodies? 
Follower Onean is based on a somewhat outdated skeleton. Personally, I have all the physics working fine for her, and also there are no bugs with physics or anything like that. But specifically in the case of "Fill Her Up", toggling that feature causes the belly to not work for that character.

[traison]

Well basically what you need is the Pregnancy morph for that character. What I would personally attempt is a conversion of all their outfits (naked body is an outfit too) to a newer body. For instance, if that follower is using regular CBBE, its quite trivial to convert that to 3BA with Outfit Studio as long as there's no intricate armors involved. I'd imagine the same goes for UNP->BHUNP.

 

You may also get lucky by identifying the armors your follower uses and seeing if someone already made a conversion for it. Replace the follower's armor meshes with the converted ones.

 

If none of those are an option, or you just feel like being more adventurous, you could just do it yourself: Add a new slider called Pregnancy and use the tools in Outfit Studio to build the morph yourself. It won't look identical, but who knows, may turn out ok.

 

Edit: Obviously if the follower comes with no custom armors and the naked body is the only issue, then simply locate their body meshes and replace them with the player body mesh. You can also edit their race record in xEdit, and have it point to the same mesh the player uses, this is what I always do.

Edited August 13, 2023 by traison

[Qwert_yyy]

28 minutes ago, traison said:

Well basically what you need is the Pregnancy morph for that character. What I would personally attempt is a conversion of all their outfits (naked body is an outfit too) to a newer body. For instance, if that follower is using regular CBBE, its quite trivial to convert that to 3BA with Outfit Studio as long as there's no intricate armors involved. I'd imagine the same goes for UNP->BHUNP.

 

You may also get lucky by identifying the armors your follower uses and seeing if someone already made a conversion for it. Replace the follower's armor meshes with the converted ones.

 

If none of those are an option, or you just feel like being more adventurous, you could just do it yourself: Add a new slider called Pregnancy and use the tools in Outfit Studio to build the morph yourself. It won't look identical, but who knows, may turn out ok.

 

Edit: Obviously if the follower comes with no custom armors and the naked body is the only issue, then simply locate their body meshes and replace them with the player body mesh. You can also edit their race record in xEdit, and have it point to the same mesh the player uses, this is what I always do.

 

This companion has its own modified skeleton and body preset that cannot be replicated. I tried to do this a long time ago, even though it sounds like a completely wild action now, but the body built this way is really different from anything we can build using just the sliders in BodySlide. (Unfortunately I pay too much attention to detail (it's a personal problem:) ) )).
Sorry for the long text, I just want to fully explain the reason why I would like to keep the look exactly as it is now, but not change her skeleton and body to the modern one.

If I understand correctly, all the options you've proposed unfortunately boil down to replacing her body.

 

I've noticed one odd thing that might work. FHU changes the body node of "PregnancyBelly", which is called "Pregnant" in BodySlide. This is set in the settings initially. But directly in the game, we can see that another node is changed, which is called in BodySlide as "PregnantSmall".  This node is not present in the other bodies. Perhaps that's the reason. I don't know, but now I'll try to play with the settings in different ways and see what happens. It does look like an FHU error.

p.s. That is, to put it another way, FHU changes the wrong node in the settings.

Edited August 13, 2023 by Soldream

[traison]

Again, FHU is the one that feeds data to SLIF. SLIF is the one that interfaces with RaceMenu. As far as I know, the newer (old now) versions of SLIF come with a configuration file (maybe written in json) that specifies which morphs to activate. If this PregnantSmall node is not available in other bodies, you can get away with having it morph along with the node that is in the other bodies.

 

i.e. instead of having it say:

"PregnancyBelly": 10

 

Do this:

"PregnancyBelly": 10

"PregnantSmall": 10

 

Pseudocode obviously but you get the idea.

 

Edit: Just need to keep in mind if you ever find an outfit with both, it will morph both: 10+10

Edited August 13, 2023 by traison

[Qwert_yyy]

2 hours ago, traison said:

Again, FHU is the one that feeds data to SLIF. SLIF is the one that interfaces with RaceMenu. As far as I know, the newer (old now) versions of SLIF come with a configuration file (maybe written in json) that specifies which morphs to activate. If this PregnantSmall node is not available in other bodies, you can get away with having it morph along with the node that is in the other bodies.

 

i.e. instead of having it say:

"PregnancyBelly": 10

 

Do this:

"PregnancyBelly": 10

"PregnantSmall": 10

 

Pseudocode obviously but you get the idea.

 

Edit: Just need to keep in mind if you ever find an outfit with both, it will morph both: 10+10

 

That was my plan in the end:)
What I said about the FHU mod not changing the node correctly is true.
But unfortunately it had no effect on the companion. I even tried to use another mod for this. Ocum Ascended. Which performs the same function.

 

By the way, I didn't have the SLIF mod, but I tried installing it, as well as the patch for FHU, but I couldn't figure out SLIF. It looks complicated for a simple user.

 

I guess that leaves me with two options. 
Or I have to change something in the Onean body file so that it is seen as BodySlide/RaceMenu and not NiOverride/Racemenu.
Or I stay with NiOverride.

 

Do you happen to have any thoughts, at least theoretical ones, that would point me to information on what would need to be understood for the first option? Because it sounds like something complicated, right?

Edited August 13, 2023 by Soldream

[traison]

First of all I didn't even know a non-SLIF version of FHU even existed; but if we assume one actually does exist (ie. what you're using is not some stoneage version for pre-LE or the like) then your option #2 is to rip the NiOverride node scaling part of it out and replace it with calls to NiOverride.SetBodyMorph.

 

Edit: as for the json file edit, all I know is that people have trouble finding them as they're apparently "sold separate". Buried in some thread somewhere last I saw one.

Edited August 13, 2023 by traison

[Qwert_yyy]

3 minutes ago, traison said:

First of all I didn't even know a non-SLIF version of FHU even existed; but if we assume one actually does exist (ie. what you're using is not some stoneage version for pre-LE or the like) then your option #2 is to rip the NiOverride node scaling part of it out and replace it with calls to NiOverride.SetBodyMorph.

 

Edit: as for the json file edit, all I know is that people have trouble finding them as they're apparently "sold separate". Buried in some thread somewhere last I saw one.

 

 I wildly apologize, I should have specified that it was "FHU Baka". I just thought the old FHU was already extremely outdated. 

 

What you said at the end of your sentence, is that what you mean by editing the script? Actually right in FHU Baka there is a toggle function. The old way of processing and the new way. Here is the description of this function in the MCM menu: "Enable Body Morph Scale instead of NIO Bone Scale. If you are an LE user, disable it. However if you are an SE user, enable it."

 

Again, I apologize for not mentioning this beforehand, I really thought everyone only used FHU Baka

[traison]

Had a look at the code. It's hardcoded to use PregnancyBelly, and changing it to use 2 different nodes would require quite a lot of editing. Not difficult edits, mostly copy-paste, but its kinda all over the place in the code.

 

If you simply want to test whether the other node works on your follower then change this accordinly in sr_inflateConfig.psc:115

String Property FHUMorphString = "PregnancyBelly" Auto

 

Edit: Obviously have to compile the script after editing it.

Edited August 13, 2023 by traison

[Qwert_yyy]

16 minutes ago, traison said:

Had a look at the code. It's hardcoded to use PregnancyBelly, and changing it to use 2 different nodes would require quite a lot of editing. Not difficult edits, mostly copy-paste, but its kinda all over the place in the code.

 

If you simply want to test whether the other node works on your follower then change this accordinly in sr_inflateConfig.psc:115

String Property FHUMorphString = "PregnancyBelly" Auto

 

Edit: Obviously have to compile the script after editing it.

 

I think I've already checked it out, but in a different way. As I said before, I tried using the Ocum Ascended mod. (This is a mod for the OstimNG framework.) This mod also modifies the belly and modifies specifically the PregnancyBelly node. Unfortunately it didn't work, so it turns out that it's really because it's related to "Body Morph Scale instead of NIO Bone Scale".

Edited August 13, 2023 by Soldream

[traison]

Plan Z then is to repaint the belly weight paint so that it doesn't look like a saggy balloon anymore, and go with the NIO Bone Scale option like before. This can be done in Outfit Studio. You can preview it with the pose mode and setting the scale of the belly node to >0.

 

Edit: FHU appears to be using NPC Belly, in case that body has multiple.

Edited August 13, 2023 by traison

[Qwert_yyy]

38 minutes ago, traison said:

Plan Z then is to repaint the belly weight paint so that it doesn't look like a saggy balloon anymore, and go with the NIO Bone Scale option like before. This can be done in Outfit Studio. You can preview it with the pose mode and setting the scale of the belly node to >0.

 

Edit: FHU appears to be using NPC Belly, in case that body has multiple.

 

I'll try a couple more days of digging into this issue, otherwise I'll be using NIO.

You have already spent more time on me than the situation required, thank you for your help, kind man.

Edited August 13, 2023 by Soldream

[Qwert_yyy]

51 minutes ago, traison said:

 

By the way, I keep looking at your avatar and hearing in my right ear. 
"Hello, good morning. You have reached the Technical Support department of SkyrimModding. How can we help you?" 
No offense, just kidding)

[traison]

How did you know??

[Qwert_yyy]

36 minutes ago, traison said:

Как ты узнал??

 

XD

[Nerosckan]

In case that someone is going through the same issue, remember to check the load order of the mods, that was the issue for me, I had to move FHU Baka edition under the normal FHU and it works.

[Solissix]

😵‍💫Why are you running both? Baka's version is a direct replacement. Having both is at best redundant, at worst, you'll end up with random bugs or broken scripts. All versions of FHU are already super delicate and prone to breaking as is.

[Nerosckan]

It was a requirement for Baka and it was crashing if I didn't use both sadly.