Wrye Bash

What works

Everything. there seems to be no issue at all no matter what version. Both the 306 and the 307 beta were tested in wine in tandem in the same game directories with no ill effects. I have heard of a bug in the beta that attempts to combine all mods into a merged mod but i did not experience it, so it may be fixed. I also tested this on several versions of wine just for kicks and it seems to play nice with anything above the 1.6 including the staging versions. since it has proven pretty stable with the more recent versions, i felt it was time to post newer results to keep it relevant.

What does not

Not sure, but every feature that was tested and i did not want to follow to completion, seemed to start great, even though nothing was altered and i backed out from those tools before making any potential changes.

Workarounds

What was not tested

Some of the more complex operations were not completed to the end by choice. this has no bearing one way or the other on whether or not they actually work, but the absence of any meaningful errors and the stability of the program seems to indicate nothing is broken bad enough to lock the program or cause any operation to fail. in other programs i have experienced stunted gui, weird graphical glitches, or buttons causing crashes, but this is not one of them. It allowed me to browse all the functions and back out without retribution.

Hardware tested

Graphics:

• GPU:
• Driver:

Additional Comments

To install wrye bash successfully in wine, several things must be done first to prepare the environment for the program installer. follow the steps below to ensure it all works. 1. prepare the wine prefix of the game you wish wrye bash to be installed for, by downloading and installing the Windows installer python dependencies, listed on the github page, in the wine prefix. these must be installed using the wine control panel gui or a similar install method by the shell. something that will recognize the first dependency which is python 2.7 msi. and the following ones should be installed the same way. when the installer gui pops up for python 2.7 it will auto complete the install directory. however, not altering it will just cause the installer to pantomime the install and not really install the files, it just evaporates, so to keep that from happening, one must use the "go up" button and manually type in the correct directory structure which will be populated correctly once you manually type it in. so for instance C:\Python 2.7 would be correct. then let it do its thing and it will register. very important, it must register in the registry. double check the directory structure to see if the folder exists in the C:\ directory. this should mean it has registered correctly. if it is absent then start over. 2. install all the rest of the dependencies. the reason for making sure python 2.7 does install and register correctly is because the third and fourth steps of python dependencies listed in the wrye bash github, both do a check of python 2.7 and depend on it being successfully installed and registered, if it doesn't pass the check, then go back to step one and start over. you may have to uninstall the second step and then proceed. ymmv. 3. once all dependencies are installed then it is safe to attempt the wrye bash installer. there will be a wizard in the wrye bash installer giving a few choices for your preferred install. by default it will detect the normal Bethesda install location and install wrye bash there, however it gives a warning that doing so may keep wrye bash from executing due to UAC, because it may not be able to detect its own files, but all it does is check if there is UAC and return null in wine, so seems to be no issue under wine, only in an actual windows environment that really has UAC. any choice you make, whether the regular install location, or an extra location, using the stand alone method for the exe version or python version should work. it will install in whatever directory or method you choose and still detect your game. 3. make your shortcut to wrye bash for the wineprefix it is in. take special care to point it to the install location you prefer to use just in case you have chosen all three methods, or make a shortcut for each if you prefer. recommended for ease of use and the least potential for error would be to install in an extra directory with either stand alone and point it to which ever location you have chosen. 4. start the program in debug mode so you can see an error log. if it does not start then it may be a simple fix. if it has this error then it is a simple fix (ymmv) "ImportError: MemoryLoadLibrary failed loading wx\_core_.pyd" this has to do with a few dlls missing, depending on your wine install of the game you use wrye bash with, they may or may not be present, but usually they are already in windows\system 32 so if wrye bash cant find them, copying them in the same directory as the wrye bash exe, or the python launcher, will make it easy for wrye bash to find them. the dlls are gdi32.dll, gdiplus.dll, and msvcp71.dll. 5. after this wrye bash should start with no errors, and a short splash will confirm it works with the wrye bash logo in a square window, then the gui will pop up and have detected all mods, then you can go to town selecting any mods not active and sort the load order with the program. it also has a lot of other powerful features so be careful what you change. any load ordering program has the potential to break the game it is associated with. there seems to be less such issues with wrye bash, but again, ymmv. happy bashing!

Use version 306+

How-to:  https://github.com/wrye-bash/wrye-bash/wiki/%5Bdev%5D-Running-Wrye-Bash-on-WINE-%28Arch-Linux%29.

WIP!