SOS issue on save load

[anjenthedog]

Not exactly sure when it started (likely after some *ostensibly innocuous mod update effort) persistent issue with one player vector (ie named player instance) where SOS does not initialize correctly upon savefile load.

 

It always results in "this game is corrupt" modal for the character's save files. All of them. (I'd also note that it opens far enough to display the player in T-pose)

 

click ok, SOS modal notice is now displayed (that the save contains different entries than it should and it will now fix the issue), but its "OK" button cannot be clicked. 

- presumably the game has already gone into dumbfounded mode by that point...

 

Game spins for a ~minute (time can vary wildly, from 10-15 seconds to several minutes), then returns to the main skyrim menu, and a cash-register "cha ching" is sounded.

 

Click "Load" again, choose the same save file as before.

 

No corrupt file message is posted this time

 

Game opens to SOS notice that the save file contains different entries than it should, and it will now fix the issue. 

 

Click OK, and...

 

It does not actually fix the issue, (no evidence of an in-game SOS initialization is displayed in 'notices' where it would normally be presented, or in console) but it does allow ~relatively unimpeded play (certain SOS selections are unavailable, including the normal SOS male genitalia and the ERF addon)

 

All the other player vectors work fine. No missing SOS stuff, no errors on load.

 

Save works fine. Save file reported as clean in re-saver. (as are successive save file made during "the current session" after going through the above).

 

Anyone recognize this issue, and maybe know how to fix the general problem, and if so would such a solution have to be done on the others as well to ensure their continued "correct" operation?

 

Edited August 16, 2024 by anjenthedog
details

[traison]

Changed your load order lately?

 

Edit: or by player vector do you mean one character out of many that was made with the exact same load order?

Edited August 16, 2024 by traison

[anjenthedog]

player vector: new game create and name unique new character, ex: "BrutalBrittany the Wanton Warlord", "Ajigorn", "Bob da Skyrim Player" "Sasha Sashinski" etc. 

 

The named-player characters we use for playing the game. I have several. (my avatar here @ LL is one player vector  - Ajigorn fwiw).

 

One such vector (a player character named Aereonne) is experiencing this issue.

 

ALL player vectors use the same mod load order. The only substantive difference is the character definition

 

Load order *might have changed, not sure. Am aware that "mid game changes can cause problems".  Six of Seven player vectors (again, unique player character instantiations) load just fine, no issues, SOS presents and functions correctly for six of seven. This one (Aeronne) does not and hasn't since some update or series of updates (uncertain which or exactly when), perhaps a month or a couple months ago (I routinely update mods that are flagged for update)

 

I read something along the way a while ago (when this wasn't in evidence) about how some SOS initialization problems can be solved by disabling the mod then creating a new save and reenabling the mod... or something., Not sure can't find post, and not really willing to blindly grasp at half remembered posts for solutions to some possibly related issue that I saw in passing months ago if not years.

Edited August 16, 2024 by anjenthedog

[traison]

10 minutes ago, anjenthedog said:

I read something along the way a while ago (when this wasn't in evidence) about how some SOS initialization problems can be solved by disabling the mod then creating a new save and reenabling the mod... or something

 

Yes but considering other characters with the same load order work, I doubt that's it. It was just a theory since I've never seen anything like this, it seems like it could be part of some more recent version of SOS. So my thinking was that was their way of dealing with the load order issue of older SOS versions.

 

How about a link to the SOS version you're using? Gonna have to take a look at the dll probably.

[anjenthedog]

0.1.6.7 a10. Installed May 2023. Worked fine from the time it was installed until recently for All players.

 

Sorry, got muddled for a sec. Males (Schlongs of Skyrim) 1.0.0

Edited August 16, 2024 by anjenthedog

[nilead]

19 minutes ago, anjenthedog said:

I read something along the way a while ago (when this wasn't in evidence) about how some SOS initialization problems can be solved by disabling the mod then creating a new save and reenabling the mod... or something.,

 Not exactly. If you use MO - hide SOS dll file, load into the game (you'll get a metric ton of errors, but it will load), save, exit, unhide .dll file and get back into the game, effectively resetting SOS. Used to do that dance alot when SOS just caused crash on load after LO changes.

 Got fed up and switched to TNG eventually, can wholeheartedly reccomend.

[anjenthedog]

Ok thanks for the confirmation of the basic reset scheme. (I'd presume "hide", by whichever means, be it via MO2 or literally pulling it out into a dummy folder for the duration) disables it

 

So if I do that for the one player, will I need to do that for all my players? (even though the other ones are currently working)

Edited August 16, 2024 by anjenthedog

[anjenthedog]

OK... may/might have answered my own question  kinda ... sideways. Suddenly, the mod in question is encapsulated in a Nexus Beta warning page wrapper and says it requires AE.

https://www.nexusmods.com/skyrimspecialedition/mods/112351

That's a (potential) problem.  (I play exclusively under 1.5.97).

 

Although it doesn't explain why six of seven player vectors (unique player instances)  have no issue using it...

 

I didn't install it from any such page. and it's hotlinked from Vortex to Nexus so I know that I didn't install it from my hard drive manually... Weird.

 

Edited August 16, 2024 by anjenthedog
little additions...