Jump to content
  • 0

Question

I was wondering about overwrite mods in general, eg output from SKSE, FNIS, Bodyslide etc.

Where is the best place for the overwrites, in the sense of load order? Should they be placed with the mods that generate them, or just after any mods that they might effect, or should they go right at the bottom where the original overwrite entry is?  I read somewhere about "dynamic" mods needing to go at the bottom, and I'm thinking that overwrites probably qualify as dynamic.

I've experimented with all of these and it often seems to make little or no difference, but when I've installed a few dozen mods and CTDs start rearing their heads then I start thinking about what various contributing factors there might be.

I've also experimented with the "Create Files in Mod instead of Overwrite" option. Particularly with FNIS which seems happier that way. Without this option ticked I have to run FNIS twice every time I use it, otherwise it says "ERROR(53): Could not find file 'temporary_logs\Skeleton.xml'."  It's like FNIS doesn't know where to look for the xml. Am I doing the correct thing here or is there a better solution?

On a vaguely related topic too ... when SKSE has overwrite data, is it best that it all goes into the same overwrite mod or would it be better to create a different overwrite for each mod that creates the SKSE data? So far I've only done the former and it seems to work ok, but again when I start getting CTDs then I wonder about anything that might be contributing in any way.

Thanks, and sorry if these are daft questions.
 

Share this post


Link to post
Share on other sites

4 answers to this question

Recommended Posts

  • 0

Generally you want to move files out of Overwrite into either the mod that generated the files or into a new mod immediately after the files are created. When you create the bashed bash, the files in Overwrite should go into a Bashed Patch mod. When you run GenerateFNISForUsers, the files should go into a mod named something like FNIS Output. When you run the game the first time, you may find some files in Overwrite created by SKSE and these can be moved into the SKSE mod or into a new mod of your choice. Whichever option you chose isn't that important and I seem to recall that some files from SKSE continue going into Overwrite each time you run the game so I wouldn't worry too much about cleaning these out after every playthrough. It's really more important to ensure Overwrite is clean before generating files that should be moved into a mod (like Bashed Patch, FNIS, etc.) so you don't end up with a mixture of files in Overwrite that's difficult to manage.

 

It's been a while since I've generated the FNIS animations, but I think you're doing it right. I remember the last time I installed FNIS, I ran into similar issues and finally set the option to create files in mod instead of Overwrite.

Share this post


Link to post
Share on other sites
  • 0

Generally you want to move files out of Overwrite into either the mod that generated the files or into a new mod immediately after the files are created. When you create the bashed bash, the files in Overwrite should go into a Bashed Patch mod. When you run GenerateFNISForUsers, the files should go into a mod named something like FNIS Output. When you run the game the first time, you may find some files in Overwrite created by SKSE and these can be moved into the SKSE mod or into a new mod of your choice. Whichever option you chose isn't that important and I seem to recall that some files from SKSE continue going into Overwrite each time you run the game so I wouldn't worry too much about cleaning these out after every playthrough. It's really more important to ensure Overwrite is clean before generating files that should be moved into a mod (like Bashed Patch, FNIS, etc.) so you don't end up with a mixture of files in Overwrite that's difficult to manage.

 

It's been a while since I've generated the FNIS animations, but I think you're doing it right. I remember the last time I installed FNIS, I ran into similar issues and finally set the option to create files in mod instead of Overwrite.

Thanks for your comments.

 

Yes, I do move stuff out of the overwrite folder every time. I was just wondering about where is the best place to put my output mods once I've made them. I don't know if they belong with (i.e. immediately beneath) their "parent" mods, or if they should go at the bottom of the list just above the overwrite folder. Or even whether it makes any difference at all.

Share this post


Link to post
Share on other sites
  • 0

That only ones I can think of off the top of my head that really matter are the smashed/bashed patch, FNIS output, Dual Sheath Redux patch, TextGen and DynDoLOD. These should all go towards the bottom in the order generated. The files created by SKSE are basically log files so I usually just move these into the SKSE mod since order doesn't matter.

Share this post


Link to post
Share on other sites
  • 0

That only ones I can think of off the top of my head that really matter are the smashed/bashed patch, FNIS output, Dual Sheath Redux patch, TextGen and DynDoLOD. These should all go towards the bottom in the order generated. The files created by SKSE are basically log files so I usually just move these into the SKSE mod since order doesn't matter.

Thank you, this is all very helpful.  At the moment I have my outputs (FNIS and Bodyslide and SKSE) almost at the bottom except for a dozen or so compatibility patches and a couple of mods where the authors say that they need to be last (XPMSE and Alternate Start).  I only just started using Wrye Bash yesterday and I've put that with the other outputs.

 

Touch wood and not wishing to jinx anything but I seem to have a relatively stable game right now : )

 

Thanks for your input.

 

(edit, not sure how I quoted myself here but I can't seem to remove it now. Ah well.)

 

Thank you, this is all very helpful.  At the moment I have my outputs (FNIS and Bodyslide and SKSE) almost at the bottom except for a dozen or so compatibility patches and a couple of mods where the authors say that they need to be last (XPMSE and Alternate Start).  I only just started using Wrye Bash yesterday and I've put that with the other outputs. I'll put the SKSE one back with its parent then, if it doesn't really matter. Just to keep things tidy.

 

Touch wood and not wishing to jinx anything but I seem to have a relatively stable game right now : )

 

Thanks for your input.

 

 

Edited by NikiRandom

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 sheson
      DynDOLOD DLL beta for Skyrim, Skyrim Special Edition and Skyrim VR
      So far all versions of DynDOLOD use the SKSE plugin PapyrusUtil for the optional dynamic LOD in the game. Starting with version 2.45 there is now the alternative DynDOLOD DLL available.
      The current DLL version is 2.45. It works with dynamic LOD generated by DynDOLOD Standalone 2.45 and newer.
      Read the ..DynDOLOD\Docs\DynDOLOD_DLL.html included in DynDOLOD Standalone for an explanation about DynDOLOD DLL, installation instructions (overwrite papyrus scripts of DynDOLOD Resources) and how it works.
      If there are problems with it, check DynDOLOD_DLL.html and the DynDOLOD FAQ first before posting.
      If a DynDOLOD.DLL version is required for a game version that is not listed below, request it in this thread. First, search this thread if it has been requested already, though. The future will tell how long it takes to release updates.
      Typically a new DynDOLOD.DLL is required for each new game version, but not each new SKSE version. For example a DynDOLOD.DLL compiled with SKSE64 2.0.9 also works with SKSE64 2.0.10 for the same game version.
      Nexus Downloads for DynDOLOD 2.45 and higher
      DynDOLOD DLL for Skyrim
      DynDOLOD DLL SE for Skyrim Special Edition
      DynDOLOD DLL VR for Skyrim VR
      Mega Mirrors:
      DynDOLOD.DLL + Scripts for Skyrim 1.9.32 (overwrite the papyrus scripts included in DynDOLOD Resources)
      DynDOLOD Scripts for Skyrim Special Edition and Skyrim VR (overwrite the papyrus scripts included in DynDOLOD Resources SE)
      DynDOLOD.DLL for Skyrim Special Edition 1.5.39
      DynDOLOD.DLL for Skyrim Special Edition 1.5.50
      DynDOLOD.DLL for Skyrim Special Edition 1.5.53
      DynDOLOD.DLL for Skyrim Special Edition 1.5.62
      DynDOLOD.DLL for Skyrim Special Edition 1.5.73
      DynDOLOD.DLL for Skyrim Special Edition 1.5.80
      DynDOLOD.DLL for Skyrim Special Edition 1.5.97
      DynDOLOD.DLL for Skyrim VR 1.4.15
    • By qwrtui1245
      Hi, 
      I'm modding SkyrimSE with MO2 by following this version of the step guide: https://stepmodifications.org/wiki/SkyrimSE:1.0.0#04-Foundation. I've followed everything until now but experience problems with the first mod I need to install without using Nexus. It's Skyrim SE particle patch for ENB and I downloaded 'SPECIAL EDITION > ALL-IN-ONE INSTALLATION > LATEST VERSION (GOOGLE DRIVE)'. It's installation went fine (Situation A) but when I have to enable the optional ESP 'Particle Patch for ENB SSE.esp' I get the message 'Plugin not found: Particle Patch for ENB SSE.esp' in my log (Situation B). 
      I've tried: reinstalling the mod, refreshing, enabling and disabling the mod, restarting MO2, re-downloading the file. It doesn't fix my problem. I've added the pictures of situation A and B. I hope there are people who can help me here. Thanks so much in advance!
      Situation A

      Situation B

       
    • By Newtant
      Hello!

      I've stumbled upon a weird issue that I haven't encountered or read about before. I'm running Windows 8.1 and a fresh install of Fallout New Vegas with no mods so far. I'm trying to get Mod Organizer and the 4GB exe to work together, but despite following all of the advice, tips and workarounds it's still not happening. Right now I can launch the 4GB exe through Mod Organizer. The game starts, I can load a save and 'play'. The problem is that all of the text has disappeared or is invisible. I can only navigate the main menu by memory, the ingame popups regarding the DLC is missing the text as well.

      This issue does not happen if I start the game on its own with the normal exe.
      This issue does not happen if I start the 4GB exe on its own.

      It only happens if I start the either the normal or the 4GB exe through Mod Organizer.

      NVSE is being loaded, it doesn't matter if I'm using NVSE stable or beta.
      I'm using NVAC, without it the game crashes before arriving at the main menu. NVAC seems to be working, the log is showing several handled errors. (Pastebin)
      Yes, I've added '-laaexe .\FalloutMO.exe' to the launch arguments, that helped me get around the access is denied error but produced this text error.
      I did try compatability modes, I've tried starting MO, the 4GB or both as administrator. No dice.

      I've arrived at a point where I really don't know what it could be or what I could try next. One thing I do know, however, is that I can't go back to the pre-MO modding, so I'm turning to you helpful people and hope that someone here has an idea.

      Thanks in advance!
       
      Pictures:
      New Vegas installation folder
      Mod Organizer executable settings
      Disappeared text main menu #1
      Disappeared text main menu #2
      Disappeared text ingame
       
      Edit:
       
      I deleted all of the fallout .inis as well in case some of my text/font settings were messed up, but that didn't work either.
  • 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.