Jump to content

z929669

Administrator
 View Profile  See their activity

  • Posts

    13,086

  • Joined

  • Last visited

 Content Type 

Everything posted by z929669

  1. z929669
    I've been missing this one.
  2. z929669
    We use CACO. JK's is a deviation from vanilla, and doesn't meet our mandate for modding the game. Our other mods take care of the issues you mention with respect to the rest of these mods. Install Step SSE and you will see.
  3. z929669
    It may be a small convenience in your workflow, but using your clipboard seems slightly redundant, since MO remembers your custom mod names for a given modID, and those are available for all subsequent files installed from same mod page in the alphabetized dropdown menu when installing the mod and choosing a name. As soon as you install the main file, the name is available for any optionals via that dropdown.
  4. z929669
    I split relevant posts from the RWT topic onto this apt topic.
  5. z929669
    This one looks good, too. Marked for Testing.
  6. z929669
    If I want to create a mod for which I want to have persistent, static object LOD, and this mod is replacing existing statics in SSE, then I do not need to use "Create Mod Mode", correct? This is only for new lands/objects (records that neither SSE or DynDOLOD are aware of) in order to set up the new plugin records with the proper flags for LODGen? Rather, all I need to do is create the full and LOD models using the file-naming and path conventions, and DynDOLOD will take care of the rest? I have read through the doc, but I am still churning around what I have read. My questions will get more intelligent as I understand more. PS: Disclaimer ... my questions may not get more intelligent either way
  7. z929669
    But you posted this: There are no file paths to change if you use the same exact tools and the same exact game folder name for each version. You also need to launch both versions with the launcher on first launch to establish proper reg and INI settings. Check your game folders to ensure that they have all of the correct game files and that EXEs are correct versions (right-click > properties)
  8. z929669
    Carefully read the relevant OP in the DynDOLOD forums, download the correct files, and install according to the documentation. Remove all 3rd party billboards if you are running DynDOLOD 3 (recommended). Read the instructions for using DynDOLOD DLL if you are not using Papyrus (both can be installed, but setup with DynDOLOD Resources is different). Get the correct DynDOLOD Resources for SSE from the MEGA link in the OP. Use the -sse game switch in MO executable config.
  9. z929669
    You should not need different file paths for any MO-integrated tools if you install into a neutral location as we described in the System Setup Guide in Step 2. Once you have tricked Steam into thinking you have the latest version of the game, you simply need to rename the game folders. It sounds like you are using dedicated names of "Skyrim Special Edition-SAE" and "Skyrim Special Edition-SSE". So that means double the config, double the potential for issues, and double the headache. If you only use "Skyrim Special Edition" at any given time, then it's all much simpler. Just rename the Steam-game instance you want to use to "Skyrim Special Edition" and leave the other one named "Skyrim Special Edition-SxE". This way MO, tools and Steam only see and recognize one game folder at any given time. You really only need to configure BethINI for each instance when you want to use it.
  10. z929669
    You will want to post on sheson's DynDOLOD 2 topic for assistance. He doesn't support the Step guide, so let us know what the issue is if it's related to the guide or a mod in the guide. I don't run SLE any longer, so I can't say for certain, but I think it has to do with the mountain mod not having LOD versions of the textures. It could also be a number of other things that I don't want to speculate.
  11. z929669
    Given previous comments, if this is working as expected, I vote to accept (although I haven't tested)
  12. z929669
    Anyone want to vote this one in for 2.0.0? I haven't tested it, but I vote for it if the glow works consistently with iconics
  13. z929669
    @Greg Unable to check right now, but I don't want to forget: Is this working as intended with all of our new meshes this iteration? I know it's a plugin, but I don't know if it is relying on vanilla meshes or not. If working as expected, I vote to accept.
  14. z929669
    Do we want to include this one? I will vote 'yes' if others don't disagree.
  15. z929669
    I'm voting to include this one for 2.0.0
  16. z929669
    This mod prioritization works fine and probably does reduce the need to hide files in some cases. Nevertheless, we try to keep the Foundation ModGroup limited to larger overhauls with many assets that should generally be overridden by other mods. This way, this ModGroup remains limited in size and relatively consistent. Hiding files only takes a few seconds and is now standardized in Mod Recommendations. That said, I'd support some arrangement limiting the need to hide files but the other admins will need to also express support without any objections.
  17. z929669
    Looks promising ... I don't see any window glow in what I assume are the LOD screens though. I'm not at my gaming PC now, but is the DynDOLOD resources file replacing the full texture for this? That mod should only be providing LOD resources and should not affect the full textures at all. Marked for Testing.
  18. z929669
    Yeah, I just fixed it ... I will be fixing them all over the next few days using the same format for consistency. Doing the same for disabling plugins. Both can be seen here.
  19. z929669
    Updated changelog
  20. z929669
    Just to affirm install options for this and Font Overhaul, I'm posting some screens. I agree with Mousetick that placement of this mod alphabetically is fine as long as we don't install the FO "Realistic Print" option. Most vanilla-like options for FO: Without this mod: With this mod (defaults for font size, adding Mousetick's suggestion for 'steal' font color, & reverting this mod's settings to Skyrim defaults [ bHideBookBG=true & bHidePageTurnButton=true ]): Step options for FO: Without this mod: With this mod (defaults for this mod's INI): My suggestions for both mods: Defaults for FO but using vanilla note font instead of the FO default. Default INI for this mod except for sBookStealTextColor=0xFF0000. Alternatively, we can consider using the FO default note font and consider setting bHideBookBG=false for better readability of the 'steal' option when it's present. I don't think the page-turn instruction is necessary, but I could go either way with these other settings.
  21. z929669
    I vote to accept this mod for 2.0.0. It's definitely an improvement and vanilla-friendly. Also, I think the suggested options in the OP can be adopted.
  22. z929669
    Is the issue caused by FO overrriding /interface/book.swf? I have this mod sorted just after FO in my MO left pane. We'll probably just use this ModGroup sort order if sorting alphabetically is the cause.
  23. z929669
    Also as mentioned on the previous topic, if you are just helping out with updates to mod pages rather than installing the guide, then this is helpful. Just be aware that you will not likely have success installing all of them in the ModGroup listing for SkyRimSE (or any other game).
  24. z929669
    Mousetick is correct. You should be using the guide mod tables. All game-mods pages are classified into ModGroup on the game home pages, but many/most of them are not used in a particular guide. However, if you are simply checking all game-mod pages for issues and not installing a particular mod build, then that's helpful. We appreciate the assistance
  25. z929669
    Thanks for posting the compares. I guess I like larger or fullscreen, as those will have the least chance of wrapping or overlap.
×
×
  • Create New...

Important Information

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

  I accept