Neovalen

To SR users: If you want to help me BETA test Dual Sheath Redux tonight, please pm me your Steam ID so I can add you as friend or add me user: Neovalen (duh). Giving you guys first crack at it. Remember this is BETA though... :) I will be getting home at ~8pm pst and working on the mod until 1am or so.

No need to re-do any textures.

Also as a note, Uncapper was updated for v1.9.28 so yes it still requires bAutoUpdate to be set but should have no issues with Legendary. (Not that you need it with uncapper... its essentially a I want to forget this and take other perks cheat made by Bethesda which I will not be using)

Update.esm has changed. Therefore you DO need to reclean the base Bethesda files AT A MINIMUM to make sure your actually using the new records properly. If you ignore this then it will use the v1.8 cleaned ESM in your overwrite dir from the last time you cleaned and WILL cause issues.

So he does! Must have uploaded it late last night. Hadn't looked yet today. Will update.

They honestly likely do the same thing. Was planning on switching to the RaceMenu one just to take a mod off the list for simplicity sake but he doesn't have one for the 1.9.32.0 version of Skyrim yet (the latest "fix" beta).

That makes sense to me - it's what I would assume the overwrite folder was for! However, further up the instruction guide, under the heading "Clean the Bethesda ESM's" is this instruction: "Select all the ESM files in the /Data folder except Skyrim.esm and move them to the /overwrite directory." Following that instruction is how the DLC's came to be in the overwrite directory in the first place, and I don't remember seeing any instruction to take them back out again (though I could easily have missed it). Should they be removed? Leaving them there would seem to negate any changes affected by additional mods. Or do I still not quite get it? For me, when cleaning the base Bethesda ESMs MO leaves the cleaned base files in the main Skyrim directory. Obviously I'm trying to keep my install vanilla so I manually move them to overwrite. Now of course I'm missing those 4 vanilla ESMs so the next instruction is to restore them from TES5Edit backups. This is explained in the guide. Note: If you are re-cleaning then delete the corresponding ESMs in the overwrite folder and repeat.

That note is left over from when we used to manually create the Atlas Dragonborn module(the author now has his own which we modify slightly). Therefore removing the note. In general, the only files that end up in overwrite when you see that note are NEW files created during the patch process which have to be moved manually. (I.e. XX-YY Patch.esp) Anything that existed at launch and is modded will be moved automatically by MO.

Damn I'm happy, everything I had hoped to accomplish regarding the Dual Sheath Redux scripts has come to pass... the update I thought about during work today worked perfectly! *grins* This means I have confidence enough in my script to move forward and work on the "dragonborn" workaround for SkyProc (if I can get that to work).

Right now it is built with 1.8 as the 1.9 creation kit has not been released yet. Obviously not finished yet either of course. Works great for the most part ATM and think I just discovered how to fix the last issue I was having (pending more testing). I'm my own worst enemy with my rigorous testing. Just wish I had more time... between work, family, and being sick recently(damned cold) I haven't gotten to work on it as much as expected.

Keep in mind the 1.9 version of the guide is in its infancy and incomplete so don't consider it bible ATM. That's why I made a 1.8 backup.

Try optimizing without putting it into a BSA... I optimize loose files not into the bsa.

Now that I think on it more... think I'm going to bite the bullet and do the update to get a head start. Before I do that I will make a backup of the 1.8 guide on the wiki as the "stable" build. If you have a game in progress I highly suggest you stick with that for now.

It already does this.

I'm likely going to make a backup copy of my current 1.8 then once I feel 1.9 isn't overly out of reach do an update.

Mine didn't and this fixed it right up. Thanks!

Thank god my build is locked down.

I do... yes.

The new USKP version for 1.9 is up also... damned huge.

That's just the NMM being dumb. :) For some reason setting a recommended option in the installer makes it pop up that message. Ignore it and select options listed. :)

Skyrim 1.9 is out of beta. Hope you all followed my advice here and on the top of SR to stop steam from auto-updating until patches are out for various mods. :)

Its better to use original esps.

Did Steam actually stop the auto update this time?

64bit or DX11 would help a TON for Skyrim. Sadly as explained above the problem is RAM not VRAM. ( see the STEP support section for slews of posts). Dx11 would skip mirroring textures in RAM and 64bit would allow us to run more than 3.2gb but that's a Bethesda fix....