The problem with lack of a gradual increase belly size

[tyty2244]

Good day. How can I adjust the smoothness of the gradual increase belly size, when an actor is filled up? Currently, the belly increases instantly at jerky intervals. In other words, a partial increase belly size is instantly added every 0.2 seconds (or are these not seconds, but morph values?), while, for example, if 5 liters of cum were inflated into the actor at once.

A combination of mods "Fill Her Up Baka Edition" and "Inflation Framework" is used. The body was installed from CBBE 3BA.

In Racemenu, I tried changing PregnantBelly morph slider. Even changing the value by hundredths causes the belly to grow in little jerky intervals. I don't understand how to make the change more smooth. Maybe I should use a different body?

 

This video (alternate link) shows an example of the kind of inflation I'd like to see. I don't know if a different inflation mod is being used there, or if any other morphs, bodies, or settings have been applied. But in video inflation is smoother and more gradual.

Edited Friday at 09:58 PM by tyty2244
added alternate link

[traison]

Depends on what you mean by jerky movements. There's no tweening by the game itself, nor RaceMenu. This is a concept that's added presumably by the Papyrus mod that handles inflation (SLIF). Since it's in Papyrus, that means it's subject to Papyrus latency. If the tweening function takes into consideration time deltas between calls then it's entirely possible its going to take huge leaps when interpolating.

[tyty2244]

7 hours ago, traison said:

Depends on what you mean by jerky movements.

Something like that.

 

Spoiler

 

 

 

7 hours ago, traison said:

There's no tweening by the game itself, nor RaceMenu. This is a concept that's added presumably by the Papyrus mod that handles inflation (SLIF). Since it's in Papyrus, that means it's subject to Papyrus latency. If the tweening function takes into consideration time deltas between calls then it's entirely possible its going to take huge leaps when interpolating.

Is there a way to change this in Papyrus or through Faster HDT-SMP?

[traison]

4 hours ago, tyty2244 said:

Is there a way to change this in Papyrus...

 

The script sources are always available. If not from the author then you can decompile them yourself. Identify where the problem is and compile your changes.

 

4 hours ago, tyty2244 said:

...or through Faster HDT-SMP?

 

This has nothing to do with morphs.

 

4 hours ago, tyty2244 said:

Something like that.

 

That to me looks like a tweening function that's taking the time delta into consideration, and your Papyrus latency is high enough to only allow for 5 updates in ~5 seconds. The alternative could be that it would take about 50 seconds to do the morphing if time delta was ignored which isn't good either I'd say. So instead of poking around in scripts you should perhaps look into increasing your Papyrus ops budget or removing badly made or otherwise script-heavy mods.

 

Edit: Get Papyrus Stack Stalker if you want to do diagnostics before increasing the ops limit. This is perhaps not necessary if you're still running on the extremely choked vanilla limit. Increasing the limit too much will eventually bite you in the ass though so at some point you'll have to actually do things properly. For reference I have my ops limit set to 10,000 which is 5x the recommended upper limit if I remember correctly; but I'm also the wrong person to ask since most of my would-be script-heavy mods I made myself.

 

Edit again: I should perhaps clarify that when I implied my would-be script-heavy mods are leaner it's not because I'm claiming to be better than everyone else that scripting, it's because I have the unfair advantage of not having to take into consideration compatibility with other peoples mods: neither existing or future.

Edited Saturday at 11:42 AM by traison

[tyty2244]

On 8/15/2026 at 2:56 PM, traison said:

 

The script sources are always available. If not from the author then you can decompile them yourself. Identify where the problem is and compile your changes.

 

 

This has nothing to do with morphs.

 

 

That to me looks like a tweening function that's taking the time delta into consideration, and your Papyrus latency is high enough to only allow for 5 updates in ~5 seconds. The alternative could be that it would take about 50 seconds to do the morphing if time delta was ignored which isn't good either I'd say. So instead of poking around in scripts you should perhaps look into increasing your Papyrus ops budget or removing badly made or otherwise script-heavy mods.

 

Edit: Get Papyrus Stack Stalker if you want to do diagnostics before increasing the ops limit. This is perhaps not necessary if you're still running on the extremely choked vanilla limit. Increasing the limit too much will eventually bite you in the ass though so at some point you'll have to actually do things properly. For reference I have my ops limit set to 10,000 which is 5x the recommended upper limit if I remember correctly; but I'm also the wrong person to ask since most of my would-be script-heavy mods I made myself.

 

Edit again: I should perhaps clarify that when I implied my would-be script-heavy mods are leaner it's not because I'm claiming to be better than everyone else that scripting, it's because I have the unfair advantage of not having to take into consideration compatibility with other peoples mods: neither existing or future.

I tried increasing Papyrus ops budget by 3,000. Nothing changed.

 

When I wrote "something like that", I just wanted to show an example of the problem.

The point is that in latest versions of "Fill Her Up Baka Edition", added a "Body morph apply period" feature.

Spoiler

 

By default, it’s set to 1.0. I don’t know what the ratio is between this value and PregnantBelly value in racemenu (maybe 1:5, or maybe 1.0 equals one second), but the higher value, the more belly grows over time. The minimum value for "Body morph apply period" is 0.2. Here’s how the belly grows with a value of 0.2:

Spoiler

 

 

Slightly better, but not good enough.

 

Since "Fill Her Up" is linked with "Inflation Framework", and "Inflation Framework" gets morph from racemenu, a few possible solutions come to my mind. They might not be the best solutions, though.

First, make changes to the code in "Fill Her Up", so that the minimum value for "Body morph apply period" is 0.01, just like in racemenu. However, after moving slider in racemenu, I once again got impression that motion isn’t smooth there either, in my opinion.

Spoiler

 

 

 

The second solution is to change movement step for the "Belly - Pregnant” morph in racemenu to 0.001, or to set maximum and minimum values for "Belly - Pregnant" to -2 and 2, while maintaining proportions of the belly size at those values. If that's even possible. And also make changes to the code in "Fill Her Up", so that the minimum value for "Body morph apply period" matched with slider's new movement step in the racemenu.

 

Is it possible to do all of this for me, and is the Creation Kit enough for these tasks?

Edited Sunday at 12:10 PM by tyty2244
.

[traison]

22 minutes ago, tyty2244 said:

I tried increasing Papyrus ops budget by 3,000. Nothing changed.

 

One thing to keep in mind with this is that if you have a mod that's stuck in a loop eating up all of the Papyrus engine's budget then increasing the limit will do nothing. This is part of the reason why I tell people that while increasing the budget is a good idea or even required, doing it for the wrong reasons is not good.

 

24 minutes ago, tyty2244 said:

Slightly better, but not good enough.

...

The second solution is to change movement step for the "Belly - Pregnant” morph in racemenu to 0.001, ...

 

You will never get Papyrus to a point where it will update morphs 60 times a second. I think 2-5 updates per second is already optimistic however I haven't actually measured the performance of my own setup. Personally I did it by running it in its own Papyrus thread and in a loop with Utility.Wait(0.1) instead of OnUpdate (and with the 10k budget). But you need to keep in mind that even if there's a Wait(0.1) I'm not going to get 10 updates a second as you need to factor in the time it takes to execute the script itself including the call to UpdateModelWeight (RaceMenu).

 

I might see about benchmarking my own thing here as I've already got a TODO-list entry to create a performance measuring script for Papyrus. This could be a good excuse to get that done. Maybe someone has already made something like this, saving me the trouble.

 

38 minutes ago, tyty2244 said:

The second solution is to change movement step for the "Belly - Pregnant” morph in racemenu to 0.001...

 

I doubt the slider resolution has anything to do with the floating point precision in NiOverride; that would be a really strange limitation to add.

 

39 minutes ago, tyty2244 said:

...or to set maximum and minimum values for "Belly - Pregnant" to -2 and 2, while maintaining proportions of the belly size at those values. If that's even possible.

 

That can be done but you'd have to:

1. Repaint all bodies and armors with your new morph slider.
2. Adjust all relevant scripts to instead use the value range 0.0-2.0.

None of that will fix the update frequency issue.

 

41 minutes ago, tyty2244 said:

...is the Creation Kit enough for these tasks?

 

The only relevance the CK has here is to potentially compile Papyrus script changes.

[traison]

Did a quick performance test on my morph thread:

sample size: 120
avg: 0.14146634166666672 s
min: 0.128998 s
max: 0.192001 s

 

So the cost of running the code is ~0.04 s, and ~0.1 s is spent in Utility.Wait. In other words, should I need to, I could double the performance and get ~10 updates per second. There has to be a Wait call in a long loop otherwise you run the risk of choking the Papyrus engine and causing stack dumps when the engine is frozen/stopped. This is better than I expected myself tbh.

Edited Sunday at 01:52 PM by traison