Sexlab Aroused Redux December 05 2016

[Xper000]

Waxen gave the answer, it's a vanilla bug not any one particular mod, or combination thereof.

 

And it can be easily fixed, when you make your last save of the play session, type in coc qasmoke in the console, and save again in there.

That save will load every time all the time, once it loads, then simply load you last game save from there, which will now load every time all the time, and continue merrily forward.

[pihwht]

Waxen gave the answer, it's a vanilla bug not any one particular mod, or combination thereof.

 

And it can be easily fixed, when you make your last save of the play session, type in coc qasmoke in the console, and save again in there.

That save will load every time all the time, once it loads, then simply load you last game save from there, which will now load every time all the time, and continue merrily forward.

 

I'll try that. Thanks. I've just been using an early save just ouside Helgen.

[Xper000]

I am kind of ashamed to admit how long it took me to figure that little trick out.:}

 

It also has the added advantage of not having to scroll down for an hour looking for that one save I knew worked.:}

[pihwht]

I am kind of ashamed to admit how long it took me to figure that little trick out.:}

 

It also has the added advantage of not having to scroll down for an hour looking for that one save I knew worked.:}

 

Plus, the save that worked sometimes quits working. Someone here said that eventually they become corrupted.

[Jimbodan]

its a problem with the engine, it can only load so much before it breaks, which is why early saves and saves that aren't heavily modded will usually load while larger saves and heavily modded saves usually crash. 

 

I get around this by doing coc qasmoke at the main menu screen then loading my most recent save. This will always work to load uncorrupted saves and you don't ever have to actually save in the qasmoke area or make a "safe save". If however your save is broken and won't load even doing this you can try the save cleaner (think its on nexus) but it will only help if your problem is a script.

[fishburger67]

I hate this kind of "Skyrim mysteries".

But still, it's strange that it happens only with SA activated and never when it's not. If you look at the Papyrus log, it's always when this particular mod is loading. It has to be something.

 

 

 

I hate this kind of "Skyrim mysteries".

But still, it's strange that it happens only with SA activated and never when it's not. If you look at the Papyrus log, it's always when this particular mod is loading. It has to be something.

 

I think it may sometimes  have to do with active scripts and find I have the best luck loading the autosaves first. It doesn't happen all the time when I forget that it is "going" to happen.

 

 

 

 

Coincidentally, the same thing just happened to me.  Like plopyck, the last line of my papyrus log said that SAR was initializing.  Took me 5 tries to load the save game without crashing.  I never for a minute even considered uninstalling SAR

 

 

 

Coincidentally, the same thing just happened to me.  Like plopyck, the last line of my papyrus log said that SAR was initializing.  Took me 5 tries to load the save game without crashing.  I never for a minute even considered uninstalling SAR

 

Same here. Once I got used to remembering to load a "safe" save, it wasn't a very large annoyance.

 

 

 

Still, would be nice if it could be fixed . At least I'm not the only one with this problem. Nice to know

This is not a SAR bug, or a bug with most any mod.  I screwed with this AT GREAT LENGTH over several days and on three machines.  I have saves with out SAR or vanilla aroused and they still crash.  IT CANNOT BE FIXED as there is nothing to fix.

 

If you want to fix it, the only sure way I have found it beef up your machine, get a 3gig graphics card and load one of the enbseries mods.  That fixed it for me 100% of the time.

[fishburger67]

its a problem with the engine, it can only load so much before it breaks, which is why early saves and saves that aren't heavily modded will usually load while larger saves and heavily modded saves usually crash. 

 

I get around this by doing coc qasmoke at the main menu screen then loading my most recent save. This will always work to load uncorrupted saves and you don't ever have to actually save in the qasmoke area or make a "safe save". If however your save is broken and won't load even doing this you can try the save cleaner (think its on nexus) but it will only help if your problem is a script.

 

This is excellent advice.  Its called savetool.exe and it is dead simple to use and will fix MOST CTD issues that are related to uninstalling mods.

 

If you want to avoid CTDs almost completely, figure out what mods you want to use forever and never change or upgrade, and then start a new game and play it.  If you want to uninstall a mod, start a new game afterwards.

 

This advice sucks in most circumstances as most people don't want to start from scratch. 

 

Get in the habit of making a papyrus log and checking it from time to time (but don't leave logging turned on always and this adds some load).

 

Load a save, wait for it to stablize, then exit and have a look at your log.  If it has more that a couple of pages, fix your problem, usually with savetool or another save game editor and more work.

 

YOUR CTD issues are in your save games, not SAR, vanilla aroused etc.  The issues vanilla aroused are when you are travelling around in populated areas, not when loading a save (although SAR will diminish your save game load CTDs by about 20% based on my testing).

[fishburger67]

 

I am kind of ashamed to admit how long it took me to figure that little trick out.:}

 

It also has the added advantage of not having to scroll down for an hour looking for that one save I knew worked.:}

 

Plus, the save that worked sometimes quits working. Someone here said that eventually they become corrupted.

 

 

Make a papyrus log and review it.  It will almost certainly point to your problem which will also almost certainly not be SAR.

 

You probably uninstalled a mod and there are still scripts running even though you uninstalled the mod, maybe months ago.

[plopyck]

Well, I did a new game anyway and it seems that the problem is solved. But I'll remember the trick with the secret room.

 

However I have another minor problem, it seems so that the "Arousal" display that I get with the hotkey is always completely different that the value display in the "puppet master" windows. I can't figure out why, and I don't know which value is the good one. Any idea ?

[fishburger67]

Well, I did a new game anyway and it seems that the problem is solved. But I'll remember the trick with the secret room.

 

However I have another minor problem, it seems so that the "Arousal" display that I get with the hotkey is always completely different that the value display in the "puppet master" windows. I can't figure out why, and I don't know which value is the good one. Any idea ?

 

The hot key and the puppet master MCM display are showing different values.  The N key shows arousal.  The puppet master is showing exposure.  Check the old Aroused home page as well as a rather lengthy description I did on this forum back a few pages to understand the difference.

[fishburger67]

Uploaded new Version 16

 

This version fixes a minor bug where if an cell scan was requested as a result of sex and there was already a cell scan going on, your log would be peppered with errors.

Fixed a minor grammatical error in the English translation file.

[BushJr]

qasmoke and working saves? OMG, guys are you serious?

 

It's ram. Use enb or enbooster it's an old stuff, idk, maybe already year old or maybe 2. I didn't even realise somebody still have those problems.

[PubliusNV]

 

I hate this kind of "Skyrim mysteries".

But still, it's strange that it happens only with SA activated and never when it's not. If you look at the Papyrus log, it's always when this particular mod is loading. It has to be something.

 

 

 

I hate this kind of "Skyrim mysteries".

But still, it's strange that it happens only with SA activated and never when it's not. If you look at the Papyrus log, it's always when this particular mod is loading. It has to be something.

 

I think it may sometimes  have to do with active scripts and find I have the best luck loading the autosaves first. It doesn't happen all the time when I forget that it is "going" to happen.

 

 

 

 

Coincidentally, the same thing just happened to me.  Like plopyck, the last line of my papyrus log said that SAR was initializing.  Took me 5 tries to load the save game without crashing.  I never for a minute even considered uninstalling SAR

 

 

 

Coincidentally, the same thing just happened to me.  Like plopyck, the last line of my papyrus log said that SAR was initializing.  Took me 5 tries to load the save game without crashing.  I never for a minute even considered uninstalling SAR

 

Same here. Once I got used to remembering to load a "safe" save, it wasn't a very large annoyance.

 

 

 

Still, would be nice if it could be fixed . At least I'm not the only one with this problem. Nice to know

This is not a SAR bug, or a bug with most any mod.  I screwed with this AT GREAT LENGTH over several days and on three machines.  I have saves with out SAR or vanilla aroused and they still crash.  IT CANNOT BE FIXED as there is nothing to fix.

 

If you want to fix it, the only sure way I have found it beef up your machine, get a 3gig graphics card and load one of the enbseries mods.  That fixed it for me 100% of the time.

 

 

I wasn't trying to blame SAR in any way, I've had the problem long before I installed SAR or any LL mod.  BTW, I've got 8G RAM, 4G video RAM, and I'm using an ENB and it still crashes, so even beefing up your machine won't necessarily get rid of it.  It's just Skyrim.

 

 

[fishburger67]

I wasn't trying to blame SAR in any way, I've had the problem long before I installed SAR or any LL mod.  BTW, I've got 8G RAM, 4G video RAM, and I'm using an ENB and it still crashes, so even beefing up your machine won't necessarily get rid of it.  It's just Skyrim.

 

Gads, my assumption was wrong.  In my testing, I installed a lightweight enb and ALL my CTDs went away, but I only got like 16fps.  So, I bought a great big video card, but have yet to install it.

 

This might just be something like the vsync issue.  If you have a fast machine with vsync turned off, you get all these things banging around.  That is fixed by throttling with vsync.

 

Who knows, I have read hundreds to thousands of posts on this and no one has an answer.

[fishburger67]

qasmoke and working saves? OMG, guys are you serious?

 

It's ram. Use enb or enbooster it's an old stuff, idk, maybe already year old or maybe 2. I didn't even realise somebody still have those problems.

 

I have 16megs of ram.  I even installed a ram profiler.  I installed enboost and did EVERYTHING suggested and I have made absolutely no progress.  I still get a CTD on load 1 of every 3 or 4 times, but only on one machine.  The other mostly runs fine and strangely, both are close to identical.

[fizzybutt]

When I crash on load (hasn't happened in a long while), my memory doesn't even get close to it. After I made sure the memory block patch was working, I discovered that scripts would get all tangled when they were starting up sometimes; and preloading into qasmoke before loading my save would iron out the kinks so to speak.

[Jimbodan]

Uploaded new Version 16

 

This version fixes a minor bug where if an cell scan was requested as a result of sex and there was already a cell scan going on, your log would be peppered with errors.

Fixed a minor grammatical error in the English translation file.

 

I was hoping this would fix the problem i was having but i'm still getting the same thing, having sex prevents any more scans. Doing some testing it seems that having sex and force ending it before a scan tries to happen will keep the mod working as intended however once i see this line in the log

 

"[slaMainScr <sla_Main (19042D62)>]:Aroused scan skipped because sexlab is animating."

 

i never see anything else arousal related save for the increases in arousal from viewing sex.

 

It bothers me that noone else is having this problem or noticing that they do. The next thing i'm going to try is uninstalling a lot of my other mods to rule out compatability and script lag issues.

 

update: Well i tried a new game with the bare minimum of sexlab mods installed and i still have the problem. I don't know what else i can try but hope you can come up with a magical fix.

[fishburger67]

 

Uploaded new Version 16

 

This version fixes a minor bug where if an cell scan was requested as a result of sex and there was already a cell scan going on, your log would be peppered with errors.

Fixed a minor grammatical error in the English translation file.

 

I was hoping this would fix the problem i was having but i'm still getting the same thing, having sex prevents any more scans. Doing some testing it seems that having sex and force ending it before a scan tries to happen will keep the mod working as intended however once i see this line in the log

 

"[slaMainScr <sla_Main (19042D62)>]:Aroused scan skipped because sexlab is animating."

 

i never see anything else arousal related save for the increases in arousal from viewing sex.

 

It bothers me that noone else is having this problem or noticing that they do. The next thing i'm going to try is uninstalling a lot of my other mods to rule out compatability and script lag issues.

 

update: Well i tried a new game with the bare minimum of sexlab mods installed and i still have the problem. I don't know what else i can try but hope you can come up with a magical fix.

 

I just checked this code again as a result of your previous post, and right before the trace statement you see is a statement that resets the scan timer.  Are you giving it enough time?  Here is what I did to test this, I set the scan time to ten seconds,  waited a while to make sure I could see several scans in the log. had sex, waited 15 seconds, had sex again and waited another 15 seconds and then looked at my log.  It all looked just hunky dorry.   Give it a test as above (15 second scan timer), have sex, wait 30 seconds, have sex, wait 30 seconds, then post the papyrus log if it doesn't look right.

 

[Jimbodan]

 

 

Uploaded new Version 16

 

This version fixes a minor bug where if an cell scan was requested as a result of sex and there was already a cell scan going on, your log would be peppered with errors.

Fixed a minor grammatical error in the English translation file.

 

I was hoping this would fix the problem i was having but i'm still getting the same thing, having sex prevents any more scans. Doing some testing it seems that having sex and force ending it before a scan tries to happen will keep the mod working as intended however once i see this line in the log

 

"[slaMainScr <sla_Main (19042D62)>]:Aroused scan skipped because sexlab is animating."

 

i never see anything else arousal related save for the increases in arousal from viewing sex.

 

It bothers me that noone else is having this problem or noticing that they do. The next thing i'm going to try is uninstalling a lot of my other mods to rule out compatability and script lag issues.

 

update: Well i tried a new game with the bare minimum of sexlab mods installed and i still have the problem. I don't know what else i can try but hope you can come up with a magical fix.

 

I just checked this code again as a result of your previous post, and right before the trace statement you see is a statement that resets the scan timer.  Are you giving it enough time?  Here is what I did to test this, I set the scan time to ten seconds,  waited a while to make sure I could see several scans in the log. had sex, waited 15 seconds, had sex again and waited another 15 seconds and then looked at my log.  It all looked just hunky dorry.   Give it a test as above (15 second scan timer), have sex, wait 30 seconds, have sex, wait 30 seconds, then post the papyrus log if it doesn't look right.

 

 

Gave your test a try. I've attached the relevant part of the log. You can see the scan working in the beginning every 15 seconds.  Then i initiated the first sex act (just had someone masturbate). When that ended i waited about a minute then did the same thing again. After the second act finished i waited about 2 minutes then did another this time with 2 people and then waited about 2 minutes after the last one ended. You can see that its simply not doing any scans after the first act.

papyrus arousal test log.txt

[Uncle64]

One question.

Is it possible to have one option that animals dont get aroused?

[fishburger67]

One question.

Is it possible to have one option that animals dont get aroused?

 

I agree that this would be nice.  I'll add it to my feature request list.

[fishburger67]

 

 

 

Uploaded new Version 16

 

This version fixes a minor bug where if an cell scan was requested as a result of sex and there was already a cell scan going on, your log would be peppered with errors.

Fixed a minor grammatical error in the English translation file.

 

I was hoping this would fix the problem i was having but i'm still getting the same thing, having sex prevents any more scans. Doing some testing it seems that having sex and force ending it before a scan tries to happen will keep the mod working as intended however once i see this line in the log

 

"[slaMainScr <sla_Main (19042D62)>]:Aroused scan skipped because sexlab is animating."

 

i never see anything else arousal related save for the increases in arousal from viewing sex.

 

It bothers me that noone else is having this problem or noticing that they do. The next thing i'm going to try is uninstalling a lot of my other mods to rule out compatability and script lag issues.

 

update: Well i tried a new game with the bare minimum of sexlab mods installed and i still have the problem. I don't know what else i can try but hope you can come up with a magical fix.

 

I just checked this code again as a result of your previous post, and right before the trace statement you see is a statement that resets the scan timer.  Are you giving it enough time?  Here is what I did to test this, I set the scan time to ten seconds,  waited a while to make sure I could see several scans in the log. had sex, waited 15 seconds, had sex again and waited another 15 seconds and then looked at my log.  It all looked just hunky dorry.   Give it a test as above (15 second scan timer), have sex, wait 30 seconds, have sex, wait 30 seconds, then post the papyrus log if it doesn't look right.

 

 

Gave your test a try. I've attached the relevant part of the log. You can see the scan working in the beginning every 15 seconds.  Then i initiated the first sex act (just had someone masturbate). When that ended i waited about a minute then did the same thing again. After the second act finished i waited about 2 minutes then did another this time with 2 people and then waited about 2 minutes after the last one ended. You can see that its simply not doing any scans after the first act.

 

Thanks for taking the time to do this.  Will have a look shortly.

 

[fishburger67]

 

 

 

 

Uploaded new Version 16

 

This version fixes a minor bug where if an cell scan was requested as a result of sex and there was already a cell scan going on, your log would be peppered with errors.

Fixed a minor grammatical error in the English translation file.

 

I was hoping this would fix the problem i was having but i'm still getting the same thing, having sex prevents any more scans. Doing some testing it seems that having sex and force ending it before a scan tries to happen will keep the mod working as intended however once i see this line in the log

 

"[slaMainScr <sla_Main (19042D62)>]:Aroused scan skipped because sexlab is animating."

 

i never see anything else arousal related save for the increases in arousal from viewing sex.

 

It bothers me that noone else is having this problem or noticing that they do. The next thing i'm going to try is uninstalling a lot of my other mods to rule out compatability and script lag issues.

 

update: Well i tried a new game with the bare minimum of sexlab mods installed and i still have the problem. I don't know what else i can try but hope you can come up with a magical fix.

 

I just checked this code again as a result of your previous post, and right before the trace statement you see is a statement that resets the scan timer.  Are you giving it enough time?  Here is what I did to test this, I set the scan time to ten seconds,  waited a while to make sure I could see several scans in the log. had sex, waited 15 seconds, had sex again and waited another 15 seconds and then looked at my log.  It all looked just hunky dorry.   Give it a test as above (15 second scan timer), have sex, wait 30 seconds, have sex, wait 30 seconds, then post the papyrus log if it doesn't look right.

 

 

Gave your test a try. I've attached the relevant part of the log. You can see the scan working in the beginning every 15 seconds.  Then i initiated the first sex act (just had someone masturbate). When that ended i waited about a minute then did the same thing again. After the second act finished i waited about 2 minutes then did another this time with 2 people and then waited about 2 minutes after the last one ended. You can see that its simply not doing any scans after the first act.

 

 

This log does not look at all right.  You should have log lines produced by debug.trace(self+"Unlocking scanner").  Are you sure you loaded the new version?  If so, I'll put out another version that writes the version number in the log file.

 

[Jimbodan]

 

 

 

 

 

Uploaded new Version 16

 

This version fixes a minor bug where if an cell scan was requested as a result of sex and there was already a cell scan going on, your log would be peppered with errors.

Fixed a minor grammatical error in the English translation file.

 

I was hoping this would fix the problem i was having but i'm still getting the same thing, having sex prevents any more scans. Doing some testing it seems that having sex and force ending it before a scan tries to happen will keep the mod working as intended however once i see this line in the log

 

"[slaMainScr <sla_Main (19042D62)>]:Aroused scan skipped because sexlab is animating."

 

i never see anything else arousal related save for the increases in arousal from viewing sex.

 

It bothers me that noone else is having this problem or noticing that they do. The next thing i'm going to try is uninstalling a lot of my other mods to rule out compatability and script lag issues.

 

update: Well i tried a new game with the bare minimum of sexlab mods installed and i still have the problem. I don't know what else i can try but hope you can come up with a magical fix.

 

I just checked this code again as a result of your previous post, and right before the trace statement you see is a statement that resets the scan timer.  Are you giving it enough time?  Here is what I did to test this, I set the scan time to ten seconds,  waited a while to make sure I could see several scans in the log. had sex, waited 15 seconds, had sex again and waited another 15 seconds and then looked at my log.  It all looked just hunky dorry.   Give it a test as above (15 second scan timer), have sex, wait 30 seconds, have sex, wait 30 seconds, then post the papyrus log if it doesn't look right.

 

 

Gave your test a try. I've attached the relevant part of the log. You can see the scan working in the beginning every 15 seconds.  Then i initiated the first sex act (just had someone masturbate). When that ended i waited about a minute then did the same thing again. After the second act finished i waited about 2 minutes then did another this time with 2 people and then waited about 2 minutes after the last one ended. You can see that its simply not doing any scans after the first act.

 

 

This log does not look at all right.  You should have log lines produced by debug.trace(self+"Unlocking scanner").  Are you sure you loaded the new version?  If so, I'll put out another version that writes the version number in the log file.

 

 

Aha, you gave me the clue to fix it. After you said the log didn't look right i figured it must have been an installation issue. After looking i realized that wrye bash hadn't recognized your Sexlabaroused.bsl file and skipped its installation. So i then manually installed the file however skyrim itself didn't recognize it either. Finally i decided to download the loose file version and install it and voila it works. Thanks for putting up with me and helping to solve this >.<

 

The odd thing is that i have other .bsl files that work and install just fine i don't know why yours is special.

[fishburger67]

Gads, wished you'd told me earlier.  I just updated it again to put the version number in the log file.  But, then again, maybe the bsa file is not right, maybe I better check that.

 

BTW: the bsl file should never be used.  It just contains the absolute path to the files enclosed which are meaningless on your machine (all my development work is on a J: drive which almost certainly does not exist on most machines.)  I had no idea that an istaller would actually use it.  I use NMM, never got into the fancy stuff.  I have the .bsa and .bsl files installed and skyrim likes them just fine, except that skyrim does not use the .bsl as far as I know.