5ansgaming Posted May 9, 2021 Posted May 9, 2021 Ive had an issue with this text popping up every 1-2 sec. Looking through other posts, someone said its caused by old versions of the mod that havent been cleared out, I have downloaded this mod only once, the most recent version and never have updated it. Still, going through the listed process of removing the old version, the constant messages persisted. I would like to try to remove the mod notifications, or at least replace them with something less intrusive like a spacebar or a"." but Im a complete moron when it comes to technology, code and everything connected to that. Does anyone have any tips on removing these messages, since turning off the mod wont launch the game because of the mods relying on it.
Sgt. Marge Posted May 9, 2021 Posted May 9, 2021 Which version of Sexlab Aroused are you using? Is it the latest SexLab Aroused eXtended 29.0 on Legendary Edition? or are you using the older mod, "Sexlab Aroused Redux"? I think there might be 3 different mods called Sexlab Aroused. I would highly recommend the newest one that I linked, "eXtended" if you are not already using that.
5ansgaming Posted May 9, 2021 Author Posted May 9, 2021 Yes, Im using the one you linked, (SLAX - 29). I have also tried the one called "fishburger" from the publisher, and "SexLab Aroused Modular Edition 0.5". The messages pop up on every one of them. I dont think its the files fault. more likely Im doing something wrong, but I would much rather prefer to disable notifications from the mod. Is there any way or even a different mod to controll and disable notifications?
Sgt. Marge Posted May 9, 2021 Posted May 9, 2021 You'd have to figure out which script has that as a "debug" message and comment it out with a semicolon and recompile the script. I don't think I would recommend doing that, I'm not sure if that would have implications later on down the line. (could be spamming papyrus at the least, could cause instability?) I wouldn't use any of the older versions other than the one I linked. Too many mods rely on arousal based mechanics so you may as well use the latest one, just in case. Also, SLAX is pretty reliable in my experience. I think I had the same problem as you with Redux, pretty sure that's what prompted me to troubleshoot and found SLAX. Is the arousal mod actually working? Have you tested to see if your characters and npc's arousal is changing? is it being affected by sex etc.? Because if it isn't working, then there's no reason to bother with editing out the message in the script. Also, I would recommend posting your issue on the SLAX support page as well (Press the Get Help button on the mod's download page) You are likely to get people helping that have way more experience with troubleshooting Sexlab Arousal that way.
Lupine00 Posted May 9, 2021 Posted May 9, 2021 2 hours ago, 5ansgaming said: Ive had an issue with this text popping up every 1-2 sec Sorry, can you clarify what text is popping up? If it's something about an old PapyrusUtils version, that's SLS complaining about SexLab itself, and you just need to make sure that PapyrusUtils 3.3 is overwriting SexLab's version (or any other version that is dragged in from an old mod). It would be nothing to do with SLA* at all.
Sgt. Marge Posted May 10, 2021 Posted May 10, 2021 1 hour ago, Lupine00 said: Sorry, can you clarify what text is popping up? If it's something about an old PapyrusUtils version, that's SLS complaining about SexLab itself, and you just need to make sure that PapyrusUtils 3.3 is overwriting SexLab's version (or any other version that is dragged in from an old mod). It would be nothing to do with SLA* at all. The message they are getting repeatedly (per the OP's title) is "Sexlab Aroused is ready to use"
Lupine00 Posted May 10, 2021 Posted May 10, 2021 32 minutes ago, Marg597 said: The message they are getting repeatedly (per the OP's title) is "Sexlab Aroused is ready to use" Ah... They don't say what they (may have) updated from, and whether it's a new game or an old game with an update. ... or what mod-manager they're using, which is probably the root cause of this issue. From what I can see, SLAX replaced the popup with a Notification, so you'd never get popups in SLAX code even if there was some bug that made it appear repeatedly. Also, SLAX doesn't retrigger that mechanic unless you open the MCM, so if you aren't opening the MCM it can't happen there. But if this incompletely reported issue is seen when updating from SLAR to SLAX, I'd like to know It might be something else entirely. Maybe they were running the Babo version? Maybe they updated from original SLA to SLAR first? Hard to know. Here's my best guess... It's a new game and... They installed SLAX using NMM over the top of SLAR. They didn't let it overwrite completely, and have a frankenslar. (Possibly they have also done manual mod installs on top of NMM, which breaks it). They should uninstall both mods in NMM, then reinstall SLAR or SLAX, allowing all overwrites. They should then manually check that all final installed .pex and esp files match the source zip. Second guess... They use MO, left pane ordering is messed up: either they have a duplicate copy of an old SLA still overwriting, or they have both mods enabled and in the wrong order. Third guess... They use Vortex and have the Vortex equivalent of the issues noted above. Or... It's an old game and... Their game is a train-wreck of detached objects, log filled with None property warnings and stack dump warnings. In this case, SLAX literally has no quest objects and will never succeed in an update.
5ansgaming Posted May 12, 2021 Author Posted May 12, 2021 I managed to fix it. I used "slax" as you recomended, deleted all the mods and installed them one by one again. All while turning the game on and saving after each mod. The messages stopped coming, but it continued on the save file. Luckily a different lvl 1 save worked fine. Thank you for help and the time trying to explain simple stuff to me. I would have never worked it out myself
Recommended Posts
Archived
This topic is now archived and is closed to further replies.