OsmelMC Posted December 31, 2022 Author Posted December 31, 2022 3 hours ago, mikesolo1975 said: ok thanks my friend Done Dark Arena - Patch (20221231).7z
OsmelMC Posted December 31, 2022 Author Posted December 31, 2022 (edited) 2 hours ago, poporaltemporal said: I installed the sexlab utility plus and I am modding. When I compile SL files I get error for Precision_Utility being missing. That sounded familiar and I went to download Precision from nexus but it only has the compiled script but not the source. How do you compile your scripts that you don't run into these errors? The source is on the Nexus setup file but have to be manually extracted.   51 minutes ago, poporaltemporal said: After solving the Precision_Utility error I am left same errors as I had with SLSO.  First than all "experience" is a parameter type float of the SLSO "Orgasm" and "HoldOut" functions so unless you make some change on those functions, you be adding the "experience" variable something else on the "sslActorAlias" or as a property on some imported script using the "import" command. You have none reason to see those error when compile.  On my last version scripts the experience parameters is defined on the lines 3182 and 3196 of the sslActorAlias as:  function Orgasm(float experience = 0.0)  and  function HoldOut(float experience = 0.0)      On the SLSO last version scripts the experience parameters is defined on the lines 2314 and 2328 of the sslActorAlias as:  function Orgasm(float experience = 0.0)  and  function HoldOut(float experience = 0.0)    Just make sure that those too functions still are declared that way on your tweak. And in the unnatural case you can find the text "import" on the file "sslActorAlias" that is used to make that another script be considered a part of this, so in that case you should find and open that file to check if have some "experience" declared there too and do something about that because both scripts can't use the same variable name for two different things. By the way, make changes on the parameters of the functions lead to compatibility issues, so don't do it.  Edited December 31, 2022 by OsmelMC
mikesolo1975 Posted December 31, 2022 Posted December 31, 2022 2 hours ago, OsmelMC said: Done Dark Arena - Patch (20221231).7z thanks my friend for amazing work as always ?
poporaltemporal Posted January 1, 2023 Posted January 1, 2023 3 hours ago, OsmelMC said: The source is on the Nexus setup file but have to be manually extracted.  ? 3 hours ago, OsmelMC said:  First than all "experience" is a parameter type float of the SLSO "Orgasm" and "HoldOut" functions so unless you make some change on those functions, you be adding the "experience" variable something else on the "sslActorAlias" or as a property on some imported script using the "import" command. You have none reason to see those error when compile.  On my last version scripts the experience parameters is defined on the lines 3182 and 3196 of the sslActorAlias as:  function Orgasm(float experience = 0.0)  and  function HoldOut(float experience = 0.0)      On the SLSO last version scripts the experience parameters is defined on the lines 2314 and 2328 of the sslActorAlias as:  function Orgasm(float experience = 0.0)  and  function HoldOut(float experience = 0.0)    Just make sure that those too functions still are declared that way on your tweak. And in the unnatural case you can find the text "import" on the file "sslActorAlias" that is used to make that another script be considered a part of this, so in that case you should find and open that file to check if have some "experience" declared there too and do something about that because both scripts can't use the same variable name for two different things. By the way, make changes on the parameters of the functions lead to compatibility issues, so don't do it.   I installed the utility 2 days ago and I checked that its the latest ( same one on the file of this post ). Nothing is overriding the utility. I have not made any changes to sexlab or the utility. And I only have voice factor mods that add voicefactories. I compile things on AE. I have SLSO disabled because it has its own compile issues so its not affecting anything. I never done any "import" action so therefor I am confused of what you speak of.
OsmelMC Posted January 1, 2023 Author Posted January 1, 2023 18 minutes ago, poporaltemporal said: ?  I installed the utility 2 days ago and I checked that its the latest ( same one on the file of this post ). Nothing is overriding the utility. I have not made any changes to sexlab or the utility. And I only have voice factor mods that add voicefactories. I compile things on AE. I have SLSO disabled because it has its own compile issues so its not affecting anything. I never done any "import" action so therefor I am confused of what you speak of.  Just make sure that the lines of the script file are exactly like i said.   And "import" is a reserved word of many programming languages. Is used to virtually merge two or more script files in one and his main objective is be able of access to the imported script functions without write the name of the file each time. The side effect is that also merge the variables defined on that script that otherwise aren't accessible so you can end with a conflict in that case.  sslActorAlias don't have imported scripts by default but I don't know what are you doing so i have to consider that possibility too.  For example you can find the "import" command on the "sslConfigMenu" on the lines 4 and 5, to import the "PapyrusUtil" and the "SexLabUtil" into the "sslConfigMenu". This isn't related with the sslActorAlias, is just a example of how looks. Curiously you will find that even with the "PapyrusUtil" and the "SexLabUtil" imported still you can see a lot of unnecessary calls to those files on the sslConfigMenu script but is just because I prefer to do it like that instead of relays on the import.  This is all the help I can give you without seeing what you are trying to compile. 1
chasidrill Posted January 1, 2023 Posted January 1, 2023 Hi! thanks, I don't know what happened... I did try the AE option too. Tried again but renaming the mod install and it worked this time. It seems MO replace or overwrite messes up sometimes. Â
OsmelMC Posted January 1, 2023 Author Posted January 1, 2023 (edited) 13 minutes ago, chasidrill said: Hi! thanks, I don't know what happened... I did try the AE option too. Tried again but renaming the mod install and it worked this time. It seems MO replace or overwrite messes up sometimes. Â If you use replace, it makes a clean setup. But if you choose overwrite, it will keep the previous files and overwrite the selected files. The problem is when you for some reason have files of some previous SE setup because my SE setup include files that aren't required for the AE and the file in question is precisely the file that have the SE version number. Â Â Edited January 1, 2023 by OsmelMC
Iroha Posted January 1, 2023 Posted January 1, 2023 (edited) Hi, @OsmelMC, I have 2 questions.:)  You are using GetDiff, GetDiffForm, GetMatching of PapyrusUtil 4.0+ in some of SLU+ scripts for all of skyrim x64 versions. But latest version of Papyrus utils for Skyrim SE 1.5.97 is 3.9, which lacks these new functions, also, Papyrus Utils 4.0+ requiring skse version >2.0.0.20 (which is last for Skyrim se 1.5.97). So, I suppose there will be problems in scrips execution for all users of SE 1.5.97. Am I right? (I don't know, maybe there is workaround to use latest versions of Papyrus for all se versions?? Or maybe it doesn't matter at all since scripts already compiled?)  And one more thing, in latest 20221229 build in sslAnimationSlots you checking version of Precision plugin, but maybe before it better to check if plugin actually exists in Load Order?  P.S. wish you good new year! Edited January 1, 2023 by Iroha 1
alranteesi Posted January 1, 2023 Posted January 1, 2023 Hi OsmelMC, last utility update working with sexlab v1.63 Beta9? and thanks for ur works.
Iroha Posted January 1, 2023 Posted January 1, 2023 13 minutes ago, alranteesi said: Hi OsmelMC, last utility update working with sexlab v1.63 Beta9? and thanks for ur works. Yes, if you are on SE, not AE.
OsmelMC Posted January 1, 2023 Author Posted January 1, 2023 1 hour ago, alranteesi said: Hi OsmelMC, last utility update working with sexlab v1.63 Beta9? and thanks for ur works. Better install the official v1.63 if you are on SE, but yes. I only check the compatibility with the last versions of SexLab Framework for each one of the 3 Skyrim versions. 1
OsmelMC Posted January 1, 2023 Author Posted January 1, 2023 (edited) 10 hours ago, Iroha said: Hi, @OsmelMC, I have 2 questions.:)  You are using GetDiff, GetDiffForm, GetMatching of PapyrusUtil 4.0+ in some of SLU+ scripts for all of skyrim x64 versions. But latest version of Papyrus utils for Skyrim SE 1.5.97 is 3.9, which lacks these new functions, also, Papyrus Utils 4.0+ requiring skse version >2.0.0.20 (which is last for Skyrim se 1.5.97). So, I suppose there will be problems in scrips execution for all users of SE 1.5.97. Am I right? (I don't know, maybe there is workaround to use latest versions of Papyrus for all se versions?? Or maybe it doesn't matter at all since scripts already compiled?)  And one more thing, in latest 20221229 build in sslAnimationSlots you checking version of Precision plugin, but maybe before it better to check if plugin actually exists in Load Order?  P.S. wish you good new year! I use alternative functions for LE and for SE you should use this PapyrusUtil that i don't remember where come from but include the functions.  PapyrusUtil SE.7z  I don't notice that my PapyrusUtil was different until was too late to roll back.  The safest way to check the presence of on DLL plugin is using the version check of the SKSE. Usually the DLL files comes with it's own papyrus functions to know the version installed and with that know if is installed but those papyrus functions are useless when the Mod isn't installed and even cause errors on the logs. Precision is one of the few Mods that can be also checked throw the presence of the ESP file but Precision use the ESP file only for the configuration so probably can work even without the ESP file so the ESP file isn't reliable. Use the version check of the SKSE also have the advantage of allow me know if is the version with scripts and is fast. The only reason why more programmer's don't use the SKSE function is for lack of knowledge by the way SKSE return version -1 when the DLL isn't installed.   Happy New Year too! Edited January 1, 2023 by OsmelMC 1
Barka Posted January 1, 2023 Posted January 1, 2023 31 minutes ago, OsmelMC said: I use alternative functions for LE and for SE you should use this PapyrusUtil that i don't recommend where come from but include the functions.  PapyrusUtil SE.7z 377.35 kB · 259 downloads  I don't notice that my PapyrusUtil was different until was too late to roll back.  The safest way to check the presence of on DLL plugin is using the version check of the SKSE. Usually the DLL files comes with it's own papyrus functions to know the version installed and with that know if is installed but those papyrus functions are useless when the Mod isn't installed and even cause errors on the logs. Precision is one of the few Mods that can be also checked throw the presence of the ESP file but Precision use the ESP file only for the configuration so probably can work even without the ESP file so the ESP file isn't reliable. Use the version check of the SKSE also have the advantage of allow me know if is the version with scripts and is fast. The only reason why more programmer's don't use the SKSE function is for lack of knowledge by the way SKSE return version -1 when the DLL isn't installed.   Happy New Year too! Is your PapyrusUtil like 3.9 but better? Should we replace default with your version?Â
OsmelMC Posted January 1, 2023 Author Posted January 1, 2023 8 minutes ago, Barka said: Is your PapyrusUtil like 3.9 but better? Should we replace default with your version? Is not my version. Probably is the version on the GitHub but I got it when the official SexLab v1.63 was released and not longer remember the source. And yes you should install "my version" at the bottom of the Mod list, to make sure that none other version is overwriting it. By the way have the same version number 39 than the public SE version. 2
Barka Posted January 1, 2023 Posted January 1, 2023 1 minute ago, OsmelMC said: Is not my version. Probably is the version on the GitHub but I got it when the official SexLab v1.63 was released and not longer remember the source. And yes you should install "my version" at the bottom of the Mod list, to make sure that none other version is overwriting it. By the way have the same version number 39 than the public SE version. Okay. But you should mention it on download page too
OsmelMC Posted January 1, 2023 Author Posted January 1, 2023 36 minutes ago, Barka said: Okay. But you should mention it on download page too Done 2
Iroha Posted January 1, 2023 Posted January 1, 2023 8 hours ago, OsmelMC said: I use alternative functions for LE and for SE you should use this PapyrusUtil that i don't recommend where come from but include the functions.  PapyrusUtil SE.7z 377.35 kB · 292 downloads  I don't notice that my PapyrusUtil was different until was too late to roll back.  The safest way to check the presence of on DLL plugin is using the version check of the SKSE. Usually the DLL files comes with it's own papyrus functions to know the version installed and with that know if is installed but those papyrus functions are useless when the Mod isn't installed and even cause errors on the logs. Precision is one of the few Mods that can be also checked throw the presence of the ESP file but Precision use the ESP file only for the configuration so probably can work even without the ESP file so the ESP file isn't reliable. Use the version check of the SKSE also have the advantage of allow me know if is the version with scripts and is fast. The only reason why more programmer's don't use the SKSE function is for lack of knowledge by the way SKSE return version -1 when the DLL isn't installed.   Happy New Year too! Thanks!
OsmelMC Posted January 1, 2023 Author Posted January 1, 2023 15 minutes ago, Iroha said: Thanks! Wow, I just noticed that said "recommend" instead of "remember". Â Is: I don't remember where come from.
ShimizuModding Posted January 2, 2023 Posted January 2, 2023 anyone have a way to unlock the sliders of the expressions in sexlab? maximum value is at 100 while im want to go beyond it
applesandmayo Posted January 2, 2023 Posted January 2, 2023 I'm getting something odd with SL 1.63 beta 8 and the latest SL Utility (2022.12.19). Any time a sexlab animation begins with two or more actors, (in this case for just narrowing down purposes, myself the PC and some random NPC), before the animation actually begins, the NPC will strip for a half second, redress fully, and the animation will then start. Â I know that SLSF has a redress utility, for which I have turned off, but I'm still getting this error. Any ideas on where I should look in logs for what is causing it?
r3mind Posted January 2, 2023 Posted January 2, 2023 (edited) There is an option in SLSO to make consensual animations require actors to orgasm (not only aggressors), but I always wondered why it never worked until I decided to study the sslThreadController.psc code. For some reason in function SLSO_Animating_GoToStage(int ToStage) there is a condition "if ActorAlias.IsAggressor() && ... " which basically makes the option I mentioned useless. I made 2 small changes to the script (this condition and also got rid of SLSO_shouldrun_SLSO_Animating_GoToStage condition) and managed to make all scenes in my game to keep switching animations until male actors orgasm (which is pretty handy with auto advance stages enabled).  Is there a reason why this SLSO feature doesn't work by default? I think it would be nice to have it finally fixed^^ I'm asking in this thread, because I'm using SexLab Utility Plus and it overwrites SLSO scripts anyway. Edited January 2, 2023 by Vigor 4
OsmelMC Posted January 2, 2023 Author Posted January 2, 2023 11 hours ago, applesandmayo said: I'm getting something odd with SL 1.63 beta 8 and the latest SL Utility (2022.12.19). Any time a sexlab animation begins with two or more actors, (in this case for just narrowing down purposes, myself the PC and some random NPC), before the animation actually begins, the NPC will strip for a half second, redress fully, and the animation will then start. Â I know that SLSF has a redress utility, for which I have turned off, but I'm still getting this error. Any ideas on where I should look in logs for what is causing it? The most common reason is that some Mod already force one or more equippable items to stay always equipped in which case the actor get redressed each time one equippable item is added. This case usually isn't related with SexLab but can be related to some Sex Mod adding items to the actor before the scene start. Â Also you shouldn't be using the BETA 8
OsmelMC Posted January 2, 2023 Author Posted January 2, 2023 10 hours ago, Vigor said: There is an option in SLSO to make consensual animations require actors to orgasm (not only aggressors), but I always wondered why it never worked until I decided to study the sslThreadController.psc code. For some reason in function SLSO_Animating_GoToStage(int ToStage) there is a condition "if ActorAlias.IsAggressor() && ... " which basically makes the option I mentioned useless. I made 2 small changes to the script (this condition and also got rid of SLSO_shouldrun_SLSO_Animating_GoToStage condition) and managed to make all scenes in my game to keep switching animations until male actors orgasm (which is pretty handy with auto advance stages enabled).  Is there a reason why this SLSO feature doesn't work by default? I think it would be nice to have it finally fixed^^ I'm asking in this thread, because I'm using SexLab Utility Plus and it overwrites SLSO scripts anyway. This should be reported on the SLSO thread. I can fix it here but probably be rolled back when the next SLSO version be released, since I copy paste it's scripts into my scripts changing only those that are incompatible.
applesandmayo Posted January 2, 2023 Posted January 2, 2023 (edited) 24 minutes ago, OsmelMC said: The most common reason is that some Mod already force one or more equippable items to stay always equipped in which case the actor get redressed each time one equippable item is added. This case usually isn't related with SexLab but can be related to some Sex Mod adding items to the actor before the scene start. Â Also you shouldn't be using the BETA 8 I've been running Beta 8 since playing modded SkyrimSE, why shouldn't I be using it? Not going up against you on that, if there is a better version I should be using, I'd like to know, I just want to know why not Beta 8. I presume the latest stable release of Sexlab would be preferred? I'm just not positive that all my current mods are compatible, even though most if not all are up to date. I think some of my mods state that Beta 8 is required, but those mod descriptions may just be out of date. Â Also, I'm on SSE 1.5.97. Edited January 2, 2023 by applesandmayo
XxX_PrOgAmEr420_XxX Posted January 3, 2023 Posted January 3, 2023 Hey, necro animations have stopped working since i installed this (latest version). Im on LE. Im using the extra patch. Not sure whats going on tbh. I have tried resetting animation registry and cleaning animation cache, didnt work.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now