*PLAYER TESTING NEEDED* Vanilla Savegame! :)

[FastestDogInTheDistrict]

(Edit: thread name changed)

 

*SAVEGAME TESTING NEEDED - PLEASE SCROLL DOWN*

 

 

Something just occurred to me, and I don't think I've ever seen it specifically discussed...

 

I am creating a couple more savegames for people to download. I have noticed before that when the game is run from the SKSE launcher, a little additional file is created along with the .ess save - an .skse version, about 5k in size. This little extra file is not created if the game is run from the Vanilla launcher, which seems to make sense.

 

My question is - if creating a save for other people to use, is it better to do it via the SKSE launcher or the Vanilla?

 

(*note that for all other purposes the save is pure Vanilla & clean. My load order at this moment is a clean re-install of the game with *no* mods - just the basic game .esms including dawnguard, and the HDDLC .esps).

[FastestDogInTheDistrict]

...or perhaps to make a save for this kind of purpose with SKSE not installed at all?

 

What I'm trying to do is ensure maximum compatibility, and to make sure I'm creating clean saves which can keep being used into the future.

 

(*note also - I'm not asking whether the .ess.or .skse save is the right one to package for download, it's definitely the .ess, but I'm curious as to whether SKSE exerts any influence on a Vanilla save going forward, and/or whether it's installation at the time of save may prevent compatibility with future versions).

[FastestDogInTheDistrict]

...does anyone know? Or am I truly asking a boneheaded question?

[BSnake]

If you download save file mods on the Nexus, they usually contain just an .ess file. When a user has SKSE plugins installed and loads this .ess file, their plugins will likely create a coinciding .skse file upon saving. I'm guessing that you shouldn't bundle an .skse save along with your .ess. You should probably ask the SKSE dev team, though, or ask someone with SKSE plugins installed to test your .ess file.

[FastestDogInTheDistrict]

If you download save file mods on the Nexus, they usually contain just an .ess file. When a user has SKSE plugins installed and loads this .ess file, their plugins will likely create a coinciding .skse file upon saving. I'm guessing that you shouldn't bundle an .skse save along with your .ess. You should probably ask the SKSE dev team, though, or ask someone with SKSE plugins installed to test your .ess file.

 

 

Actually, that does answer my question I think. My own uploaded saves contain only an .ess version (although in the very first couple I ever did, I somehow buggered it up & I couldn't work out how except that it might have something to do with SKSE & me uploading an incorrectly executed, tainted save) - my chief concern is/was future SKSE compatibility. If SKSE basically takes a Vanilla save & runs with it then all should be well.

 

Good point on the testing - I'll attach a tester save below! Thanks indeed BSnake!

 

 

 

Basically, all I need to get confirmed is that other players are able to load the save & that the character is visible & able to move in-game.

 

DETAILS: Vanilla save, Vanilla launcher, Helgen Keep, Imperial

 

Load Order at time of save (basically pure Vanilla):

 

Skyrim.esm

Update.esm

Dawnguard.esm

HighRes TexturePack01.esp

HighRes TexturePack02.esp

HighRes TexturePack03.esp

 

testpreset.esp

                                   I use these two for making & testing presets - they're clean as a whistle.

testpreset01.esp

 

 

Save 3 - Ragnar Helgen Keep 00.15.37.rar

[FastestDogInTheDistrict]

If anyone's able to give this savegame a very quick spin in their Skyrim, I would be very appreciative indeed!

 

I just need to confirm that for other players he's visible, able to move, not popping up naked, etc. It might require a maximum of 2-3mins play time.