GUIDE Wrye Bash Guide

[z929669]

The Beta Wrye Bash Guide to STEP Installation is available

on THE WIKI

 

Based on the advice I received from users here, I will be asking TC to host on his site if he wishes. I will also host right here on the STEP wiki site when final. It is not yet final, but I will make it so once we have a fully compatible BOSS-Wrye Bash implementation to support Skyrim v1.5.

[violetarc]

Hi, I am new to Wrye Bash and I have been following the guide here on the STEP Wiki. However, I am confused about why the installation for SKSE and Script Dragon are modified on this page at the bottom: https://wiki.step-project.com/Guide:Wrye_Bash#tab=Pre-installation_Setup

 

Can someone confirm that this is indeed how both of these should be installed?

 

Also, do I run Skyrim through SKSE like before?

 

Thanks. I come from an older STEP (2.1.1b) and NMM so this is very different from what I did before... especially SKSE.

[z929669]

Hi, I am new to Wrye Bash and I have been following the guide here on the STEP Wiki. However, I am confused about why the installation for SKSE and Script Dragon are modified on this page at the bottom: https://wiki.step-project.com/Guide:Wrye_Bash#tab=Pre-installation_Setup

 

Can someone confirm that this is indeed how both of these should be installed?

 

Also, do I run Skyrim through SKSE like before?

 

Thanks. I come from an older STEP (2.1.1b) and NMM so this is very different from what I did before... especially SKSE.

The WBG is outdated for everything but WB itself. Just follow the STEP PDF guide from the Nexus.

[violetarc]

Good to know - thank you!! 

[frihyland]

I may write a short tutorial for how to properly use the advanced features of bain.

 

Advanced bain  

• unpack to project
• sync with data
• pack for release
• create project from conflicts

and others are incredibly powerful tools we should be recommending.

 

Combined with DDSopt and TES5edit (and eventually Thunderbolt) I see this as the way forward.

[z929669]

Go for it. I will articulate whatever you create with the WBG.

[z929669]

The WBG has been updated. Installation and BAIN sections were updated as were several other things throughout.

[TechAngel85]

I don't know a lot about WB so I'll leave this up to you, Z.

 

I don't think the Notice on the Mod Management tab is needed anymore and the link in the INI Tweaks on that tab no longer works.

[torminater]

How can I enable the LAA flag for Wrye Bash when I'm using the standalone version since I am using Windows 7 64-bit? I'ld like to speed it up a little! ;-)

 

 

EDIT: OK fellas I've got several recommendations for you to add to the guide:

As a 64 bit user with 4GB RAM and more those tweaks may be applied to Wrye Bash to work enormously faster

 

- Go to bash.ini and uncomment the "s7zExtraCompressionArguments" line and change it to:

=-mx=7 -m0=lzma2:d=32m -ms=off -mmt=7

 

- Go to Mopy\bash\compiled and remove the LZMA.dll and 7zUnicode, and replace the 7z.exe and the 7z.dll with the 64-bit ones from the 64-bit 7zip installer that you can download from 7zip.org. <- Doesn't work so far, I'll try out some things and give feedback! <- Only works when using the 64-bit python version of wrye... trying to find out whether I can fix that!

- Well, because the tweak above doesn't really work, I temporarily use LAA flags for all the 7zip exe files used by Wrye in the said folder. Everything seems to work a whole lot faster...

- Download CFF explorer and open up Wrye Bash.exe. Click on file header and go to File: Wrye Bash.exe\Nt Headers\File Header and click on "Click here" Then tick the "App can handle >2GB adressset"

[z929669]

I think that you had better start over from the beginning. The post above is not making any sense to me :confused:

 

Most users around here are on 64-bit, so I'd like a definitive and tested and reproducible procedure for getting 64-bit functionality out of WB and 7z under WB. Python 64 seems like a prerequisite, but I am pretty sure that the Python extras do not have 64-bit versions available.

[SSL]

wxPython is in 64bit version... as well as pywin

comtypes are needed for pm tab, because no1 uses that - comtypes aren't needed

Go to Mopy\bash\compiled and remove the LZMA.dll and 7zUnicode, and replace the 7z.exe and the 7z.dll with the 64-bit ones from the 64-bit 7zip installer that you can download from 7zip.org. <- Doesn't work so far, I'll try out some things and give feedback! <- Only works when using the 64-bit python version of wrye... trying to find out whether I can fix that!

You mean it works (with 64bit python) or not?

[torminater]

I think that you had better start over from the beginning. The post above is not making any sense to me :confused:

 

Most users around here are on 64-bit, so I'd like a definitive and tested and reproducible procedure for getting 64-bit functionality out of WB and 7z under WB. Python 64 seems like a prerequisite, but I am pretty sure that the Python extras do not have 64-bit versions available.

Yeah, I figured it'ld be misleading ... didn't want to double post though.

 

Situation is as followed:

- I currently DDSopted all vanilla textures and put the extracted and optimized folders in WB installers directory. After that WB took ages and more to load anything at all.

 

- I didn't like that Wrye was so slow and tried to find means and ways to improve WB performance. I knew that WB Standalone (the version I use) is a 32 bit application and so cannot naturally use more than 2 GB RAM. With all of those huge folders (somewhat like 10 GB on top of Full STEP) it was just overloaded.

 

- Additionally the 7zip version implemented by WB Standalone is 32 bit, too, so the same as above applies here too, when it comes to unpacking and packing those folders and archives for installing purposes...

 

- I then found the optimize 7zip compression method thread under Hints or sth like that in the Guides forum. There were two comments on how to use the improved compression method  using multiple cores under WB. I then took the setting recommended by the last of those comments as a base. I then read about using non-solid compression for the optimized vanilla archives (and other big archives like BethHRopt) and thought that it'ld be a great idea to let WB use this automatically, so I set the solid compression to off in the bash.ini file. All the other settings recommended in this comment I didn't look up, so I don't know whether they're good or bad... but at least it works for me.

 

- Now I looked up in the internet how I could improve WB's speed and functionality with a huge load of files and I thought... well, it'ld need to access more RAM to be faster... So I found out how to set LAA flags to any exe using CFF explorer (freeware from Nt). I then set the LAA flag for Wrye Bash.exe as explained above.

 

- I also was aware that WB used 7zip 32 bit as extraction and compretion program and I tried hard to find a way to use the 7zip 64 bit version which is installed on my system... but I couldn't so far. I already posted on the relevant nexus threads but so far no answers were given to my issues... So in absence of a better idea, I set LAA flags up for all three exe files in the compiled folder of Wrye Bash (detailed path found above) so even if it was just a 32bit application it could use all the RAM it could get (I only have 4 GB RAM anyways on my Laptop).

 

So, I hope I was a little clearer now. :-)

I can say from my experience that packing and unpacking those huge archives goes much faster now (takes 22 seconds from opening WB til the end of loading the installers tab now... before it was at least 1 minute). Didn't use benchmarks (don't really know how to anyway) but WB starts faster, opens the installer tab faster, packs archives faster and unpacks archives faster, still it takes several seconds (15-20) where WB is "not responding" until it is done loading. Maybe these "non-responsiveness" gets increased by setting the LAA flag, since WB as 32 bit application is actually not made for more than 2 GB of RAM and it takes too long to work off the data overflow...

 

Two things I wished to come true:

- Find a way to use 7zip 64 bit with WB standalone (seemingly impossible :-/ )

- Get a 64 bit WB standalone version (would need to be made by the author of WB) which already uses 7zip 64 bit... doesn't seem very likely. I don't know anything about programming but I guess it would take lots of work to port WB from 32 bit to 64 bit...

[SSL]

Mark folders with optimized textures (and texture packs at all) as "don't refresh"

[torminater]

Mark folders with optimized textures (and texture packs at all) as "don't refresh"

it won't let me ... ?! :-/

 

7zip 64 apparently works with the 64 bit python WB version... at least according to this thread...:https://forums.nexusmods.com/index.php?/topic/390341-so-is-there-a-way-to-get-wrye-bash-working-on-64-bit-systems/page-2

[SSL]

Mark folders with optimized textures (and texture packs at all) as "don't refresh"

it won't let me ... ?! :-/

 

RU sure you click on directories, not archives?

[torminater]

 

Mark folders with optimized textures (and texture packs at all) as "don't refresh"

it won't let me ... ?! :-/

RU sure you click on directories, not archives?

Well...???

I only have 7zip archives in WB installers tab. Why should I have uncompressed folders anyway?

 

Edit: I see, well so it's either having more space on my HDD or less loading time with WB xD

Isn't it a bad idea to tell WB to not refresh any of the texture/mesh mods?