Jump to content

SexLab SE - Sex Animation Framework v1.66b - 01/18/2024


Recommended Posts

Posted

So an update from my last post: This might be relevant for some of you, but Estrus' developer is trying to work on a current version, but they need help with it. As for the File Access Interface (the one that has fiss.dll, does anyone know what that is for?) Its the only other script that seems to be broken now. The new Racemenu is up, and if FasterSMP can be used as a replacer for the original HDT-SMP mod, that's updated now, too. The original HDT-SMP is unfortunately not updated yet.

Posted
7 hours ago, Seeker999 said:

Hi Ashal, appreciate you getting this out so fast. But, the day after you posted this skse posted a newer update, v2.2.5, for SSE 1.6.1130.


I think this is causing issues for those who updated to the most recent skse.

Posted (edited)
6 hours ago, Talamaeus said:

fiss.dll, does anyone know what that is for?

 

for many things

check section "Mods requiring this file", unfortunately it does not cover LL mods

Edited by PippinTom
Posted
8 hours ago, Talamaeus said:

So an update from my last post: This might be relevant for some of you, but Estrus' developer is trying to work on a current version, but they need help with it. As for the File Access Interface (the one that has fiss.dll, does anyone know what that is for?) Its the only other script that seems to be broken now. The new Racemenu is up, and if FasterSMP can be used as a replacer for the original HDT-SMP mod, that's updated now, too. The original HDT-SMP is unfortunately not updated yet.

https://www.nexusmods.com/skyrimspecialedition/mods/13956

Posted

I came to ask if there were problems with the new version (1.6.1130), and I see that there are. I use most bestiality mods, do they work? Or should I wait for the mods to be updated?

Posted

Hey, guys. So, weirdest thing. I have been using this framework and multiple mods that depend on it for months now, and I haven't updated my game nor this mod, nor any sort of mature content mod. However, whenever I start a new game, SexLab won't start. It'll be in the MCM list but whenever I click it, there's nothing there. This started happening a few days ago (maybe 4) and I've tried fixing it a lot of ways with no success.

 

Does anyone know what could be causing this issue? I'm not getting any crashes, the mod just doesn't seem to be able to fully initialize in-game and therefore it can't be installed (in-game). I'm running AE, btw (again, not updated, it's 1.6.640 with SL 1.65). Thanks in advance.

Posted

Ok been reading through the comments here, being in the IT field, knowing the common practices used with version why is SL 1.65, able to be used with skyrim ae 1.6.640 and SL 1.66 version cant and sends back an error on the dll? am I missing something? If is am using 1.6.640 why would I down grade to skyrim 1.6.1130 when it is an older version of skyrim ae, to use a new version of SL?? 

 

Posted
4 minutes ago, tonitrulupus said:

1.6.640 why would I down grade to skyrim 1.6.1130

Because 1.6.1130 is a higher number than 1.6.640 ?

 

Posted
49 minutes ago, Tlam99 said:

Because 1.6.1130 is a higher number than 1.6.640 ?

 

A in numbers no 6 is higher then 1 is it not? unless you right it 1.6.11.30 but you would have to write 1.6.6.40, in this case it isin the other methon it is not. you cam have .113983662345, but .640000000000 will still be higher, its in the way you write it, but if .1130 is the latest skyrim then it is Bethesda that is not holding true to the numbering system. and nubers, leaving out version contect is .640 not a larger number then .1130 in decimals? 

 

Posted
16 minutes ago, tonitrulupus said:

A in numbers no 6 is higher then 1 is it not? unless you right it 1.6.11.30 but you would have to write 1.6.6.40, in this case it isin the other methon it is not. you cam have .113983662345, but .640000000000 will still be higher, its in the way you write it, but if .1130 is the latest skyrim then it is Bethesda that is not holding true to the numbering system. and nubers, leaving out version contect is .640 not a larger number then .1130 in decimals? 

 

1130 is a higher number than 640. Thought that was obvious, guess I have a wierd brain ;)

Posted
1 hour ago, tonitrulupus said:

Ok been reading through the comments here, being in the IT field, knowing the common practices used with version why is SL 1.65, able to be used with skyrim ae 1.6.640 and SL 1.66 version cant and sends back an error on the dll? am I missing something? If is am using 1.6.640 why would I down grade to skyrim 1.6.1130 when it is an older version of skyrim ae, to use a new version of SL??

Every time there is an update to Skyrim, SKSE and all SKSE plugin mods must be updated to be compatible. This can take hours, days, weeks, or for some mods it may not happen at all. SkyrimSE.exe version 1.6.640 was around for a long time, so it is currently the most compatible. The update to 1.6.1130 was only a week ago.

 

You will need to look at which SKSE plugin mods you want to install and which version of SkyrimSE.exe they are compatible with.

Posted
1 hour ago, tonitrulupus said:

A in numbers no 6 is higher then 1 is it not? unless you right it 1.6.11.30 but you would have to write 1.6.6.40, in this case it isin the other methon it is not. you cam have .113983662345, but .640000000000 will still be higher, its in the way you write it, but if .1130 is the latest skyrim then it is Bethesda that is not holding true to the numbering system. and nubers, leaving out version contect is .640 not a larger number then .1130 in decimals? 

 

 

1130 is newer then 640.  The version is not a number it's a string, numbers also can't have multiple decimal points making your entire post irrelevant. 

Posted
1 hour ago, tonitrulupus said:

A in numbers no 6 is higher then 1 is it not? unless you right it 1.6.11.30 but you would have to write 1.6.6.40, in this case it isin the other methon it is not. you cam have .113983662345, but .640000000000 will still be higher, its in the way you write it, but if .1130 is the latest skyrim then it is Bethesda that is not holding true to the numbering system. and nubers, leaving out version contect is .640 not a larger number then .1130 in decimals? 

 

 

Except this is software versioning, not decimal versioning.

Major, minor, patch. x.y.zzzz

 

When the number after the decimal increases so the first number after a decimal is above 9, the previous level is not always increased as it would be in decimal. Instead, a place is added after the decimal. So the numbers can go from 1 - 9 to 1 - 99 to 1 - 999, and so on. 

 

The patch version was incremented with the last release, not the major or minor version. So that changed the range from 1 - 999 to 1 - 9999.

So .640 starts with 6 (six)

And .1130 starts with 11 (eleven) and not 1. 

Posted
1 hour ago, ebbluminous said:

1130 is a higher number than 640. Thought that was obvious, guess I have a wierd brain ;)

yeah but one you put a . in front of 11 it becomes a smaller, that is why a period should have been added behind the 11 and the 6 in both versions, its the same reason why thy dont use letter i in license plates.  do you count 6 then 1 then 9? I have never seen anyone do upgrade versions by counting backwards, leave it to Bethesda.  That begin said this is the version number V 1.6.1130.0.8

That is a bigger number this would indicated that the ver I am using is 1.6.640.0.0 see how the way it is written can change the meaning behind it. something to keep in mind if you a modder.

Posted
15 minutes ago, zarantha said:

 

Except this is software versioning, not decimal versioning.

Major, minor, patch. x.y.zzzz

 

When the number after the decimal increases so the first number after a decimal is above 9, the previous level is not always increased as it would be in decimal. Instead, a place is added after the decimal. So the numbers can go from 1 - 9 to 1 - 99 to 1 - 999, and so on. 

 

The patch version was incremented with the last release, not the major or minor version. So that changed the range from 1 - 999 to 1 - 9999.

So .640 starts with 6 (six)

And .1130 starts with 11 (eleven) and not 1. 

Must have changed fairly recent, I have ever seen some one write a version like that and I have been doing computers since 1985, this is the first time i have seen it, guess you learn something new.

 

Posted

I need help with downgrading. I uninstalled SE and reinstalled it, downgraded it with the downgrader from nexus, redid my mods and what not (ENB included). Now, I try to launch SKSE and it takes a little to load, the ENB info pops up, and then the game closes. 

 

What do I do?

Posted
1 hour ago, tonitrulupus said:

yeah but one you put a . in front of 11 it becomes a smaller, that is why a period should have been added behind the 11 and the 6 in both versions, its the same reason why thy dont use letter i in license plates.  do you count 6 then 1 then 9? I have never seen anyone do upgrade versions by counting backwards, leave it to Bethesda.  That begin said this is the version number V 1.6.1130.0.8

That is a bigger number this would indicated that the ver I am using is 1.6.640.0.0 see how the way it is written can change the meaning behind it. something to keep in mind if you a modder.

Hoooow?

 

1.6.1130 is still higher than 1.6.640 cause it is .1130 of 1.6 compared to .640 of 1.60. 640 is smaller than 1130 unless you use girl math.

Posted (edited)

Has anyone gotten Sexlab 1.66 to work for Skyrim 1.6.1130? Nemesis is able to see and compile sexlab animations, but when I go into a game (new save or save) the MCU doesn't show up and other mods that need sexlab dont see it being loaded. Tried it with a fresh game with just sexlab and the needed mods and still a no go.

 

Edit: Nevermind, im dumb. It was a load order issue.

Edited by iSc00t
Posted
15 hours ago, mattvm said:

whenever I start a new game, SexLab won't start. It'll be in the MCM list but whenever I click it, there's nothing there.

 

 

If you are starting new game "vanilla style" (with cart ride and helgen scene), then sexlab won't start until you get to "catacombs", which is when 3rd person perspective becomes available, and it is required for proper SLF installation, and late in-game updates for that matter.

Posted

I'm having an odd problem for which I would greatly appreciate some advice if possible.

 

I've got the latest Sexlab (v1.66) and Papyrus (v4.5) installed and everything that relies on both are either working or showing through MCM that both are present and working.

 

However, when I try to install/activate Sexlab through the MCM menu, it doesn't register that I have Papyrus installed and thus won't let me install/activate Sexlab through the MCM menu.

 

I've read through the previous pages but couldn't find anything that gave me any ideas, so as stated previously, I would greatly appreciate any advice if anyone else has come across this issue?

 

Many thanks,

Posted
8 hours ago, PippinTom said:

 

If you are starting new game "vanilla style" (with cart ride and helgen scene), then sexlab won't start until you get to "catacombs", which is when 3rd person perspective becomes available, and it is required for proper SLF installation, and late in-game updates for that matter.

I'm using Unbound. I don't know, sometimes it works, sometimes it doesn't. Sometimes it's Creatures Aroused that doesn't work. It took me messing with the load order and starting new games 8 or 9 times for both of them to open in the MCM (they're always there, but my issue is that the MCM seems to get stuck loading them when I click them on the list).

 

Must be some mod I installed recently. I thought it could be Improved Camera, so I tried reinstalling with and without the patches for SL mods included in the FOMOD. Then I started getting full-on crashes and realized I shouldn't mess with that. 

 

I also disabled a couple of creature overhauls I downloaded recently that I knew were not compatible with Aroused Creatures and Creature Framework, but I'm not even sure that that was the issue. I'll try starting a new new game to see if I just got lucky when starting the current one or if I actually fixed the problem (somehow). Thanks for the reply!

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...