An interesting symptom

[lethielnyrond]

So, I got a download from Steam today. SSE 1.5.3.

 

I have SKSE64 and SkyUI 5.1 SE, and they run on the whole very well. I've just started a new playthrough, I have 240+ mods all of which work very well together, and I'm enjoying it very much.

 

When the download had finished, I tried to start SSE.

 

I got a message saying my version of SKSE64 didn't support this version of Skyrim. So I went to the page and downloaded and installed 2.0.4. Ran LOOT, ran Wrye Bash, ran SSEEdit. Tried again.

 

I got a message saying achievements were disabled. So I went looking, and found sure enough there was a new version of Achievements Enabler for SKSE64. I deleted the old version, installed the new version, ran LOOT, ran Wrye Bash, ran SSEEdit, tried again.

 

Crashed after the first load screen. Restarted NMM. Tried again.

 

Crashed after the first load screen. Restarted the computer. Tried again.

 

Crashed after...you get the idea.

 

An interesting feature of this new beta version of SSE is the way it doesn't bloody run.

 

I know a lot of people are going to tell me it's my own fault for using mods/using NMM/enabling achievements/having too many mods/going for SKSE when it's an alpha release/going for SkyUI ditto/opting into the beta in the first place. I'd love it if we could take all that as read, but I've been around these forums for a while and I know that's too much to ask.

 

If anyone knows a way in which I can get back to the SSE I had this morning, that worked perfectly well with all my mods and gave me an excellent gaming experience as opposed to bugger all, I'd be very very grateful. If it involves wiping everything and rebuilding my rig from scratch, though, I'm unlikely to bother. I've done that too many times already.

 

Really hacked off right now.

 

Lethiel

[WastelandAssassin]

try unchecking all mods , and running Skyrim from the SKSE64 executable , and see if any errors come up

if the game runs properly , than it means that one of the mods you have installed causes the crashes

what I would do is either start from an empty load order and start activating mods in sets of 10 or so plugins , and try to see when the game stops working (you can also activate all plugins , and start removing plugins in groups , to see when the game works)

try to find which mod is causing your crashes , and remove it if necessary

 

this is a very crude and basic way to work , however do to the very limited information you seem to have (no specific error messages upon crashes) , there isn't much to work with

[lethielnyrond]

Well, I know what's causing the crashes. It's the update. No crash before, crash after. My mod setup worked perfectly well with the previous version of the game, and should work perfectly well with this version. A mod that did not cause a crash with version 1.4.2 should not cause a crash with version 1.5.3. If it does, then version 1.5.3 is (from my point of view) faulty.

 

I've had this discussion before. I'm just not interested in playing Skyrim without mods. Bethesda may not agree, but that's just the way it is.

 

Thanks anyway. I know you want to help, and I appreciate it.

 

Lethiel

[WastelandAssassin]

yeah , I know how you feel

that's the faulty implementation of the CC , with it's constant updates screwing with the script extenders and all

but this isn't going to change , as it would seem

 

If you can play the game without the problematic mod , than maybe that's the best you can have for now

but it's really a sad day when a company breaks the game for their costumers , even if for a limited time

[lethielnyrond]

And looking at the Steam discussions, I'm not the only one. Some people haven't been affected--I'm sure the ones who are playing the way Bethesda want them to play--but others are just as angry as I am, if not more so.

 

Well, it was fun while it lasted.

 

Lethiel

[lethielnyrond]

Well, I found the "mod that was causing the trouble" (Enhanced Character Edit) and I found the update patch and I found out the non-standard way to install it (thanks R246!), and I'm back in my game with all the mods working. Pure luck at every step.

 

And of course the mod wasn't causing any trouble at all...as with the "false save corruption" bug that I've now given up on ever seeing fixed, it was the update to the game that caused the trouble. All because Bethesda are still desperate for a way to squeeze some money out of modding.

 

Sigh.

 

Lethiel

[Rfsp2]

Lets be realistic here for a second.

 

The update isn’t at fault, one or more of your mods is, because the modders didn’t have time to update their stuff and most are probably waiting for a stable version of CC and/or SKSE64.

 

You cannot blame bethesda for not accomodating for the 50k+ files currently available on the nexus at every update they make - it’s the modders who have to accomodate for beth’s updates, not the other way around. It has been this way since vanilla skyrim and it’s updates.

 

Just give it some time, when modders make the necessary updates everything should go back to normal.

[lethielnyrond]

And then there are the patronising ones...

 

The mods are not at fault. They were working fine. I did not ask for, want or need this game update, which appears to consist entirely of yet another attempt to introduce paid mods by the back door, and a rollback facility (or indeed an opt-out option) would have obviated the problem altogether. There's realistic for you.

 

In fact I have now identified the "mod that was causing the trouble" (by functioning perfectly with the game as it was); it was Enhanced Character Edit, and the creator (as I found out when I went looking) had already kindly provided a patch for it, so once I had found out how to install the patch (non-standard; thanks to R246 for instructions!) and done it, all was eventually again well, no thanks to Bethesda. Finding that out, without doing as WastelandAssassin suggested and spending two weeks painstakingly rebuilding my rig mod by mod, was a matter of pure luck, and reading the instructions on my part. If it hadn't been for that luck I would probably not have bothered.

 

No, I don't blame Bethesda for belatedly trying to monetize what was at the beginning a generous and innovative gesture to their fans. That's just the way of the world now. I blame them for doing it haphazardly, ham-fistedly and high-handedly. And so far, in my experience, the modders have been there with the updates ahead of them.

 

Lethiel

[nightscrawl]

Updates have been breaking mods since mods and updates were a thing that existed together, regardless of the game, regardless of the mod, and regardless of the update's purpose. It is always on the mod author to keep their own mod updated. You completely ignored the part where Rfsp2 stated it happened with Oldrim as well [it's also happened with other non-Bethesda games], and obviously the Creation Club had nothing to do with those updates.

 

The author of the mod released a patch, which is what should happen with authors who continue to offer support for their mods. The description page of that mod even says, "This is a beta version. Also SKSE. It will be updated frequently."

 

If you're using SKSE64 alpha, and mods that rely on it, frankly, that's on you for not waiting. It's been known for a while that this would happen because Fallout 4 users experienced this exact same thing with F4SE and the Creation Club. There are measures you could have taken to prevent the update if you wanted to keep using mods that rely on SKSE alpha. You could also have simply waited until the rush of frequent updates surrounding the Creation Club died down, as happened with FO4.

[lethielnyrond]

There are measures you could have taken to prevent the update...

 

Are there? It's the first I've heard of it. What are they? I may need them in the future...

 

I absolutely agree that part of it is on me for not waiting. Indeed, for bothering to play Skyrim at all till it was all finished and done. (Except of course it--hopefully--never will be!) And of course I know it happened with Oldrim as well. I was there. (Which is why I didn't bother responding to it.) It's precisely the purpose of this update to which I take exception. It's nothing to do with adding anything of substance to the game, and everything to do with the company trying to take financial control of as much of modding as they can get hold of. I don't see any difference between this and the Steam Workshop debacle, and nobody queried the outrage about that, as I recall.

 

But, I expect we shall have to agree to disagree. My game is working again, and as long as it continues to do so--and I can continue to avoid the Creation Club--I shall be a reasonably happy bunny.

 

Thanks for your responses.

 

Lethiel