Jump to content
  • 0
Sign in to follow this  
Reytag

Specifics on Merge and Bashed Patches

Question

I have followed most of the guide, watched many video tutorials and read many articles on merge and bashed patches yet still have a few questions.

 

One of the reasons for this is a lack of consensus on what is the correct method and another is that many videos do not pertain to Fallout 3 specifically, many bashed patch videos for exampled are for Skyrim and not being an expert I do not know for sure whether or not the steps for one game are exactly the same as another, it could be either way.

 

My reason for unfortunately wanting (well, needing) to complicate my life is that the "general consensus" is that it is best to use both types of patches although one or the other "would do".

Me being me I strive for perfection even if it isn't needed.

 

What I have been able to find out is that first one creates a merge patch in F03Edit and remove the leveled lists from it.

 

Next you create a bashed patch, this is where the confusion starts as most articles seem to approach this as though its only the bashed patch being created, not that a merge patch was created beforehand, or, I have to at least assume this as none of them ever state whether a merge patch was created before or not.

 

What I want to do is therefore create a bashed patch the proper way but taking into consideration that the merge patch was created first.

Additionally, I do NOT want to merge plugins in Wrye Flash.  Why, because it requires disabling said plugins in the mod manager and while testing this is irritating as you have to keep track of why they are unchecked, was it because they are now merged or because you simply have disabled them for various testing scenarios.

I also never plan on having so many mods that I reach the Fallout 3 limit where plugin merging would be required.

 

Now on to the main questions, taking the above into account.

 

1. I assume when creating the bash patch that the merge patch plugin should be checked and enabled in the load order and therefore included in the bashed patch, or not, I saw this once somewhere, just wanting to confirm.

 

2. Which items need to be selected in the left and right panes.  What doesn't help here is that your guide, other articles and videos do not have a general consensus on which should be checked or not, everyone "does it a little different" and nobody states whether a merge patch has been created beforehand or not (in the case of your guide I am almost 100% positive you are only creating a bashed patch).

Do I follow your guides list of "check all except the few listed" regardless of whether a merge patch exists or not or do I have to leave additional categories unchecked?

One video guide mentioned, "as long as there are entries on the right pane, check all those as well as the box on the left pane for which category they fall under".

I have noticed that Wrye Flash will show on the right plugins that you do not actually have enabled in the mod manager anyway.

Common sense would tell me that those should of course be disregarded completely and if those are the only plugins in a certain category then that category on the left would remain unchecked, is that correct?

 

3.  I assume the "Merge Patches" box is not required since I am choosing not to merge and this box in the left pane is only required for that purpose.

 

4.  If no plugins are actually listed on the right would one not leave that category unchecked also on the left?

 

I really did look several days for the answers to the above without any luck, maybe they are too specific and in general nobody cares, am I being too exact?

 

Nonetheless, if you could shine some light and answer a few of the above questions that would be great and enable me to mod my game in as precise a manner as possible.

 

Thank you, especially for having taken the time to write your guide for the benefit of the community in the first place.

Edited by Reytag

Share this post


Link to post
Share on other sites

4 answers to this question

Recommended Posts

  • 0

I have followed most of the guide, watched many video tutorials and read many articles on merge and bashed patches yet still have a few questions.

 

One of the reasons for this is a lack of consensus on what is the correct method and another is that many videos do not pertain to Fallout 3 specifically, many bashed patch videos for exampled are for Skyrim and not being an expert I do not know for sure whether or not the steps for one game are exactly the same as another, it could be either way.

Wrye Bash and Wrye Flash work the same way and the videos apply to both. There are only a few small differences, and these are primarily in the list of "bash tags" each supports.

 

My reason for unfortunately wanting (well, needing) to complicate my life is that the "general consensus" is that it is best to use both types of patches although one or the other "would do".

I have no idea what you mean here by both types of patches; see comment at bottom.

 

Me being me I strive for perfection even if it isn't needed.

 

What I have been able to find out is that first one creates a merge patch in F03Edit and remove the leveled lists from it.

The FO3Edit training manual describes creating a "Merged Patch" using a combination of FO3Edit filtering and manual conflict resolution; typically many of these would need to be created. These techniques can be used to create compatibility patches. Most users start with the automated capabilities of Wyre Bash/Flash since it handles a large part of what otherwise needs to be done manually. Additional compatibility patches can be created manually using FO3Edit to handle what the bashed patch was unable to handle. These patches can be built so they can be loaded before the bashed patch and merged by Wyre Flash (usually bash tags need to be added to support this), or they can be loaded after the bashed patch if they have resolved all the conflicts (including the levelled lists) for all the plugins they handle. The patches in the "Wasteland Patch Collection" included in the guide are such patches.

 

Next you create a bashed patch, this is where the confusion starts as most articles seem to approach this as though its only the bashed patch being created, not that a merge patch was created beforehand, or, I have to at least assume this as none of them ever state whether a merge patch was created before or not.

See comment at bottom of response. Wrye Flash only creates a bashed patch.

 

What I want to do is therefore create a bashed patch the proper way but taking into consideration that the merge patch was created first.

Additionally, I do NOT want to merge plugins in Wrye Flash.  Why, because it requires disabling said plugins in the mod manager and while testing this is irritating as you have to keep track of why they are unchecked, was it because they are now merged or because you simply have disabled them for various testing scenarios.

I also never plan on having so many mods that I reach the Fallout 3 limit where plugin merging would be required.

 

Now on to the main questions, taking the above into account.

 

1. I assume when creating the bash patch that the merge patch plugin should be checked and enabled in the load order and therefore included in the bashed patch, or not, I saw this once somewhere, just wanting to confirm.

See comment at bottom. There is no "merge patch plugin".

 

2. Which items need to be selected in the left and right panes.  What doesn't help here is that your guide, other articles and videos do not have a general consensus on which should be checked or not, everyone "does it a little different" and nobody states whether a merge patch has been created beforehand or not (in the case of your guide I am almost 100% positive you are only creating a bashed patch).

Do I follow your guides list of "check all except the few listed" regardless of whether a merge patch exists or not or do I have to leave additional categories unchecked?

The other categories are not affected by whether Merge Plugins is checked. They are typically used to tell Wrye Flash what kinds of objects it should evaluate when providing automated conflict resolution.

 

One video guide mentioned, "as long as there are entries on the right pane, check all those as well as the box on the left pane for which category they fall under".

This isn't always true. The guide would note such situations if they occurred.

 

I have noticed that Wrye Flash will show on the right plugins that you do not actually have enabled in the mod manager anyway.

Common sense would tell me that those should of course be disregarded completely and if those are the only plugins in a certain category then that category on the left would remain unchecked, is that correct?

No. Wrye Bash is a full mod manager that can be used instead of Mod Manager. Part of this capability allows enabling/disabling plugins. STEP used Mod Organizer instead for most purposes since its ability to support multiple sets of mod configurations (called profiles) is extremely useful.

 

3.  I assume the "Merge Patches" box is not required since I am choosing not to merge and this box in the left pane is only required for that purpose.

Yes

 

4.  If no plugins are actually listed on the right would one not leave that category unchecked also on the left?

I would leave it checked in case plugins are later added that will be merged

 

I really did look several days for the answers to the above without any luck, maybe they are too specific and in general nobody cares, am I being too exact?

The Wrye Flash GUI is described briefly in the "What Symbols & Colours Mean" section of the Wyre Bash General Readme. The "Creating a Bashed Patch" subsection of the guide has pointers to the two Wyre Bash Readme pages.

 

Nonetheless, if you could shine some light and answer a few of the above questions that would be great and enable me to mod my game in as precise a manner as possible.

 

Thank you, especially for having taken the time to write your guide for the benefit of the community in the first place.

I have a question before I can answer several of your questions. You use the term "Merge Patch" as if there were a mod or plugin that is identified as a "Merge Patch". I am not aware of any use of this term by Wrye Flash or Mod Organizer. What do you mean by the term? Wrye Flash does not create a separate "merge patch". When it merges compatibility patches they are included in the bashed patch.

 

Wrye Flash uses the term "Merge Patches" where "Merge" is a verb. This feature allows merging multiple "compatibility patches" into the bashed patch. I understand your reasoning for not wanting to use it, but the benefits are significant. Plugin count is limited in Bethesda games and it helps to reduce the number of plugins needed. In Wrye Flash any plugin that can be merged is shown in green. If the compatibility plugin is merged there is a "+" sign in the box for the plugin. If you don't wan't to use the "Merge Plugins" feature uncheck this box.

Share this post


Link to post
Share on other sites
  • 0

Thanks for the detailed reply, for clarification where I say "Merge Patch" I mean "Merged Patch" as created by F03Edit when leaving all plugins selected, hitting ok and then after it loads right click on left pane, go to "other" menu and then click "create merged patch".  I then name the resulting merged patch and it appears as a plugin which is then put at the bottom of the load order (typically).

 

Therefore by "both types of patches" I mean both the "Merged Patch" created in FO3Edit and the "Bashed Patch" created in Wrye Flash.

 

You actually mention the Merged Patch from FO3Edit right after your bashed Patch section, sorry, I missed the "d" from "Merge(d)" which caused the confusion.

 

It has been mentioned in several places throughout my readings that one can create a Merged Patch and a Bashed Patch and use them together as a "superior" solution to just one or the other.

 

Maybe that will clear things up and influence some text above?

 

I am using FOMM as my mod manager.

Share this post


Link to post
Share on other sites
  • 0

You can create manual patches and the FO3Edit tools used to help build a merged patch can be helpful when building manual patches. I suggest only using manual patches after creating a bashed patch and using FO3Edit to see what is missing. A Merged Patch that doesn't provide conflict resolution is a lot less useful than a bashed patch, so you will not see Merged Patches recommended often on the STEP site.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Content

    • By sheson
      This is a beta of [FNV|FO3|FO4|FO4VR|TES5|SSE|TES5VR|ENDERAL|ENDERALSE]LODGen/Edit with terrain LOD meshes and textures generation.
      This is for experienced mod authors and users that know how to use xEdit, xLODGen or DynDOLOD already.
      Installation and Setup
      Download
      xLODGen beta 85 - based on 4.1.4
      Unzip into a dedicated folder outside of any game and Steam folders or special Windows folders like Program Files.
      (Pro users can merge with existing xEdit installation. Make sure to overwrite older LODGen.exe/LODGenx64.exe TexConv.exe/TexConvx64.exe in Edit Scripts. All other files with the same filenames are the same as the latest version of xEdit.)
      Rename xLODGen.exe to [game mode]LODGen.exe (TES5LODGen.exe for example) or start with command line parameter -fnv, -fo3, -fo4, -fo4vr, -tes5, tes5vr, -sse, -enderal, -enderalse
      Use -o:"c:\OutputPath\" command line parameter to change where files are generated to, default is the game folder.
      Do not generate into any game or any mod manager folders.
      Requirements
      Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 - Required by LODGen.exe/LODGenx64.exe and Texconv.exe/Texconvx64.exe. Get matching platform x86/x64 depending on which xLODGen.exe (x86) or xLODGenx64.exe (x64) is used.
      RTFM and Share Results
      See the included Skyrim-Occlusion-Readme.txt for a brief explanation of the Skyrim TVDT Occlusion data generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions or give feedback in the dedicated Skyrim TVDT - Occlusion Data thread.
      See the included Terrain-LOD-Readme.txt for a brief explanation of the settings for terrain LOD generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions about terrain LOD in this thread for a more in-depth explanation if required and share feedback (with screenshots) about results or problems.
      These tools generate LOD meshes and textures "exactly" like CK, but not like the meshes and textures which are shipping with the games (they are often manually edited).
      However, these tools provide more options and higher resolutions (use the x64 version if there are memory errors because you believe you require 4k or higher) and can be updated to add more useful features and options.
      I did some testing in the different games, but finding the best combinations of options and settings requires lots of testing and are a matter of personal opinion and which game is used, the load order, mods, even different worldspaces probably.
      That means, I am only able to give generic guidelines and hints to send you off to find and test for yourself and share your results. My main interested is that generations works correctly and without problems for now.
      Check out the thread xLODGen Terrain Settings Compare. Also refer to any modding guide which has a list of relevant mods close to your load order.
      The object and tree LOD generation is the same as the current versions of xEdit / xLODGen. Refer to their respective descriptions and explanations.
      Obviously, users of Skryim/Enderal/Skyrim SE/Skyrim VR/EnderalSE continue to use the easier and more comprehensive DynDOLOD for drastically improved object and tree LOD generation and only use xLODGen for terrain LOD (and maybe Occlusion) generation.
      First Time
      Here are suggestion to start without going crazy and that should be quick enough to generate:
      Set quality of meshes for LOD4 to 5 and then +5 for each next level. Or just set levels 8/16/32 to 10.
      Check protect cell borders (yes it fixes the ugly terrain drops at outer cell borders that still exist in Fallout 4).
      Use the max vertices setting only if you want to hard limit max file size.
      In Skyrim Special Edition or Skyrim VR, if you notice terrain briefly flickering when new areas are loading in, set [Display] bEnableLandFade=0 in Skyrim.INI
      Set Optimize Unseen to off for LOD4 for first generation. Start experimenting with a value of 550 with a quality setting of 10 or lower for LOD32 (used for map) and compare coastlines and file size to other settings.
      To quickly generate terrain LOD meshes just for the map, check only terrain LOD Meshes, check the Specific Chunk checkbox and set drop down to 32. Leave SW fields empty for complete map or set SW cell coordinates to same values as a *.btr filename to test a specific area with lots of water, river etc.
      Set texture sizes to 512 for a start. Larger sizes and large world spaces will take a considerable time (like 15 to 30 minutes or more easily). Each higher resolution means quadruple the work.
      Use DXT1 for diffuse and 565 (DXT1 if on Windows 7) for normal maps. If generating for Skyrim Special Edition use BC7. Uncheck mipmaps, raise steepness and Bake normal maps.
      For now, leave the Brightness, Contrast and Gamma at 0 and 1.0 respectively. It seems that only Skyrim CK and Skyrim SE CK are manipulating the intensity of the textures to adjust for the noise.dds and the god awful "improved" snow shader of Skyrim SE (just turn that thing off, really). If textures seem too dark in the game, brighten the noise.dds instead or vice versa. That way you can get perfectly matching LOD textures that look just like the textures in the loaded cells. For Skyrim a good average color of the noise texture seems to be around #C0. See below for a couple noise texture downloads.
      If you want to test larger texture sizes, use the chunk option to limit the number of textures that need to be generated. For example, check [x] Specific chunk, leave the drop down empty and set WS to the lower left cell coordinate of an 32x32 area, like 0, 0. It will then generate all textures up to 31,31. Not all worldspaces have their origin at 0,0 so you will have to check already generated meshes/texture filenames for their lower left coordinates.
      Questions and Feedback
      Obliviously anything related to terrain LOD should be posted in this thread.
      Posts related to Occlusion should be made here.
      Recommended Optionals
      TES5-Terrain-Tamriel.esm (Mega), SSE-Terrain-Tamriel.esm (Mega)
      TES5-Terrain-Tamriel-Extend.esm (Mega), SSE-Terrain-Tamriel-Extend.esm (Mega) - These extend the sea of ghost further to the north (see screenshots)
      SSE-Terrain-Tamriel-Full-Extend.esm (Mega) - Entire map from -96,-96 to 95,96 with northern ocean extension. Useful for mod authors.
      Put in game data folder obviously. Adds back terrain for Skyrim (Tamriel worldspace) at the outer edges so there is no missing terrain meshes/textures when generating terrain LOD for Skyrim.
      Load as early with lowest priority as possible, so that any other plugins overwriting or adding land records or cells with the same coordinates take precedence.
      Only required to be loaded when generating terrain LOD. No harm done when loaded in-game but typically the player can not get close to these areas. There are no effects outside the far away added cells.
      Noise
      Single color flat noise, Adjusted vanilla noise, HD Terrain Noise Texture SE
      Examples for Skyrim. Install to game folder like any other texture mod. The noise texture is applied in-game on top of terrain LOD textures, so no effect for LOD generation.
      Only the red channel is used in case the textures is not a grey channel format. MipMaps are ignored. The textures is tiled 3x3 per LOD quad, e.g. for LOD level 4, the noise texture is repeated 3 times to cover 4 cells, for LOD level 8, the noise texture is repeated 3 times to cover 8 cells and so on.
      Test-Terrain-Tamriel.7z
      For testing terrain LOD distances. Plain color terrain LOD textures for Tamriel with coordinates for every LOD quad. Green for LOD 4, yellow for LOD8, blue for LOD 16 and red for LOD 32.
    • By se7enex
      Lucas Simms himself is missing his arms. I can see his gloves but his actual arms are invisible. I can't even begin to imagine what the fluff could be causing that. I did have issues with .32 and Mausers having big red exclamation marks but that's because it REQUIRES (listed in mod guide as optional) the individual weapon remakes. 

      Springvale Sewers, a AWOP location crashes consistently when I try to enter it. 

       
    • By Dennai
      Is there a way to make GaryBash work with MO in Fallout 3? I tried to use it as executable, but MO wouldn't recognized the Wrye launcher as such. It surprised me, because MO had no problem recognizing the Wrye Bash launcher for Oblivion, but I don't have the same luck with Wrye Flash. When I browse the Moppy folder to try to find the Binary, Wrye Bash Debug is the only application the MO can see.
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.