Jump to content

A Simple & Easy Proposal For Sex Frameworks: Location-Type Specific Z-Offset


Recommended Posts

Posted (edited)

Everyone has seen this: A sexscene starts, but you're in the wilderness or uphill slope in a town, so one or multiple actors clip into the ground.

 

That's a Skyrim limitation that cannot really fixed. But it can be mostly mitigated by positioning the scene slightly higher on the Z-axis. This works, since "floating" bodyparts are less annoying than say, an actors hand being entirely chopped off by sinking into the ground. But how much Z-offset is needed varies from one spot to another. Trying to automatically detect it with some kind of raycasting is expensive and error-prone. Possibly even crashprone, given the amount of raycasting mods crashing i've seen.

 

So instead i have a much simpler and cheaper idea: I've noticed that elevating the scene by 0.5 units avoids most clipping on perfectly flat terrain, such as housefloors. On city-streets the most bang for the buck is around 1.0 units. And in the wilderness a scene z-offset of 2.0 avoids most clipping on flat but uneven terrain. Still clips on slopes of course, but that cannot really be fixed anyways without tilting the whole scene.

 

So in summary: Most ground-clipping could be avoided, if sexscenes would be elevated 0.5 units in houses, 1.0 units in cities, and 2.0 units everyhwere else (wilderness and dungeons). 

 

Now who should be responsible for making those adjustments? Not the animation creator. His job should be to align for an ideal scenario - perfectly flat surfaces using 1.0 raceheights and vanilla body proportions. This way frameworks and users start with perfectly calibrated values and make adjustments as needed, instead of starting with unknown offsets already baked in.

 

Neither should users making offset corrections be responsible for accounting for terrain. Firstly because the purpose of those offset corrections is to account for custom races and body-proportions. Secondly because terrain varies, so a single global offset is the wrong tool for the job.

 

Instead sex-frameworks should simply look at the location type: Are we in a house? A city? Or anywhere else? It's just two conditions to check. Pseudocode: "IF location == house THEN ZOffset += 0.5 ELSEIF location == city THEN ZOffset += 1.0 ELSE ZOffset += 2.0 END"

 

The offset values for each of the three cases could also be configurable in MCM, so users who don't like the feature can just set them to 0.0 - or change them to whatever they prefer.

Edited by libertyordeath
  • libertyordeath changed the title to A Simple & Easy Proposal For Sex Frameworks: Location-Type Specific Z-Offset

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...