Ghostman7nz Posted December 19, 2021 Posted December 19, 2021 6 hours ago, superspyro90 said: Did all that, and it's still broken Be sure to completely uninstall 1.64b from your favorite mod manager then download 1.64b again and install as usual. If you try to just reinstall without uninstalling first then the mod manager assumes you are installing the same file again and doesn't overwrite some files. It took me hours to figure this out but once I did everything worked without issue
maultex Posted December 19, 2021 Posted December 19, 2021 Try updating/downloading SSE Engine Fixes. That fixed the problem with Address Library for me.
maultex Posted December 19, 2021 Posted December 19, 2021 Just now, maultex said: Try updating/downloading SSE Engine Fixes. That fixed the problem with Address Library for me. Refering to the CTD confusion after people updated Address Library to the latest version. SSE Engine Fixes: (Anniversary Edition is 1.6.xxx) https://www.nexusmods.com/skyrimspecialedition/mods/17230?tab=files
raiderornot Posted December 19, 2021 Posted December 19, 2021 Skyrim SSE and AE Are Broke Play LE No Crying.
zarantha Posted December 19, 2021 Posted December 19, 2021 1 hour ago, raiderornot said: Skyrim SSE and AE Are Broke Play LE No Crying. There's crying with LE too, due to CTDs from memory issues. Nothing is perfect.
RyukyuShin1997 Posted December 19, 2021 Posted December 19, 2021 11 hours ago, Ghostman7nz said: Be sure to completely uninstall 1.64b from your favorite mod manager then download 1.64b again and install as usual. If you try to just reinstall without uninstalling first then the mod manager assumes you are installing the same file again and doesn't overwrite some files. It took me hours to figure this out but once I did everything worked without issue Nope, still broken
coffeeink Posted December 19, 2021 Posted December 19, 2021 (edited) Hm ok Search Engine doesn't find the issue at least i don't find the solution. I reinstalled SE due a lot of reasons. - installed newest SE (AE) and backported with the unoffical backporter (best of both worlds patcher) https://www.nexusmods.com/skyrimspecialedition/mods/57618 back to old SE .exe. I used Both Version simply the full backport only supports English version of the game (as far as i understood the FAQ) - set up my base setup Papyrus Utils, Skyui (Version 5.2SE) skse(Version 2.0.17) etc. everything is working fine so far. (MCM working Menus are changed etc) - installed SexLab 1.63 to match the SKSE Compiler - Start a new game and i get a greeting that SKYUi isn't installed I mean the Error message itself would be directly hinting to a missing SKyUI or wrongly installed SkyUI but everything important of SkyUI is working. MCM shows up and i even can isntall Sexlab without an error message in the log. Where is the issue? Is Sexlab somewhere wrong or is rly SkyUI broken? I tripple checked SKSE Setup, and SkyUI Setup I don't think i'm the first one with this issue. My guess is => something incomatible with the "AE features" no one wants ... /edit: Nope even with fll downgrade it has the same issue /Edit: I found the Issue. It's a mod incompatibility. Sexlab is not compatible with the mod Menu Maid (here you can hide MCM entries if you don't need htem during gameplay) https://www.nexusmods.com/skyrimspecialedition/mods/60087 This mod chancges SKI_CofigManagerInstance and this causes the Check to fail even if everything works fine For everyone who knows who wants to use "Menu maid" i add here a "patched" script file. Be aware the change was just "return true" in SkyUI check. If you replace the file and your setup is bad ... it's still bad and not funtional. Use on your own risk. i tested a little bit and both mods working fine for me. [Sexlab 1.63 not for 1.64 i do not know if there is a change in the file from 63 to 64] sslSystemConfig.pex Edited December 20, 2021 by coffeeink
KingofSkyrim Posted December 20, 2021 Posted December 20, 2021 I have Zaz animations installed along with sexlab, but for the life of me I can't figure out how get animations to play. Also can someone recommend me some basic "let's fuck" mods that trigger animations?
4nk8r Posted December 20, 2021 Posted December 20, 2021 32 minutes ago, KingofSkyrim said: I have Zaz animations installed along with sexlab, but for the life of me I can't figure out how get animations to play. Also can someone recommend me some basic "let's fuck" mods that trigger animations? Zaz is just like Sexlab. Framework only. You need other mods that use it to do stuff. If you just want raw sex animations without context, look at the "Mindless Sex" section of the below index.
4nk8r Posted December 20, 2021 Posted December 20, 2021 19 hours ago, Ghostman7nz said: Be sure to completely uninstall 1.64b from your favorite mod manager then download 1.64b again and install as usual. If you try to just reinstall without uninstalling first then the mod manager assumes you are installing the same file again and doesn't overwrite some files. It took me hours to figure this out but once I did everything worked without issue What mod manager are you using? 8 hours ago, superspyro90 said: Nope, still broken Sexlab 1.64b got an update without version change (like this shit isn't confusing enough to keep track of, right?) to correct the CTD on game start, so uninstall Sexlab 1.64b, delete the archive from your harddrive and download/install it completely once more.
KingofSkyrim Posted December 20, 2021 Posted December 20, 2021 (edited) I downloaded puppet master to use with Sex lab. It works great. But any idea on how to get pregnancy working for Being Female, or Soul Gem Oven 4 B6? I have both installed, nothing happens after sex for Being Female, and Soul Gem Oven 4 says I need race menu when I try and activate it in the mod menu, but I already have the latest version of race menu installed. Any ideas or tutorials? Edited December 20, 2021 by KingofSkyrim
zarantha Posted December 20, 2021 Posted December 20, 2021 40 minutes ago, KingofSkyrim said: I downloaded puppet master to use with Sex lab. It works great. But any idea on how to get pregnancy working for Being Female, or Soul Gem Oven 4 B6? I have both installed, nothing happens after sex for Being Female, and Soul Gem Oven 4 says I need race menu when I try and activate it in the mod menu, but I already have the latest version of race menu installed. Any ideas or tutorials? Racemenu hasn't been updated for the latest AE version yet. you'll need to wait until a working version is updated on the nexus, or support expired on his patreon to get the pre release version. your best bet is to roll back to SE using one of the methods that are littered throughout this thread.
KingofSkyrim Posted December 20, 2021 Posted December 20, 2021 (edited) Ahh ok. I'll download the unofficial roll back patch then. Thanks. Edited December 20, 2021 by KingofSkyrim
Gledania Posted December 20, 2021 Posted December 20, 2021 On 12/7/2021 at 3:55 PM, liars_paradox said: If you're super new (I don't blame you because I know some people who bought Skyrim AFTER AE came out), then you're not able to run it due to AE being incompatible with most mods here. SKSE updated to AE, but it will be a while before all the mod developers (assuming they're active) can update their mods. The creator of SexLab Framework is active, by the way, but there's no guarantee that your other mods will work when SexLab is updated. Most people in this forum turn off upgrades on Steam, but there's still a lot of people out there who haven't done that, and if you're one of them or you never had the old version, then you need to downgrade. I had this back and forth about downgrading Skyrim to an earlier version before AE. You have Steam DB, where you need to download three manifests or get this mod that does the patching for you. So everybody here don't play the anniversary edition huh ? I did so many stuff to make it work properly and just failed for almost a fucking month. I gotta see how I can downgrade it. thanks budy
Ashal Posted December 20, 2021 Author Posted December 20, 2021 This is going to come off as elitist and mean-spirited, and I apologize for that, but I need to vent right now. I can honestly say with 99% confidence, that all current versions of SexLab, LE/SE/AE, work exactly as intended. The problem isn't with sexlab, it's with your install method. PapyrusUtil isn't broken, SexLabUtil isn't broken, sslSystemConfig isn't broken, the FNIS behavior files aren't broken. The framework itself, when properly up to date, is almost 100% certainly not the real cause of your CTD despite the fact that disabling it supposedly stops it. Your install and/or overwrites are broken. Or you have a different outdated mod triggering the issue This whole AE update thing has really highlighted a few things for me. Just how many people simply don't get the basics of Skyrim modding. How shitty Vortex's dumb overwrite system is in the name of supposedly being "easy" How much people weirdly don't understand how stupidly simple and obvious MO2's overwrite system is by comparison. How much the previous 2 issues are the cause of 90% of the complaints in this thread. I honestly just can't deal with support these days when it comes to Skryim mods... People seem to be frustratingly unwilling to follow so many basic modding guidelines. It makes me want to try to make an "idiots video guide to installing sexlab" but I'm so sure it'd be mostly ignored at this point that I don't think it'd be worth the effort. 8
swmas Posted December 20, 2021 Posted December 20, 2021 48 minutes ago, Ashal said: This is going to come off as elitist and mean-spirited, and I apologize for that, but I need to vent right now. I can honestly say with 99% confidence, that all current versions of SexLab, LE/SE/AE, work exactly as intended. The problem isn't with sexlab, it's with your install method. PapyrusUtil isn't broken, SexLabUtil isn't broken, sslSystemConfig isn't broken, the FNIS behavior files aren't broken. The framework itself, when properly up to date, is almost 100% certainly not the real cause of your CTD despite the fact that disabling it supposedly stops it. Your install and/or overwrites are broken. Or you have a different outdated mod triggering the issue This whole AE update thing has really highlighted a few things for me. Just how many people simply don't get the basics of Skyrim modding. How shitty Vortex's dumb overwrite system is in the name of supposedly being "easy" How much people weirdly don't understand how stupidly simple and obvious MO2's overwrite system is by comparison. How much the previous 2 issues are the cause of 90% of the complaints in this thread. I honestly just can't deal with support these days when it comes to Skryim mods... People seem to be frustratingly unwilling to follow so many basic modding guidelines. It makes me want to try to make an "idiots video guide to installing sexlab" but I'm so sure it'd be mostly ignored at this point that I don't think it'd be worth the effort. Is your fault for rushing to move SL to AE. What's the point of a working SL if there are no mods to make use of it? Blaming old mods for not working with your framework is like Apple not supporting old software with their OS. Also the Vortex fiasco is just the audience you courted, the people that tend to rush the AE update are not MO2 users, they know better.
Vyxenne Posted December 20, 2021 Posted December 20, 2021 (edited) 59 minutes ago, swmas said: Also the Vortex fiasco is just the audience you courted What "Vortex fiasco?" Please describe specifically where/when this is posted so I can educate myself. Also, your inference that Vortex users are less intelligent than MO2 users is ignorant and wrong. And also, a textbook case of elitism. While I disagree with his assessment of Vortex's "overwrite system" (like MO2, Vortex does not overwrite anything- it facilitates users resolving conflicts by setting priorities within its virtual installation on a whole-mod or individual file basis and is quite effective and intuitive to use) I have followed this whole AE fiasco fairly closely both here and on the Nexus, and I fail to see how Ashal has "courted" any particular audience. He (and OsmelMC) have diligently kept SL updated and working despite Beth's incessant game-breaking updates. The fact that many SL-dependent mods have not yet been updated to work with the new game versions, and/or SKSE64 and/or SexLab Framework is hardly his fault- that's like blaming Bill Gates because most Windows 3.1 apps won't run on Windows 11 machines. And neither is it Ashal's fault that there are (apparently) hordes of noobs who know how to cry and ask for help but don't bother reading or learning anything about Bethesda Game Modding in general and SexLab modding in particular. This has been true since Fallout 3/Oblivion days, and will undoubtedly still be true 50 years from now. There is simply no legitimate way to make this PEBCAK Pandemic Ashal's fault. Edited December 20, 2021 by Vyxenne Because she hadn't used Comic Sans MS font in several days 2
Ashal Posted December 20, 2021 Author Posted December 20, 2021 46 minutes ago, swmas said: Is your fault for rushing to move SL to AE. What's the point of a working SL if there are no mods to make use of it? Blaming old mods for not working with your framework is like Apple not supporting old software with their OS. Also the Vortex fiasco is just the audience you courted, the people that tend to rush the AE update are not MO2 users, they know better. In what way did I rush to AE? AE and SE were both supported day 1 of the update to SL. Was I supposed to completely ignore AE and not support it just to spite the people who updated? An update most didn't specifically opt for and got automatically. The SE version is plainly available as well for those that didn't update. Not releasing an AE version would've just resulted in more complaints as people questioned why the SE build didn't work. And I'm not blaming old mods. I'm blaming peoples inability to recognize and troubleshoot basic overwrite/load order issues that has been around and explained for years now. 3
swmas Posted December 20, 2021 Posted December 20, 2021 21 minutes ago, Vyxenne said: What "Vortex fiasco?" Please describe specifically where/when this is posted so I can educate myself. Also, your inference that Vortex users are less intelligent than MO2 users is ignorant and wrong. And also, a textbook case of elitism. While I disagree with his assessment of Vortex's "overwrite system" (like MO2, Vortex does not overwrite anything- it facilitates users resolving conflicts by setting priorities within its virtual installation on a whole-mod or individual file basis and is quite effective and intuitive to use) I have followed this whole AE fiasco fairly closely both here and on the Nexus, and I fail to see how Ashal has "courted" any particular audience. He (and OsmelMC) have diligently kept SL updated and working despite Beth's incessant game-breaking updates. The fact that many SL-dependent mods have not yet been updated to work with the new game versions, and/or SKSE64 and/or SexLab framework is hardly his fault- that's like blaming Bill Gates because some Windows 3.1 apps won't run on Windows 11 machines. And neither is it Ashal's fault that there are (apparently) hordes of noobs who know how to cry and ask for help but don't bother reading or learning anything about Bethesda Game Modding in general and SexLab modding in particular. This has been true since Fallout 3/Oblivion days, and will undoubtedly still be true 50 years from now. There is simply no legitimate way to make this PEBCAK pandemic Ashal's fault. Vortex users are dumber. 1
swmas Posted December 20, 2021 Posted December 20, 2021 21 minutes ago, Ashal said: In what way did I rush to AE? AE and SE were both supported day 1 of the update to SL. Was I supposed to completely ignore AE and not support it just to spite the people who updated? An update most didn't specifically opt for and got automatically. The SE version is plainly available as well for those that didn't update. Not releasing an AE version would've just resulted in more complaints as people questioned why the SE build didn't work. And I'm not blaming old mods. I'm blaming peoples inability to recognize and troubleshoot basic overwrite/load order issues that has been around and explained for years now. Exactly you should have not updated so soon if you didn't want this complication now deal with the consequences.
Ashal Posted December 20, 2021 Author Posted December 20, 2021 1 minute ago, swmas said: Exactly you should have not updated so soon if you didn't want this complication now deal with the consequences. You completely missed my point. 3 minutes ago, swmas said: Vortex users are dumber. This, I'll agree with. 3
tasairis Posted December 20, 2021 Posted December 20, 2021 (edited) 1 hour ago, swmas said: Is your fault for rushing to move SL to AE. What's the point of a working SL if there are no mods to make use of it? Blaming old mods for not working with your framework is like Apple not supporting old software with their OS. Also the Vortex fiasco is just the audience you courted, the people that tend to rush the AE update are not MO2 users, they know better. The upgrade problems aren't exclusively a SexLab thing: they're happening in the CBPC and DD threads, and r/skyrimmods is inundated with folks asking why stuff doesn't work. If you want reasons why this AE upgrade thing is hurting so much, I've got four - and none of them are SexLab's fault. 1. The AE update came nearly two years after the last update. Everyone who joined Skyrim/LL in that time had no idea about these breaking updates, and they're going to be the ones asking/complaining most about this. 2. Even after two years, it's still an update. The process this time has been the same as it's been every other time before: wait for SKSE to update, wait for dependencies like Address Library and PapyrusUtil, wait for frameworks like SexLab and DD, then finally wait for individual mods. That's a bother for everyone. 3. AE hasn't really even been just the one update. We've had three updates to Skyrim in the last ~month, including AE, and we're going to receive a fourth soon (I was actually expecting it today). That's a lot of churn and people are tired of it, and when people are tired they bitch, and if they can't bitch at the people actually responsible then they're going to bitch at whoever is in range of their voice. 4. The stupid "Anniversary Edition" branding. It's a good marketing move on Bethesda's part but it's a fucking terrible thing for the modding community to have to live through, because now we have newbies asking whether mods are compatible with SE or AE, and as much as we'd like to answer "yes because they're the same fucking game", SKSE makes that not entirely true. There's a ton of problems going on and we're all affected by it and yeah, it sucks. But SexLab trying to support AE sooner rather than later is not one of them. Edited December 20, 2021 by tasairis 3
Ashal Posted December 20, 2021 Author Posted December 20, 2021 9 minutes ago, tasairis said: 4. The stupid "Anniversary Edition" branding. It's a good marketing move on Bethesda's part but it's a fucking terrible thing for the modding community to have to live through, because now we have newbies asking whether mods are compatible with SE or AE, and as much as we'd like to answer "yes because they're the same fucking game", SKSE makes that not entirely true. This has been my biggest annoyance. There's not a small number of people who seem to think they are still using "SE" despite updating to Skyrim v1.6.x+ just because they haven't bought the AE content upgrade on Steam. We should've just kept calling it all SE and ignored the AE dlc distinction. 4
MadMansGun Posted December 20, 2021 Posted December 20, 2021 2 hours ago, Ashal said: It makes me want to try to make an "idiots video guide to installing sexlab" but I'm so sure it'd be mostly ignored at this point that I don't think it'd be worth the effort. we already have a few of those around, and yes sadly they are. 1
zarantha Posted December 20, 2021 Posted December 20, 2021 2 hours ago, swmas said: Is your fault for rushing to move SL to AE. What's the point of a working SL if there are no mods to make use of it? On the contrary, it is one of the core mods that MUST be updated first, as soon as feasible, or the mods dependent on it can't update. The problem is all the new users who don't understand how the updates break things and don't even know what version they are on. Or, as Ashal said, understand even the basics of troubleshooting and how to put together their own mod list. 1
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