Why SL sometimes installs automatically, and sometimes doesn't?

[Roggvir]

(SL 1.63 SE)

 

It isn't a problem (probably), but i would like to know the reason, because it used to be that when i started a new game, SL usually installed itself automatically after a while, or after saving and loading the save.
Recently i had to reinstall everything from scratch, and now SL doesn't auto-install when starting a new game.

(i might have been using some 1.63 beta before, so MAYBE there was some change in 1.63?)

 

I can already hear everybody screaming that i can just click the button in MCM, yes, i can.

But the point is, SL's behavior changed, which means that something had to happen to change it.

I want to know what it is, to make sure it really isn't a problem, or that there aren't other side effects.

I don't like when things change seemingly on their own, it usually indicates some error - that is my lifetime experience, so please, do not tell me to just click the butotn, tell me instead WHY did the behavior changed, pretty please.

[Just Don't]

SL won't install in a new save immediately. You need to save and load or close the game and load a save with SL already enabled for the installation to start automatically. I feel like it always was this way, at least in the SL 163 releases (beta and current 163 non beta versions, I don't remember if SL 162 for LE or 164 for AE are the same). 

[Fiend71]

I do know what you mean. 

 

If I did something else first, then SL would auto-install.  I haven't tried it lately though, since I always, without fail, do that first now...lol

 

That was without ever saving, or loading...just wait. 

 

Not that I doubt Just Don't's opinion - not for a second. 

 

I do remember that though.

[Roggvir]

Yeah, for me it was always as i described, until now.

[Just Don't]

I do not posses any technical knowledge, but I do remember how I got that consistent behavior since late 2019 to this very day, using different beta releases and the current SL SE 163. Also note that the recommended procedure is to wait for other mods to initialize and the new game intro to be completed (once character finishes vanilla start, or chooses starting location and finishes character creation in alternate start mods). So I doubt a quick automatic install is the norm here.

[Roggvir]

Well, looking at the "sslSystemAlias" script, it automatically installs under two circumstances:

 

1.) When version is zero, but script is in Ready state, which shouldn't happen (it should get into read ystate after the installation, at which point the version should be set to some >0 number), so SL tries to fix it by forcing the installation setup to run.

2.) When the periodical checks detect the Ubound quest reached stage 250

 

I always use ASLAL start, so maybe i used to have an older version, and it used to complete this quest or advance its stages., but the current version doesn't do it - but this is pure speculation.
Or maybe i was always and reliably suffering from whatever that glitch is, that results in situation 1.

 

Anyway, i think i can put it out of my mind, it is clear now what the intended behavior is.