Skyrim VR - CTD on startup when NOT using ESL support

[past79]

Hi,

 

first of all, sorry for posting here, since this is technically not SSE but very likely a VR-only issue. Had not started the game for about 2 months, but kept updating a few mods nevertheless (bad idea). Now I'm getting pretting much instant CTDs on the logo screen...

Crashlog here: https://pastebin.com/e6LUyBh7

 

I've pretty much rolled back and/or disabled all mods I touched since the last run one by one, without success.
 

PLUGINS:
	Light: 0	Regular: 0	Total: 0

So no plugins are loaded at this point? Verified game files, all ok.

 

Now the curious thing, when I enable "Skyrim VR ESL Support", I am able to launch the game and load into my last save without crash. I've never touched ESL Support before, although I plan to, since it pretty much requires a rework of my entire modlist - tons of merged plugins - and (pretty sure) a fresh save.

(Didn't run a full test, but I expect tons of errors due to the changed load order)

 

Might as well bite the bullet and make a fresh start, but I'd be grateful if anyone got an idea what is going on. I'm trying to get it to run since yesterday, and pretty much running out of ideas myself.

[traison]

54 minutes ago, past79 said:

since it pretty much requires a rework of my entire modlist

 

54 minutes ago, past79 said:

I am able to launch the game and load into my last save without crash

 

These 2 statements are at odds with eachother. If the game works, why redo your setup?

 

54 minutes ago, past79 said:

Had not started the game for about 2 months, but kept updating a few mods nevertheless (bad idea).

 

54 minutes ago, past79 said:

I've pretty much rolled back and/or disabled all mods I touched since the last run one by one, without success.

 

Clearly not all of them because presumably the game worked before the 2 month pause and now it doesn't. So something you changed has not yet been undone.

 

As for the crash, this unfortuantely is because of some mod requiring that extended ESL address space change. I'd say go through your mod setup again and find the mod that now uses the extended esl address space and downgrade it back to what it was before the 2 month break.

 

Otherwise check if BEES is available for VR. Should be no reason to redo anything with that one.

Edited July 8, 2024 by traison

[past79]

33 minutes ago, traison said:

Otherwise check if BEES is available for VR. Should be no reason to redo anything with that one.

 

From BEES author:

• Skyrim VR ESL Support is the Skyrim VR counterpart. I don't plan on adding VR support myself.

 

33 minutes ago, traison said:

These 2 statements are at odds with eachother. If the game works, why redo your setup?

 

Well, being able to load a save without crashing, and the game actually working without issues, unfortunately, are two very different things. But I'll do more testing on that one later if neccessary.

 

 

Thanks for your suggestions though, I'll return to what I've been doing since yesterday then. I was just hoping someone had seen this kind of issue before.

[past79]

Nevermind, I've found the culprit. In my case, it was the 3.3 version of

 

 

Yes, the changelog mentions "You will need a new game when updating to this version", and also that there were changes to the esp header version. And yes, I've missed both. 😶

Well, "new game" doesn't apply since I couldn't even reach main menu. Not sure what's going on with this new header version yet, but there might be more stuff breaking in the near future. Still curious esl support enabled it to work apparently, definitely threw me off track for a bit.
 

Quote

Supporting LE and old SE Versions

With the recent changes Bethesda made to the CK the SE .esp's of SLUTS are no longer compatible with LE unless you manually edit the headers back to the 1.5 standard (I believe a small tutorial on this can be found some pages back). Due to this, I am no longer going to upload LE versions going forward (You have permission to host a conversion on LL, of course)

Other outdated game versions are not excluded from this, SexLab in particular straight up does not work for any old 1.6 versions, and has crash invoking issues on 1.5 due to which support for this version will halt after 2.10 is being released. Whether or not SexLab P+ will be a dependency to SLUTS I dont know yet, but seeing how the first reason why SLP+ even exists is to aide SLUTS development, I cannot promise that this will never be the case

 

 

As such, and Im only going to say this once now: If you want to ensure that you can continue using SLUTS going forward, update your game