Jump to content

z929669

Administrator
 View Profile  See their activity

  • Posts

    13,028

  • Joined

  • Last visited

 Content Type 

Everything posted by z929669

  1. z929669
    The very top of the guide explains the requirements. You will need to purchase the AU update as instructed there. It's only $7 now I think. See this for a technique to remove masters if you for some reason can't get the AU update. But we don't support running without it.
  2. z929669
    Only update object LOD if you want to try the lastest. There's no need if you already have a working build/playthrough. I would always regen TexGen though, since it only takes a few minutes.
  3. z929669
    Step always uses the latest, so regenerate if you are moving to 112/Alpha4
  4. z929669
    If you are logged into MO (or presumably Vortex), you should get the download in the mod manager when clicking that link. As I said, it works for me and others, so not sure what's going on with that. It's like any other Nexus mod when you click the "Download with mod Manager" button on a file.
  5. z929669
    Thanks. Mod page updated to reflect.
  6. z929669
    It works fine. You should have a Nexus user account and be logged into Nexus as your user, which is mentioned in our guides (System Setup Guide).
  7. z929669
    Sorry if I added confusion. My hands are in quite a few pots these days, and I just didn't have the time or the inclination to sort out the script or it's logic to lend anything useful to your analysis and was merely asserting that inference based on a script should be cautionary. That's all. Elminster is a reliable authority though, so I should probably just have stayed out of this. All we can do is infer, true, but @Mousetick DID take the time to work out the script's logic to lend to your analysis (see best answer up top ... I marked it, since it seems to address your original question best. You can confirm or deny by upvoting or downvoting). He's usually quite thorough and accurate in my XP, so I think you'll find his response useful.
  8. z929669
    I'm not familiar with that script, but I quickly looked through your post, so I'm assuming that your analysis is basically accurate. Regardless, one cannot necessarily infer hard rules based on a scripted procedure. It depends on if the script was written to conform to the hard rules or if it was written to conservatively process with some padding or other calls made by the author. So you could post over on AFKmods with your question, pointing them to this evidence. Then let us know.
  9. z929669
    In MO, all you need to do is right click any vanilla DLC and disable it. You don't need to remove it that way, so Steam will be happy. Then note any MO messages: Our patches don't rely on this plugin, but the USCCCP does. I think that mod lets you install each DLC separately if you want, so you could install it that way or just tweak it yourself in xEdit. I would also check everything in xEdit once finished to be sure nothing strange is happening, but it's most likely fine with that mod.
  10. z929669
    I would find any and all relevant patches for these and load only the new lands mods without anything else. Just those and vanilla (and whatever dependencies those mods need), along with standard runtime mods like SKSE Address Lib, etc. Then I would sort out all of the conflicts myself using xEdit into a custom patch. The third-party patches may have some good reference info for this. Then I would install all of the other mods I wanted to use and modify my patch.
  11. z929669
    From the Crash Logger Nexus page: You almost certainly installed a mod incorrectly (e.g., disabling plugins as instructed or using an incorrect mod file from Nexus) or did not sort with LOOT or did not enable all plugins in the right pane. Did you pass the smoke test near the beginning of the guide? If so, that rules out 02-Extenders mods. You can resolve by disabling mods in blocks, re-sort with LOOT and test new game until you narrow down to one mod causing the issue. Disable last half of all mods, test, disable first have, test, and so on.
  12. z929669
    That's correct. Mod page updated.
  13. z929669
    Not much can be done to help until you post your relevant logs as described in the parent forum and the DynDOLOD OP
  14. z929669
    I think it's obvious if you carefully read the OP I linked that you have downloaded the incorrect resources for VR. Either that, or you have another incorrect dependency. One of your DynDOLOD dependencies is the incorrect version, and the only way to resolve is to read, since we don't have any details in the OP.
  15. z929669
    The link works fine, and the file can be downloaded. If it's having issues, it's probably a Nexus thing. Here's the Mega Link
  16. z929669
    Please see the DynDOLOD support topic and read that OP carefully
  17. z929669
    There won't be any performance improvement, because at game runtime, all plugins are effectively being merged anyway (in load order). The advantage of merging them yourself is that you will have presumably made better decisions by doing it yourself. But that's a lot of work. The only reason to merge would be to avoid the plugin cap, which is largely alleviated anyway with many mods being ESL format. Merging plugins doesn't resolve conflicts, BTW. Merging and resolving conflicts are two different actions. You would first resolve conflicts and then merge the remainder in order of load priority.
  18. z929669
    Disable all non-Step-2.2.0 mods, DynDOLOD Output, and DynDOLOD Occlusion mods. Check the config against the guide, and re-sort with LOOT. Be certain that messing with in-game Mods didn't reset your CC mods or other vanilla plugins (LOOT should show no warnings). Then test a new game.
  19. z929669
    I'm not familiar with a lot of those mods, and I see you are using some mod-specific compatibility patches, but a couple of observations: It's a large plugin list I don't see a 'build' patch near the end of the load order For large mod lists incorporating lots of different overhauls, you really should be using a custom 'global' compatibility patch specific to your plugins. Modpocalypse and Complete NPC Overhaul stick out. You are sure to have some odd things without a patch. Also, scripting gets baked into your saves, so you would probably need to consider patching and starting a new game.
  20. z929669
    https://dyndolod.info/FAQ "Long running time or output several GB in file size" Please review the OP, too.
  21. z929669
    It's a great game, but never used that guide
  22. z929669
    Good changes. Thanks. I did tweak verbiage in two places and punctuation in one place
  23. z929669
    Instructions updated to reflect
  24. z929669
    I disagree that the instructions are implicit but rather they are explicit and fairly obious, and I feel the need to push back on adding additional instructions redundantly. Anything we take the time to write is "easily missed" by many people, and there is no way to avoid that. Adding redundancy is just more maintenance for us. The guide includes images of the GUI settings recommended using color coding for context The link to ACMoS in that DynDOLOD section of the guide points to our mod page, yes, but our mod pages also link to the corresponding Nexus mod pages, so anyone really following the guide has all information at the ready. I really don't think adding yet more text for people to not read does anything but make more people not want to read even more text. I don't think it gets any clearer than it is, and with links to the Nexus and wiki mod pages conveniently provided, there's nothing more to do.
  25. z929669
    Does the dark face get corrected when disabling ENB via Shift+F12?
×
×
  • Create New...

Important Information

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

  I accept