Jump to content

Recommended Posts

Posted

 

 

 

There you go  :)

 

 

There are tons of problems in your papyrus, and I can see that VioLens is consuming a huge amount of memory.

And SSX starts the init before VioLens ends its own. And the available memory is exhausted.

Posted

Hmm what could Violens do? It's the starting place for alternate start. The memory is probably beacuse i was just running skyrim on one monitor while on the second one was browser and stuff. I just ran it for papyrus.

Eh iam gonna do some cleaning and report later. If its memory problem then it is probably going to fix itself.

Thanks :)

Posted

Hmm what could Violens do? It's the starting place for alternate start. The memory is probably beacuse i was just running skyrim on one monitor while on the second one was browser and stuff. I just ran it for papyrus.

 

Eh iam gonna do some cleaning and report later. If its memory problem then it is probably going to fix itself.

Thanks :)

 

Be aware that is not the Computer memory, but the memory allocated to the Papyrus VM.

And the max usually is 768Mb.

 

If you look at your papyrus, you will see that a bunch of mods are doing nasty stuff at init.

And nasty stuff, usually, == memory leaks.

Posted

 

Hmm what could Violens do? It's the starting place for alternate start. The memory is probably beacuse i was just running skyrim on one monitor while on the second one was browser and stuff. I just ran it for papyrus.

 

Eh iam gonna do some cleaning and report later. If its memory problem then it is probably going to fix itself.

Thanks :)

 

Be aware that is not the Computer memory, but the memory allocated to the Papyrus VM.

And the max usually is 768Mb.

 

If you look at your papyrus, you will see that a bunch of mods are doing nasty stuff at init.

And nasty stuff, usually, == memory leaks.

 

Good to know :)

 

I just made stable load order wasn't doing anything else really. Was trying to eliminate crashes etc. (memory, crash fixes, enbboost settings and looking for best outcome for me)

Now iam just fixing errors from papyrus (like requiem one for mining ore). No idea if size of log matters but iam at 150kb from 300kb (4 min in each seasion).

Posted

never having used previous versions - does it take a while for stuff to happen? i'm noticing a pretty significant time gap from entering a cell where a rule is set and something happening (the parameters for initiation are met). and if i have the dialogue options on then after the dialogue finishes it take a long time (20+ seconds?) before an event is initiated.

 

just wanted to know if that was normal or if i have some issues.

Posted

hmm all my drop down menus are empty. and i get

 

 

 

[08/29/2016 - 05:14:04PM] error: Cannot access an element of a None array
stack:
    [ssxm (E0038B54)].ssxMCM.generateDebug() - "ssxMCM.psc" Line ?
    [ssxm (E0038B54)].ssxMCM.OnPageReset() - "ssxMCM.psc" Line ?
    [ssxm (E0038B54)].ssxMCM.SetPage() - "SKI_ConfigBase.psc" Line ?

 

 

 

gonna see if starting the game without it then enableing it after sexlab started will fix it.

Posted

never having used previous versions - does it take a while for stuff to happen? i'm noticing a pretty significant time gap from entering a cell where a rule is set and something happening (the parameters for initiation are met). and if i have the dialogue options on then after the dialogue finishes it take a long time (20+ seconds?) before an event is initiated.

 

just wanted to know if that was normal or if i have some issues.

 

There is an option to decide if the rules should start right away or a first wait cycle has to be wait.

Try to switch it to: start right away.

hmm all my drop down menus are empty. and i get

 

 

 

[08/29/2016 - 05:14:04PM] error: Cannot access an element of a None array

stack:

    [ssxm (E0038B54)].ssxMCM.generateDebug() - "ssxMCM.psc" Line ?

    [ssxm (E0038B54)].ssxMCM.OnPageReset() - "ssxMCM.psc" Line ?

    [ssxm (E0038B54)].ssxMCM.SetPage() - "SKI_ConfigBase.psc" Line ?

 

 

 

gonna see if starting the game without it then enableing it after sexlab started will fix it.

 

If you start when SexLab is not fully installed, you should get a messagebox telling you that the mod cannot run in this save.

But the errors looks like (I need the papyrus to be sure) the same another member posted today: not enough memory available.

Posted

I offer a free Papyrus.log examination for everyone want it to be done.

 

Posted

thats why ima try starting game first then afterwards install SSX. also found that perma adds SSX as dependency so has to be added to list to not add.

 

hopely starting with it not installed first fixes it and it not be the 60fps menu replacements doing it.

Posted

thats why ima try starting game first then afterwards install SSX. also found that perma adds SSX as dependency so has to be added to list to not add.

 

hopely starting with it not installed first fixes it and it not be the 60fps menu replacements doing it.

 

Let me know. I never tried "Perma". (I have no clues of what it is.)

Posted

 

thats why ima try starting game first then afterwards install SSX. also found that perma adds SSX as dependency so has to be added to list to not add.

 

hopely starting with it not installed first fixes it and it not be the 60fps menu replacements doing it.

 

Let me know. I never tried "Perma". (I have no clues of what it is.)

 

 

Perkus Maximus. It's a total perks overhaul mod that uses skyproc patcher.

Posted

I offer a free Papyrus.log examination for everyone want it to be done.

 

Really?

My god man you are a saint.

I've been having some problems with 1.3;

Actors meet but sex does not initiate. My rule might not be correct.

I should note that v1.2 worked quite well for me.

 

I am actually concerned about all the nasty stuff going on with my game.

It is a very old install with many removed mods, and edits to mods. It's a very filthy game.

 

View at your leisure.

Thanks

Papyrus.0.log

Posted

yep was right when i instaled it on a game after i started the mcm dropdowns showed. now to just make me some good rules and im good to go.

Posted

...

 

Hi, here some analysis.

First thing: you have a bunch of normal missing properties from the DLCs. Be sure you do use USLEEP.

A mod with code "SLIA" is having a bunch of problems because the items are different from the ones in your save. Uninstall, clean the same, reinstall.

 

SSX in your case initializes in less than 3 seconds, not bad: SSX DEBUG: Elapsed time for Loading Configuration = 2.386002

Tags scanning is a little bit more than 3 seconds, better than my rig: Elapsed time for Tags scanning (OnPlayerLoadGame) = 3.108002

 

You have a mod to stop the naked comments. You have many errors in the log about it (but not a real problem.)

 

I can see a small error of my mod in the scanning. Please change the scan mode from "Cell Scan" to "Alias Scan".

 

I can see that you overwrite PapyrusUtil of SexLab 1.62 with something else. This is creating tons of problems. Reinstall SexLab and DO NOT reinstall PapyrusUtils.

 

And then I see errors of my mod because of the previous error of the scan.

 

Globally your papyrus is pretty clean.

Posted

 

...

 

Hi, here some analysis.

First thing: you have a bunch of normal missing properties from the DLCs. Be sure you do use USLEEP.

A mod with code "SLIA" is having a bunch of problems because the items are different from the ones in your save. Uninstall, clean the same, reinstall.

 

SSX in your case initializes in less than 3 seconds, not bad: SSX DEBUG: Elapsed time for Loading Configuration = 2.386002

Tags scanning is a little bit more than 3 seconds, better than my rig: Elapsed time for Tags scanning (OnPlayerLoadGame) = 3.108002

 

You have a mod to stop the naked comments. You have many errors in the log about it (but not a real problem.)

 

I can see a small error of my mod in the scanning. Please change the scan mode from "Cell Scan" to "Alias Scan".

 

I can see that you overwrite PapyrusUtil of SexLab 1.62 with something else. This is creating tons of problems. Reinstall SexLab and DO NOT reinstall PapyrusUtils.

 

And then I see errors of my mod because of the previous error of the scan.

 

Globally your papyrus is pretty clean.

 

 

Thank you so much.

 

I may have done a bad job cleaning my DLC's.

I've added many of my own naked comments to my followers, I must have borked some of them.

I installed SLIA (SexLab interactive arousal) then removed it, used savetool to remove scripts,

when I open the save again I still see SLIA scripts behind a hashtag. (?)

 

I am unfamiliar with USLEEP, but I will get it.

 

Thanks again,

and I am a big fan of SSX.

Posted

 

and I am a big fan of SSX.

 

 

Thank you.

 

There are two GlobalVariables, one with the ID A8653, and one with A8658 (both are from Skyrim.esm), that are marked as "Constant", so when the game tries to update them you get 6 lines of papyrus errors.

You can do two things:

1) Make the globalvariables NOT constant

2) Edit the vanilla psc "QF_WICommentNaked_000A8655" and remove the update to these global variables.

 

 

P.S. In a few I am going to provide a small patch to solve the scan problem (cell scan and fast moving to other cells.)

 

Posted

OK, here is the first patch: 

Just replace the files of the normal version 1.3 with these files.

No need to clean save or do anything special. Just be sure the mod is stopped while updating.

 

In future, I will do the full version (I still have to check and fix the problem on the consequences when aggressiveness is possible.)

Posted

so the attached pic. i'm assuming everyone else got this too ya? i don't notice anything weird.... yet...

 

Interesting...

Is SexLab in your save game FULLy installed?

Posted

 

so the attached pic. i'm assuming everyone else got this too ya? i don't notice anything weird.... yet...

Interesting...

Is SexLab in your save game FULLy installed?

lol uhh yea. i mean i guess. no issues with it other than it changed my wolves to huskies...

Posted

 

lol uhh yea. i mean i guess. no issues with it other than it changed my wolves to huskies...

 

 

Try the new patch.

Posted

 

 

lol uhh yea. i mean i guess. no issues with it other than it changed my wolves to huskies...

 

Try the new patch.

ok just fyi - that was just on first install (one time) it doesn't come up anymore.

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