Jump to content
  • 0
Yuriwa

My bashed patch (in overwrite) contains only a text and html file.

Question

There's no plugin. There should be one, right? So, when I put those files in their own folder, as you would a mod, MO shows it as empty, and presumably it does nothing.

Honestly I have never used a bashed patch before and I'm only forcing myself to try it out now because it seems more important for Fallout NV because of the lower plugin limit. And so, it's likely that I'm missing something really obvious. I have done my best to follow the STEP guide F&L to the letter.

The whole thing with that there are bashed patches, and also merge patches, and merging with FNEdit and also with Merge Plugins Standalone is super confusing to me.

My game is largely working but there are some red exclamation marks around the gas station in Goodsprings, and I had tried to add Niner to the setup, and he had one too, so I've just removed him for the time being. Preferably I'd just figure this thing out properly rather than just jury rig it.

Please, can someone shed some light on this? I'll answer questions about important information that I left out.

Thank you.

Share this post


Link to post
Share on other sites

10 answers to this question

Recommended Posts

  • 0

h8 to be that guy but you did something wrong m8. Programs that run From Mod Organizer are set up in MO under the top right drop down list. When you run LOOT, Wrye Flash...etc, you do that from that drop down list in MO.  If I were you I would start over and check everything you have went thru :( Read the guide again. Especially from here: Section 2 Utilities  I know. A pain. While reading the guide you will come across NOTES that pertain to steps for Mod Organizer. Same thing with section 2 Utilities.

 

When you install these apps you will Also be setting them up in Mod Organizer with arguments to go with them. In the drop down list on the top right of MO there will be a thing called: <Edit>:  =click that and that is where you setup the programs. (Loot, FnvEdit..etc) Don't forget to click "Add" when you do the edits and name it :)

 

I don't understand when you say you have put mods in their own folders. When You install a mod in MO, MO does that for you. The folders themselves will be in ...\Mod Organizer\Mods\.  Just like the Downloaded mods that you used for NXM Links will be in ...\Mod Organizer\Downloads\ In Mod Organizer itself... they will be the list on the Left Side(Installed Mods). You don't need to bother with the folders in windows explorer. When you double click one of those mods on left side you are basically tinkering with them like you would in windows explorer... just a different User Interface with more options. After you run Wrye Flash in MO and do a Bash Patch, the patch will most likely end up in the OVERWRITE folder (@the bottom of MO's Left Pane List). Right click on Overwrite and name it what you want. Bash Patch Date and Time is what I name it. Or any other patches that end up in there.

 

There should not be any errors in your game after following the guide. So. Read that section 2 and make sure MO is setup right. If you Downloaded everything then just go through and make sure you didn't "look over" some Notes. I hope I am not confusing :/ We'll be here if I was :) Oh and don't worry about being overwhelmed. Everyone says that at first :P It will come and you will be better off :D 

Share this post


Link to post
Share on other sites
  • 0

I'm running all of my programs through MO, and that includes Wrye Flash NV. I don't mind you pointing it out though, I appreciate it in fact, but yeah, I know at least that much.

My confusion lies in the fact that I'm led to believe by the guide that the bashed patch contents will appear in the overwrite folder after creating the patch. Well, files do appear, but they aren't files that do anything. Only a text file and an html file. I'm just wondering if this is expected behavior or not, and I suspect it's not. Shouldn't there be a plugin inside? That is all I meant by putting mods in folders: Make a mod out of the overwrite folder contents.

Share this post


Link to post
Share on other sites
  • 0

Ah ok. I'm glad :) Makes things easier. Those files are the Bash Patch. Or at least what is not the esp. I would right click on the overwrite tab at the bottom and hit create mod. Name it Date of Patch and leave it at the bottom of the list. Whenever I do patches of anything that end up in the overwrite folder/tab, I do that. Though they should be with the "Bash Patch.0.esp". Which ever folder you created for that if any.

 

Even if you run the game with files in the overwrite folder it will be essentially the same. AND you should not have errors :/ That's why I suggested going back through and double checking. Things in the Overwrite folder have precedence over everything else. Hence the name. It will overwrite anything that comes before it.

 

EDIT: Bash Patch 0.esp is in the Load Order on the Right Hand Collum under "Plugins" tab? Along with the other mods including ones that Wrye Flash Disabled/Merged?

Edited by AyleidRuin

Share this post


Link to post
Share on other sites
  • 0

I'm running all of my programs through MO, and that includes Wrye Flash NV. I don't mind you pointing it out though, I appreciate it in fact, but yeah, I know at least that much.

 

My confusion lies in the fact that I'm led to believe by the guide that the bashed patch contents will appear in the overwrite folder after creating the patch. Well, files do appear, but they aren't files that do anything. Only a text file and an html file. I'm just wondering if this is expected behavior or not, and I suspect it's not. Shouldn't there be a plugin inside? That is all I meant by putting mods in folders: Make a mod out of the overwrite folder contents.

No, you're not confused about what should and shouldn't happen.

However there are now situations where the bashed patch is created in the real Data folder when you install WB and because it exists there, that file is modified and remains where it is.

 

Basic rule of thumb with MO and its 'Overwrite' folder: If the file exists, edit it and keep it where it is. If the file is a new creation, place it in 'Overwrite' and let the user determine where it goes.

 

You can verify this behaviour with your bashed patch by moving the current file into a new folder in MO's 'mods' folder and name the folder appropriately, based on the current profile.

Now create a new file in Explorer and examine the filesize. Run Bash again and then compared the sizes of the two files. The newly edited patch will now no longer be of 0 length.

 

Keeping the patch in the real Data folder is no problem until you try and run different profiles with different settings. The same patch will be overridden each time, which is why moving it into a new mod folder is a good habit.

Share this post


Link to post
Share on other sites
  • 0

No, you're not confused about what should and shouldn't happen.

However there are now situations where the bashed patch is created in the real Data folder when you install WB and because it eists there, that file is modified and remains where it is.

 

Basic rule of thumb with MO and its 'Overwrite' folder: If the file exists, edit it and keep it where it is. If the file is a new creation, place it in 'Overwrite' and let the user determine where it goes.

 

You can verify this behaviour with your bashed patch by moving the current file into a new folder in MO's 'mods' folder and name the folder appropriately, based on the current profile.

Now create a new file in Explorer and examine the filesize. Run Bash again and then compared the sizes of the two files. The newly edited patch will now no longer be of 0 length.

 

Keeping the patch in the real Data folder is no problem until you try and run different profiles with different settings. The same patch will be overridden each time, which is why moving it into a new mod folder is agood habit.

So wrye flash put the relevant data directly into the bashed patch residing in the data folder? That's the part I didn't understand. So I can take that out and create a mod with it? Will wrye flash know to use the same file again if I ever have to rebuild the patch?

 

Also, wrye flash suggested I untick several mods prior to the creation of the bashed patch, "because they are mergeable", and the guide mentions this, so I complied with it. But am I supposed to retick those mods afterwards? Because I've tried not doing that, and one of them was Roberts' body mod, and it's active in game.

Share this post


Link to post
Share on other sites
  • 0

Bash patch, text file and Html file will be in the overwrite or in their own folder on left pane.  They'll be created each time you do a bash patch. So far I am aware of 2 mods that show up purple. Wrye Flash will ask to disable/untick those mods(hit Yes)->Run bash Patch->then Re enable those two mods.(WMX..Texture.esp AND MiscItemIconNV.esp) The other mods in green, you leave disabled for those are now merged in the bash patch.

Edited by AyleidRuin

Share this post


Link to post
Share on other sites
  • 0

Bash patch, text file and Html file will be in the overwrite or in their own folder on left pane.  They'll be created each time you do a bash patch. So far I am aware of 2 mods that show up purple. Wrye Flash will ask to disable/untick those mods(hit Yes)->Run bash Patch->then Re enable those two mods.(WMX..Texture.esp AND MiscItemIconNV.esp) The other mods in green, you leave disabled for those are now merged in the bash patch.

The bashed patch wasn't in either the left pane or in the overwrite folder. That's why I made this thread. Those 2 purple items, and the green merged items are mentioned in the guide and aren't what I'm asking about. I'm asking about these:

 

 

 

 

  • If there is a pop-up that saying certain mods will be disable because they are mergeable, click [Yes]. If not disregard.

I got the popup, and I clicked yes, and now I'm wondering what to do with them.

Share this post


Link to post
Share on other sites
  • 0

Your good. Ignore it. They will be disabled in the Right pane / "plugins" tab. Because they are now merged in the Bash Patch.  I'm sorry if I keep misreading your questions. I do go over posts a lot before I attempt to answer them. But you see what you want to see I guess :P

Share this post


Link to post
Share on other sites
  • 0

Your good. Ignore it. They will be disabled in the Right pane / "plugins" tab. Because they are now merged in the Bash Patch.  I'm sorry if I keep misreading your questions. I do go over posts a lot before I attempt to answer them. But you see what you want to see I guess :P

No, these weren't merged, because when I chose "build merge", wrye told me they would best be unchecked, and the guide's instructions are to follow that advice and uncheck them. However, the guide never goes on to mention them again, as far as I can tell, anyway.

 

Actually I discovered the answer while playing. The game ran fine, but I couldn't complete Willow's Beauty quest (item wouldn't drop) until I checked these mods again.

 

And np, we all do that from time to time, it's still good to bounce ideas back and forth. I think I got all my answers. Thanks for your help.

Share this post


Link to post
Share on other sites
  • 0

I did a video for guys having exactly this problem. I uninstalled Wrye Bash and deleted the BP in a perfectly working Skyrim SE mod Organizer 2 build. Then I show how I install Wrye and the Bashed Patch is created automatically in the real Data folder. Worked like a charm:

 

https://youtu.be/BSYIquLOtO8

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

  • Similar Content

    • By Majorman
      Discussion topic:
      FNVLODGen by zilav
      Wiki Link
    • 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 Majorman
      Discussion topic:
      ShowOff NVSE Plugin by The Dormies - Demorome and Trooper
      Wiki Link
  • 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.