Wrye bash patch help

[Lehcar]

How do I merge patch mods into my Bashed Patch correctly? I tried merging several into it, but then I fired up the game and the first thing that happened was I saw that my Dark Brotherhood 7 murders delay mod had stopped working (it was one of the merged files)

 

What am I doing wrong? :(

[Striker879]

Not sure if this will help you or not, but MarkInMKUK posted this the other day and has graciously agreed to let me repost when it may help (I've added emphasis on the merge mods part):

OK, so, we will assume that you have a correct Python install, and have installed Wrye Bash, and BOSS as well. There SHOULD be a shortcut labelled "Wrye Bash Launcher" on your desktop if all went well. Double-click it as you would any other desktop shortcut, and Wrye Bash will pop up a small window while starting, then its main window.

 

At the top of the Wrye Bash window is a series of tabs labelled "Installers", "Mods", "Saves", etc. Make sure the one labelled "Mods" is selected - the others can be ignored for the moment.

 

Next, look right at the bottom of the window. You should see a series of icons, including a pale green and pale pink aquare, and the familiar Oblivion icon. Depending which other Oblivion-related programs you also have installed, you may see icons for paint.NET, Blender, Bink Video utilities, and plenty of programs which I also don't have installed. The one to look for is the word "Boss" in black lettering.

 

If you have both of those, you are well on your way to building a "Bashed Patch". Next - a little bit of setting up...

 

Firstly the second column on the screen currently shows something like "Lo...". In the same way you would if using a spreadsheet, hover your mouse next to that label until you find the vertical bar separating it from the next column (labelled "R"). Click and drag that to the right, until the header says "Load order". Once you can see that, release the mouse click, and then click ON the words "Load Order". The column below, and the associated mods, should organise themselves into numerical order, starting with "00" at the top, and increasing as you go down the column. With me so far?

 

Secondly, right-click anywhere on the bar with the "File" and "Load Order" labels in. A pop-up menu should appear. Remoce the tick from "Lock Times" if there is one, and make sure there are ticks in front of "BOSS disable lock times" and "Always update BOSS masterlist prior to running BOSS".

 

Now, click the BOSS icon at the bottom of the screen. There will be a small popup while the Masterlist updates, and BOSS runs, and then a window will open with the "Better Oblivion Sorting Software Log" in it. Read down it, and you should see familiar mod names, along with some arcane comments about "Bash tag suggestions". Check through the whole list for anything labelled "Error" or "Warning" - these need to be dealt with (or at the very least, understood) before trying to go further.

 

If you close the BOSS log and go back to the Wrye Bash window, you may well find that mods have changed order in the window. BOSS has used its Masterlist to determine what it thinks is the best load order, and adjusted the date and time stamps of the files so that they load in that order.

 

Now, left-click on ANY one of the mods, and press Ctrl+A to select all of the mods. They should all be highlighted. Right-click the highlight, and select "Mark Mergeable" from the Pop-up. After a few seconds, a window will pop up giving a list of the files that Wrye Bash believes can be merged, either partially or fully, into its Bashed Patch file. If they weren't alredy, you may now notice that the text has changed colour for some of the mod names, and the boxes to the left of the names may also have changed colour.

 

Scroll down towards the bottom of your mod list. Ideally right at the bottom, you should find a file marked "Bashed Patch, 0.esp". If this is not present, follow the instructions in the Wrye Bash readme to locate it and copy it (NOT move it) to the correct place, then re-run BOSS.

 

Once you have a Bashed Patch" file, the next stage is to USE it. Right-click the file, and select "Rebuild patch". Another popup will appear (unless you, for some reason, have no mergeable mods)...

 

"The following mods are mergeable. While it is not important to Wrye Bash functionality or the end contents of the bashed patch, it is suggest that they be deactivated and merged into the patch; this (helps) avoid the Oblivion maximum esp/m limit."

 

There will then be a list of mod files, followed by

 

"Automatically deactivate those mods now?"

 

Click "Yes".

 

The next popup has DOZENS of options in the left-hand window. The one we are interested in this first time through is the second item on the list, "Merge Patches". Put a tick in the box next to it, and then tick all of the files which appear in the right-hand window by selecting the "Select all" button. Now click the button marked "Build Patch". A popup will tell you that the program is working, and give you a progress bar.

 

Once completed, another popup will tell you what it did, so just hit "OK". It will probably prompt you to "Activate the Bashed patch" - do so by clicking the box next to it, and a tick will appear. The ticks in some of the other boxes will have disappeared now, or been replaced with + or dot marks. This tells you what their new status is.

 

You may now close Wrye Bash, and run Oblivion, and the whole things SHOULD work just as before, but with less files active, so a smaller load list.

[wgridenour]

I hope I'm in the right place. I need help with the bashed patch. everything seemed to work fine until I downloaded a fix for project Nevada, and for WMX in Fallout NV. when I run rebuild patch it tells me it can be merged, however, all it does is deactivate the patch and it isn't added to my bashed patch,,

 

in both cases the patches are deactivated and not merged. am I doing something wrong or do I simply ignore them for the bashed patch.when I run the merge it says they can be merged but it deactivates them not merges them everything else shows merged.

 

never mid I figured it out

[lubronbrons]

me too, happen to get mod not merged correctly.
the trick is.... my routine for this problem is,

before you do bashed patch make sure you block ALL MOD then, hit 'space' button to make sure all mod is activated

after that you should use BOSS to sort it out

this is crucial, you must still block ALL MOD then do right click in the blocked area choose 'Mark Mergeable...'

I recommend use normal bashed patch do not use CBASH remember I repeat do not use CBASH because its not that stable

and finally, create bashed patch

done

 

I remember when I try using mod Grass Overhaul, many area of the original Grass Overhaul being missing....

then when I think it again, bashed patch is not directly give a user a hint of solution that : grass should keep minimum for performance but you can see better grass from that mod

IMHO the message from wrye bash & community is like that. to keep it stable as much

so.... the conclusion is : the inactive mod should be activated before you do another bashed patch. if you happen to miss this, the inactive mod will not work and not get merged correctly

Edited November 7, 2015 by lubronbrons