Jump to content

z929669

Administrator
 View Profile  See their activity

  • Posts

    13,028

  • Joined

  • Last visited

 Content Type 

Everything posted by z929669

  1. z929669
    This is one reason we don't use Root Builder. It adds a layer of unexpectedness and complexity. If you are using it, then things will be probably be different for you than what many of our guide instructions say. I recommend following the guide exactly and not using mods not in the guide.
  2. z929669
    You probably haven't set up xEdit according to tools setup.
  3. z929669
    You couldn't have cleaned all 44, because most of them are Anniversary Upgrade masters. But yes, you get the idea. You just need to do a bit of additional work but not everything. I recommend re-reading and verifying everything though. There's a lot of detail and small things that could otherwise be missed (including mod instructions).
  4. z929669
    Then continue following the SSG to download the CC content from within the game. Then go to Step 2 of the guide if you have MO and other SSG programs already installed as instructed. You will need to clean the 44 vanilla masters next probably.
  5. z929669
    Yes, you need to purchase the AU to get all of the CC mods required. Otherwise, the Step Patches won't work, and you will need to modify them yourself, which is no simple task.
  6. z929669
    Look at the big warning box at the top of the guide. Follow the SSG in Step 1 In the SSG are instructions for ensuring a clean vanilla game folder and downloading the Creation Club mods. Then in Step 2 of the guide are instructions for cleaning the vanilla masters. It looks like you just need to revisit the guide and read through it carefully, following all instructions. You don't need to re-download all the mods or anything. Just leave MO alone while you get the vanilla game folder in order (Steps 1 & 2 of the guide).
  7. z929669
    Not sure how it happened, but many of your plugins are disabled. Please enable them all. Then sort with LOOT, and show the result using your video method.. Read any remaining messages in the warning icon at upper right to resolve those issues. Once sorted with LOOT, the highest-priority plugins should look like this: Also note taht some of your plugins have warning icons. Hover over those icons for hints.
  8. z929669
    Carefully re-read the Step Patches in the guide. Install those required using the Step Patch - Conflict Resolution instructions. Ensure that the mods (left pane) and their plugins (right pane) are enabled. Then repeat grass cache generation steps once the warning is gone. The mod warnings appear to be related to the improper versioning of those mods on Nexus, which is a common problem. They can be ignored, or you can edit the meta.ini in each to make version = newestVersion, but that doesn't really matter unless you want to know when the MAs update those mods and fix their versioning issues.
  9. z929669
    Lets ignore the grass cache error for now. I presume you are running the clean & pure SkyrimSE 2.3 build as instructed by the guide? You have MO warnings: First step is clicking on the icon at upper right to resolve those issues. Probably missing masters. SSE Engine Fixes, DynDOLOD Resources, Realistic Wolf Howls, and several other mods have warnings. Hover over these warning icons to discover the issue.
  10. z929669
    bake normal maps is a general setting that applies to all levels. That screen is only different because this setting was ticked for some reason when capturing it. Maybe the other three were updated and this one wasn't, IDK. I'll fix this eventually. Moved to the xLODGen topic, since this is not an issue with the Step guide.
  11. z929669
    The changes were due to forwarding USSEP changes (like the damage mult for khajiits). I don't recall intentionally making dark elves shorter, so that may have been my mistake. I've corrected this in my instance for next update. Regarding the brows, I'll defer to Tech on what to do here. LCR made the departure, but I didn't find anything specific about that in the mod Description, so I went with the USSEP changes (Dawnguard vanilla default). Here's the ref:
  12. z929669
    I've only heard something like this once, and have no idea why, but it sounds like it 's about unexpected output files in Overwrite or elsewhere or some mod like Root Builder. I don't know what you mean. The grass cache output should be in SKSE64 Output mod if you are following the guide. It does not produce a text file. It creates a grass folder with *.cgid files.
  13. z929669
    You should generate the grass cache but not the grass LOD. You should also use the 'performance' mesh rules suggested when running DynDOLOD. I'll try to improve these instructions. See the latest Post-Relese Changes > Guide notes
  14. z929669
    Did you read the 'Highlights' opening paragraph of the changelog? Are you upgrading from the previous guide or doing a clean install? I'll fix the ACE and aMB-CA notes.
  15. z929669
    Yes. The flames were a bit too orange with all of the constant and ongoing changes to this mod over the past two years. It also has better compatibility with ENB vs no-ENB this way. The ENB was altered to accommodate.
  16. z929669
    You probably switched from using DynDOLOD DLL to DynDOLOD DLL NG. Clean all plugins identified by LOOT as being dirty. This is necessary for DynDOLOD DLL NG to work properly. Disregard incorrect advice about not cleaning vanilla (or any other) plugins. Here's some general instructions.
  17. z929669
    There is SOOOO much misinformation about not cleaning vanilla masters (and any plugin for that matter) of UDRs and ITMs. Just clean them and trust that the xEdit developers know what they're talking about. We haven't had any issues with cleaning plugins of UDRs and ITMs for 12+ years. Let Elminster's quote resound:
  18. z929669
    It looks like I already added CleanSKSECosaves = true on Aug 19 when we released 2.3
  19. z929669
    I don't know enough about SkyPatcher to say. Not sure if it is preconfigured with patches for specific mods and what decisions are made for each conflict. Automated patches notoriously make some arguably 'incorrect' decisions for specific use cases.
  20. z929669
    Can you share a screenshot of your not-removed SKSE saves in the profile? I do have the following change, and I don't see the redundant saves: CleanSKSECosaves = true # Delete SKSE cosaves that have no matching save but I'm not certain where they would be otherwise: %LOCALAPPDATA%\ModOrganizer\{instanceName}\profiles\{profileName} or D:\Documents\My Games\Skyrim Special Edition\Saves
  21. z929669
    This was recently discussed on the Improved Closefaced Helmets topic. xEditQuickAutoClean doesn't fix this one. The Step Patches cure the <Unknown> references in imp_helm_legend.esp, so cleaning it is irrelevant. You can still follow the advice in that post to manually fix, but it isn't necessary.
  22. z929669
    The MA doesn't elaborate at all on why SkyPatcher is required. Mod instructions updated to use the old version until we know what's going on with this one.
  23. z929669
    Now that I don't know. What does skyrim.ini have for sScreenShotBaseName under the applicable MO profile?
  24. z929669
    Exactly. Remember, BethINI Pie launched from MO uses the VFS, and the VFS maps the profile INIs to the standard INI path for the game under the virtualized %USERPROFILE%\Documents\May Games ... Sorry. I see Greg already said as much
  25. z929669
    You can also try the Performance version again, setting Level0 at LOD4, Level1 at LOD8, and Level2 at LOD16 (or leave at Billboard1 at LOD16 with even higher TexGen Ambient). Maybe performance will be better and things will look good.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.

  I accept