Leaderboard

v2.0 is now live! I will also have a new video on the mod page soon to demo the new heavy storms. Many FormIDs have changed for the extra non-vanilla weathers, so any 3rd-party patches may need to be rebuilt.

I've created a MO2 plugin to band-aid this issue. Thanks for information provided here. Plugin just redirects anything that goes to Documents/Skyrim.INI back to Documents/Skyrim Special Edition via MO2 VFS, it's not a real fix but enough to satisfy my OCD for now. https://www.nexusmods.com/skyrimspecialedition/mods/144932

Thanks for all the work in the guide, just wanted to mention that im following the changelog to update to 2.3 and noticed that "Moon and Star - CC Consistency and Immersion" and "Moon and Star - Cleaned Fixed and ESMed" are not in the changelog for Patches

The following time-saving procedure allows for adding new worldspaces to an existing grass cache, or for updating the current grass cache of specific worldspaces, without re-generating the cache of all worldspaces from scratch, which as we all know can be a very time-consuming process. This is not a guide about precaching grass from scratch with NGIO. It is assumed you have already precached grass with NGIO successfully at least once, and know how to repeat the operation. The procedure assumes Mod Organizer 2 is used as the mod manager. IMPORTANT: Grass Cache Helper NG is required for Skyrim SE/AE 1.6.x players. The existing grass cache must have been generated with Grass Cache Helper NG activated, and it must remain activated at all times for incremental precaching, and for playing. Step 1: Note the Editor ID of the worldspace(s) you want to add or update. Figuring out which worldspace(s) and their Editor ID is a task left up to the reader. See some suggestions at the end about finding out this information. Step 2: EXTREMELY IMPORTANT. Disable your existing grass cache mod[1] on the left side of MO2. Failure to do so will wipe out the entire grass cache during the later steps, which will then need to be exhaustively re-generated from scratch, which would make this tip completely pointless. Step 3: Edit NGIO configuration and specify the list of worldspaces to add or update. The NGIO configuration file is [..]\NetScriptFramework\Plugins\GrassControl.config.txt. Edit it with a text editor. You may want to make a backup copy of that file before editing it. Search for 'OnlyPregenerateWorldSpaces' or scroll down until you see it. Then comment out the line by prepending it with a # character. Add a new line like this, containing the Editor IDs you gathered in Step 1: OnlyPregenerateWorldSpaces = "Worldspace1EditorID;Worldspace2EditorID;Worldspace3EditorID" The list of worldspace(s) to add or update must be enclosed in double quotes, multiple Editor IDs separated by semicolon. Example showing the result of editing and specifying only one worldspace: Step 4: Launch the NGIO precaching process from MO2 as usual. You may need to make preparations[2] specific to your mod setup before launching the process. The process should only take a few minutes[3], more or less depending on the number and size of specified worldspaces. Wait until it completes successfully. Step 5: Move the grass folder from MO2's Overwrite folder to your existing grass cache mod. If you are updating the grass cache of worldspace(s), you will be prompted to confirm replacing the existing cache files with the new ones. Step 6: Undo the NGIO configuration changes you made in Step 3. If you made a backup copy of GrassControl.config.txt as suggested, simply restore it. If you added new worldspace(s), don't forget to edit GrassControl.config.txt and append their Editor ID to the existing OnlyPregenerateWorldSpaces line. Otherwise they'll be missing the next time you re-generate the entire grass cache from scratch. Step 7: Re-enable your grass cache mod on the left side of MO2. That's it. Enjoy[4] your updated or added grass. Notes [1] Your existing grass cache mod is the mod containing the grass folder, not the mod containing NGIO (inside a NetScriptFramework folder). If you have merged both mods, then you're doing it wrong. Split them into two separate mods. [2] Preparations such as reducing Skyrim's display resolution, disabling mods that may interfere with the precaching process, switching environments/profiles... Anything that had to be done when generating from scratch. [3] If you're updating Tamriel (Skyrim's main worldspace), the largest of all worldspaces, it will take quite a while, but it will still be faster to process it individually than processing all worldspaces in the entire load order. [4] You're not yet completely done if you use the grass cache for grass LODs. You'll need to (re-)generate LODs with DynDOLOD for the specific worldspace(s) you added or updated. Refer to the official DynDOLOD documentation for details: Updating or Updating. How to find out the Editor ID of worldspace(s) with grass Method 1: Recommended when adding new worldspace(s) for its accuracy. Requires xEdit, basic knowledge of its operation, and Worldspaces with Grass SSEEdit Script for No Grass In Objects. Install 'Worldspaces with Grass SSEEdit Script for No Grass In Objects' as instructed on its mod page. Load up in xEdit the plugins of the mods adding new lands, as well as any grass/landscape mod plugins. Omit other plugins. Run the 'List worldspaces with grass' script. When it's done, copy the resulting list and paste it to some place where you can edit it. Remove all vanilla worldspaces from the list. The remaining worldspaces are the new ones with grass. Example with Wyrmstooth: AlftandWorld;Blackreach;BloatedMansGrottoWorld;BluePalaceWingWorld;DarkwaterWorld;DeepwoodRedoubtWorld;Dimfrost;EastEmpireWarehouse;FallowstoneCaveWorldEnd;FallowstoneCaveWorldStart;FrostmereCryptWorld;JaphetsFollyWorld;KarthspireRedoubtWorld;KatariahWorld;LabyrinthianWorld03;LabyrinthianWorld04;MarkarthWorld;RedEagleRedoubtWorld;RiftenWorld;ShadowgreenCavernWorld;SkuldafnWorld;SolitudeWorld;Sovngarde;Tamriel;WhiterunDragonsreachWorld;WhiterunWorld;WindhelmPitWorldspace;WindhelmWorld;WyrmstoothWorld Method 2: Suitable when adding or updating worldspace(s). Physically go to the place in-game where there is already grass to be updated or where there should be grass to be added. Use fast-travel, coc or cow console commands, whatever works to get there. Open the (More Informative) Console and press the Tab key until the Worldspace & Cell information card is displayed. Ctrl+Click the 'World Space' field in the information card, to display more details. Note the Editor ID. See following screenshot for illustration: Method 3: When adding new worldspace(s), less accurate than Method 1. Requires xEdit and basic knowledge of its operation. Load up the plugin of the mod adding new lands in xEdit. Expand the Worldspace node. Select a new worldspace entry (i.e. not vanilla), and check the 'DATA - Flags (sorted)' section on the right panel. If it contains 'No Grass' then skip it, go to step 6. Otherwise note its Editor ID. Repeat from step 3 for each new worldspace entry. Illustrated example showing the first two worldspaces from Beyond Reach:

Having played many many hours with this mod without any issues after dumping FIZZLE, I'd strongly recommend it. It's very lightweight compared to FIZZLE, as its script runs only when casting spells vs. FIZZLE's cloak spell script which runs "constantly". It doesn't have the various compatibility and performance issues carried by cloak spell-based distribution to NPCs. Its user experience for new users is also superior to FIZZLE: a spellcasting failure is indicated by a "puff" of colored smoke (different color depending on spell type) around the player (or the NPC), which is easily noticeable even in first-person view. Whereas with FIZZLE a failure is indicated by a small audio "click" and nothing else happens. I found that FIZZLE feedback quite confusing and it was difficult to notice what was happening when I started playing with FIZZLE. It has its own formula for calculating the chances of success/failure which is not the same as FIZZLE's so the experience may feel different at first for users accustomed to FIZZLE. But the idea is the same: trying to cast higher level spells than skill levels may fail, the chances of failure increasing the higher the level difference. I was using a different mod than EEOS in my playthroughs to distribute spells to NPCs so I can't speak to how well this mod works with EEOS in regards to NPCs trying and failing or succeeding to cast spells in a pure STEP setup. Note: I'm not currently playing or even running Skyrim these days, haven't been for the past 6 months or so, and don't intend to return to it for quite a while, if ever. I just thought I'd chime in in favor of this mod, which is quite underrated IMHO. There are not many mods that do this kind of thing it seems. Last I checked there were 3 mods: FIZZLE, this one and another one that I don't remember. This mod also exists in a "full featured" version by the same MA, with more options and features, and a much more "sophisticated" behavior (not recommended for STEP). My 2 cents, hope they help. Cheers.

Great work on getting that updated!

Good day good STEP-people! So we had a game update and there will be some problem follow the guide as is. - SKSE is updated. According to ianpatt on Nexus SKSE page BGS will update the game again soon so no hurry updating/reinstalling stuff. - The game update has caused some issues with SkyUI (same post on Nexus SKSE page as above) I am in the middle off an actuall playtrough so i will wait with the updates.

Illustrated practical demonstration of the engine's handling of temporary references in ESM vs. ESP plugins For mod authors and advanced mod users. TLDR: Skip to the Summary section further down. Part 1: The initial (vanilla) state We're in Markarth, in front of the stables. Let's look at a few objects: the door, a handcart, and a hay bale: Notice the console shows a Textures field for all the references. This indicates the textures are loaded and the object is rendered. The door is a persistent reference because it's used with navmeshes for NPCs, among other things. The other objects are temporary references. The door is only interesting as a point of temporary/persistent comparison later on. Part 2: The demonstration plugin Now let's make a simple plugin for an hypothetical mod. We're going to permanently disable the handcart, make the hay bale bigger, and place a new small hay bale: So the plugin overrides two vanilla references and adds a new reference. We've also given each reference an Editor ID to more easily look them up. Let's go take a look at the changes in-game with our new plugin enabled. The handcart is disabled and no longer visible, the existing hay bale has grown in size, and there is a new small hay bale not far from it: For the next tests, we'll be moving to Winterhold, far, far away at the opposite end of the map. In Winterhold, the cells we were in in Markarth (i.e. the active grid) won't be active any more. Part 3: Engine handling with an ESM plugin The demonstration plugin is ESM-flagged. This is how Bethesda intended things to be based on how the engine is designed and behaves in Skyrim SE. Let's look at our references from Winterhold. First the door. The door is still there, despite it being in Markarth and us in Wintherhold, as expected since it's a persistent reference. But note the Textures field is no longer present, meaning the door while still being loaded in the game, is no longer rendered. It all makes sense. As for all the other references, they can't be found. They're no longer loaded in the game at all. It all makes sense again, since they're temporary in a cell outside Markarth and we're in Winterhold: Part 4: Engine handling with an ESP plugin We remove the ESM flag from the demonstration plugin. This is how 99% of all mods made and released by mod authors are. Let's again look at our references from Winterhold: Surprise! They're all found. They're all loaded (but not rendered, as they have no Textures field). They're essentially treated like persistent references by the engine. Note that even though the handcart is permanently disabled, it's still loaded. An object that will never ever seen in-game is wasting engine resources. Also note that the hay bale originally defined in Skyrim.esm, but has been overridden by our plugin, is now always loaded. The hay bale is now wasting engine resources. We can even go into the Jar's Longhouse, an interior cell, and they're still there: Summary The Skyrim SE engine is designed to handle (object or actor) references in ESM plugins, not in ESP plugins. References in ESP plugins still "work" but not as intended by Bethesda. Temporary references in ESP plugins essentially behave like persistent references: always loaded in the game, available and reachable globally from anywhere. All temporary references in ESP plugins, whether they are overriding existing temporary references, or newly added references, are affected. Temporary references in ESP plugins contribute to the total amount of loaded references, which has a hard limit. Even though temporary references in ESP plugins don't waste rendering resources, they still consume engine resources, mainly memory. Miscellaneous Notes ESP plugins are bad not only because they're wasteful, but they also hide all the bugs in mods. Since all the references, temporary or persistent, are always loaded, there is no longer a meaningful distinction between persistent and temporary. A temporary reference may be used in the wrong context, it's all fine, it doesn't matter as it's always loaded, it always can be found. The same plugin would be a CTD crashfest if it were ESM, or some things wouldn't work correctly. All Creation Club modules, from the simplest gimmick to the largest content, are released by Bethesda as ESM plugins (.esl is the "light" version of .esm), for a simple reason: it's how plugins are expected to be in Skyrim SE. People can be confused by the term ESM which is commonly associated with game masters, i.e. the core game files (Skyrim.esm, Update.esm, etc.). And so they think it doesn't make sense for a mod or a patch to be ESM, to be a master. The two concepts must be disassociated. Game masters are the core game files, yes. But ESM is something else, it's just a small flag that has no relation with the nature or purpose of the plugin, but has big implications for the engine. Again, Creation Club modules are not core game files, they're Bethesda-approved mods, and yet they are all ESM. There is no downside to plugins being ESM, while ESP plugins exhibit proven disadvantages and deficiencies. Technically, ESM vs. ESP only matters for plugins that add new references or modify existing references. Those that don't can be ESP. Large references are not related to temporary or persistent references. They're a separate feature that is only available, and that is no coincidence, in ESM plugins. ESP plugins that override large references cause visual bugs, which is another reason ESP plugins are a bad idea. In our demonstration above, we only used static object references. The increased resource usage and waste caused by ESP plugins is worse with temporary NPC references (ACHR), because the engine must periodically evaluate and process their AI packages in case they might need to travel somewhere, or do something on a schedule. The engine is optimized to prioritize and refresh the most often the NPCs closest to the player, but it still must check all loaded NPCs from time to time. It's too late now to do anything about it. There's too much legacy with 99% of all existing mods using ESP plugins. Making existing ESP plugins into ESM can be trivial or extremely difficult. Even if some ESP plugins can be made ESM, there is the issue of sort orders and dependencies, particularly with automated sorting tools such as LOOT. This may require that other plugins be made ESM in order to satisfy the dependencies or sorting metarules. Nevertheless, certain kinds of mods which only deal with static (STAT/TREE/FLORA) or moveable static objects (MSTT) - such as tree mods; or landscape clutter mods - can and should be made ESM as they typically add or touch thousands of temporary references. Persistent Location There exists a sparely documented reference attribute named 'Persistent Location' which is extensively used by Bethesda in the vanilla plugins, but is apparently ignored or unknown by mod authors. It seems to be used exclusively with NPC references, so may only be intended to be used with them. It allows a temporary ACHR to become "temporarily" persistent as long as the player is in the specified location. As a reminder, a location (LCTN record) is a "tag" that is applied to specific cells, which together belong to, and form, a geographic location. The Persistent Location is an optimization feature: it avoids making an NPC reference persistent, which creates some overhead for the engine as discussed above, and instead keeps it as a temporary reference while allowing for some advanced NPC behavior across multiple cells, even across interior/exterior cells, while the player is in the geographic location. For example, Adisla, a farmer working at the Hlaalu farm near Windhelm: This minor NPC has advanced AI packages to make her sleep and eat inside, work and wander outside, on a specific schedule. She also has dialogue scenes with other NPCs on the farm. These features require her to be persistent. However her reference is temporary. But the Persistent Location attribute makes her persistent only when the player is in the Hlaalu Farm. Once the player exits the location the reference becomes temporary again, and completely unloads when the player moves further away. Obviously this is only meaningful in ESM plugins. It's completely useless in ESP plugins, since all temporary references are always and everywhere pseudo-persistent.

The main theme in Fallout: New Vegas is letting go. And I have to let go. We are expecting our second child any day now and once the baby gets born I won't have the time to play and curate for quite some time. I can't say how long it will take, I can't even say if I'll make a comeback as a curator, but I know I would like to get back to it one day. On the practical side of things, the guide is currently still in working condition and would probably manage to stay in working order for 3 months or so. If someone wants to take it from here, they are free to do so. After all, that is the way Step modding works. I will keep reading the Feedback thread and providing advice when I can, but I can't make any promises on regularity. I don't want to saound too melodramatic. This is not goodbye, just a call for would-be curators willing to step in. Step is a great community and the FNV Guide has helped me get through taxing times, giving me something to do through the occasional bouts of insomnia. I want to thank the admins for giving me this opportunity (and encouraging my hobby), the guide users for the effort of installing ~300 mods (I hoipe it was worth it) and I hope that someday I will be able to contribute again. P.S. Should have given a longer notice, but I'm hooked up on gaming and was delaying the inevitable in self-denial.

I originally included these notes in my previous post under a spoiler tag, but I'll put them here without as I think they were missed (they included that bit about Bthardamz). In the Tool Setup table, xEdit.exe and xEditQuickAutoClean.exe should be named SSEEdit.exe and SSEEditQuickAutoClean. The collapsible here does refer to them by their original names, as does the System Setup Guide. If they should be renamed, the filename should be changed in both places. SPID no longer has a separate AE file, but instead, a FOMOD. May want to do a FOMOD table like you do for other mods with FOMODs (though it's an easy install, tbh--just the one choice of your game version). Same goes for Simple Offence Suppression. I recall the original version of the guide having instructions for adding mods from .zip, instead of Nexus. I know how to do this, but someone who doesn't might be confused when running into Skyrim Realistic Overhaul, Skyrim Redesigned WIP, and Arthmoor's mods. If these are elsewhere or I've overlooked them, ignore! Enhanced Vanilla Trees' FOMOD collapsible is missing the "Greener Pines" section of the custom FOMOD. Glacier LOD Meshes should have a note on it, like the other Skyrim LE mods, that it is compatible and the warning can be ignored. Reverb Interior Sounds Expansion does not ask me about Skyrim VR--unsure if FOMOD was updated or what. For Tempered Skins for Males, we're free to choose whatever we like. After choosing underwear option A2 however, the files I'm supposed to hide for underwear are not present. Will report back if this breaks something. Butterflies Unchained still lists the CACO patch as necessary--may want to note that it's unnecessary if you haven't installed CACO now that it's optional. Same thing goes for the Kryptopyrs Patch Hub--many of these are for CACO or CCOR or TCIY specifically and aren't necessary if those aren't installed. Could use some organization to reflect this. Same for Vokrii patch--unnecessary if you don't have CACO. It's clear to me, reading the ENBSeries collapsible, that the Step ENB preset files from Nexus should go straight into the root folder, but you may want to say this specifically. (Note from later: the guide does get to this, but it's at the end of the section, in the collapsible for the Post-Processing patch. Maybe have the files placed when the ENB preset is downloaded originally, in the ENBSeries collapsible itself?) All mods added! List of things that are currently listed as "redundant" in case that's helpful: the three DLCs, Majestic Mountains Double-Sided Patch, Battle Ready Candlelight Fixes, Rudy HQ - Bthardamz. Can provide overwrite reports if needed. Items that needed xEdit quick cleaning: SmoothShores.esp, imp_helm_legend.esp

Some notes: CACO has been updated for 1.6.640. Alandtse has developed an alternative to Crash Logger here, also supporting 1.6.640. I was thinking about downgrading to 1.6.353, but I worry that with the majority of these DLL-based mods updated, some will only have 1.6.640 versions available, so I will continue waiting. Thanks for maintaining this list!

Na, I really didn't mean you :) Reading my post again, I see that it can easily be understood that way. What I meant to say is that you are pouring your free time into the STEP project. For others to make passive aggressive statements about how you should best use that time seems inappropriate. Besides, it is also really counter productive. No one obligates you to contribute in a way you do not want to, that's how the Skyrim community works (*hopefully, *mostly, ect. ). You probably contributing to STEP because you are having fun sharing your expertise in the current modding process and building with others. That alone seems like a really good reason to keep things the way they are.

I've updated the mod with some additional customizable settings for the plume.

Keep it simple: just move the XPMSE.esp plugin to 'Optional' on MO2's 'Optional ESPs' tab. No need to hide anything but the plugin, which MO2's Optional conveniently does. The plugin starts hidden quests to set up the MCM and the whole cloak spell thingamajig, which run scripts. Without the plugin, the scripts and MCM interface resources are completely harmless and can stay where they are. If users want to use these features, they can just move the plugin back from 'Optional', without unhiding anything. That's it.

Starting with DynDOLOD Alpha-59 I updated the waterfall rule for Skyrim Special Edition so there is a static LOD model in object LOD Level 4 already. They are slightly moved down and back so it shouldn't z-fight with the full / dynamic LOD models.

For finding a botched mod, do a boolean search. Start by disabling the bottom half of your mods and running again. If it works, enable half of the mods you disabled. If it doesn't, disable half of your remaining mods. It should take nine searches to narrow yourself down to a single culprit mod. Do note that the boolean search is less useful if there is more than one mod causing a problem. But it did allow me to find my botched TK children install in less than ten minutes.

The STEP install instructions should be updated to remove "2. Install Fixed Mesh Lighting - Creation Club Backpack as a separate mod to maintain version notification updates." because since version 1.9.0 the main file includes the optional file Fixed Mesh Lighting - Creation Club Backpacks. The STEP FOMOD instructions even show the new option - Other / Potions / Adventurer's Backpack - as ticked.

Maybe you'd like to consider using 'Skyrim Character Sheet', which provides also faction information and more in a custom, SKSE-configurable ingame window.

In case anyone wants to move the oxygen meter widget... As a workaround until this mod gets updated to address the widget X and Y position values not working, I have downloaded and installed an older archived version of the Oxygen Meter 2 mod, 1.0.5. And then downloaded and installed the Oxygen Meter 2 - 1130-1170 Updated DLL mod. This allows me to modify the X and Y values in po3_OxygenMeter2.ini to reposition the widget.

Discussion topic: The Dragonborn's Bestiary by JPSteel2 Wiki Link Collect information about the creatures you encounter, learn their strengths and weaknesses, and keep track of your feats with kill, summon and transformation counters. Adds a new custom menu to the game. SKSE plugin. Requires SPID and KID. Patch for CACO on CACO mod page.

Discussion topic: Dragons Shout with Voice Update - SSE by ntn9713c Wiki Link Patch for Dragons Shout with Voice to add shout voice to DLC dragons, Ulfric Stormcloak and Greybeards Adds to and fixes Dragon Shout With Voice. No need for "Dragons Shout with Voice from Location" with this added (i asked the author on the mod page).

It is safe to ignore. The HD overhaul has an optional 4K Galaxy file that depends on that framework, but none of the main files do.

Before: After: By default, Skyrim Character Sheet automatically shows when entering the inventory screen. This obscures the character and the item viewer making it a nuisance. Pressing 0 turns it on or off, however, it should default to off. My ini tweak makes it so that when you enter the inventory screen it doesn't show automatically.

Section 20-Patches, penultimate item: Step Patch - Conflict Resolution. Expanding it or following the Wiki link shows the following text (relevant bit highlighted in green): You're not making any sense: Files are there but you can't find them? You found the file but it's not the right one - which file? Please read carefully and follow these 3 simple steps: Go to https://www.nexusmods.com/skyrimspecialedition/mods/31054/?tab=files. Download the file named 'Step Grass'. It's listed on that page, at the very bottom of the page. Install 'Step Grass' as a separate mod and enable in MO2.

Judging by my Wrye Bash, the STEP patches involved will need some major work, especially on the level lists.

Discussion topic: Clams and Oysters Clipping Fix by Diego2891 Wiki Link Improves positioning of clams and oysters in Skyrim and Solstheim. Compatibility: it should be compatible with everything because this mod only slightly modifies the position and rotation of clams and oysters. But one thing needs to be clarified: all the changes are based on the size and characteristics of vanilla meshes. Mods that replace original meshes may exhibit even worse clipping effects. My notes: This is based on and requires USSEP. USSEP fixes a few worst cases but this mod comprehensively adjusts the placement of every. single. clam. and. oyster. in the world. Well, not all of them. But many: 700, according to the MA (same MA as Fires and Embers Clipping Fix). That's quite a feat. Comes as a FOMOD with regular ESP or ESL-flagged ESP options. I'm not too bothered by shells sinking into the ground once harvested, which this mod prevents. But I'm annoyed by shells floating in the air or clipping with their surroundings, and this mod fixes that too. Compatibility is to be taken with a grain of salt. If another mod changes the terrain or objects around/under some shells, the results may not be as intended. Ideally that other mod should disable or move the affected shells to fit its own changes and prevent floating/clipping. So it's best to sort this mod high in the load order so that other mods may override it if needed without patching.

Can we please keep this conversation about the mod and not make it personal. There is no need for that. People have opinions and they don't always match your own. As (supposed) adults we can agree to disagree. On the topic: to me, whether or not SLaWF and USSEP overlap is a non-issue. Skyrim in all it's forms is flawed and both mods aim to fix the flaws. This is what modding the game is about in essence: getting the base game updated/ fixed/ working better. To me most mods that change the LOOK of the game are merely the cherry on top and a matter of personal preference. SLaWF may have started out as "just" a landscape fix, but over time wizkid probably saw other issues that weren't/ still aren't being addressed by USSEP. So he stepped in to fix them. Nothing at all wrong with that. More kudos to him I say. As for the overlap, using STEP as a mod guide and adding mods on top of it, invariably means USSEP/ SLaWF edits are being overwritten by other mods. In my modlist over half of USSEP edits are changed for various reasons, like I don't agree with what USSEP changed or another mod does it better. Again, a matter of personal preference. So in my opinion both these mods complement each other, despite the overlapping scope. Problems are fixed and the game benefits. As to how the overlap is handled is pretty much up to the player. Some will want to keep the USSEP edits and others the SWaLF ones. Everything is easily solved with xEdit, a merged patch and or a wrye bash. In my opinion people should really learn how to use Wrye Bash to fix issues. But that is a whole other discussion.

I don't get what all the fuss is about. What is the problem that this mod presents exactly? What are the tangible, concrete issues it creates for mod users or for players in-game? This mod fixes cosmetic issues that are not in USSEP precisely because USSEP doesn't address them soon enough or won't ever address them as they're considered out of scope for USSEP. Nowadays USSEP updates mainly addresses gameplay, "lore" and UI issues. Both mods together complement each other nicely. This mod requires and is built on top of USSEP. We can argue whether some of its changes are necessary/arbitrary/subjective, but the same can be argued about USSEP. I'd rather this mod exist than not, as it's more convenient than using a bazillion tiny fix mods. And fixing this type of issues is painstaking, boring work that few modders are willing to do. So I'm glad someone is taking care of it. The updates may be beneficial for donation points, but if you care to look at the comments instead of badmouthing, many changes/fixes are in response to user reports. They're not done in a complete vacuum, just for the sake of putting out updates. Lastly, in regards to conflicts, whether the same changes were in USSEP instead of this mod, wouldn't change anything. So this argument doesn't stand. The whole bashing on this mod sounds more like politics than serious technical discussion. Please provide actual tangible points to demonstrate how/why this mod is bad. My 2 cents.

In both cases, the user still needs to install files manually in SSE root folder, and edit the executables in MO2. So no difference in convenience or difficulty of installation and setup. Configuring "Force Load Library" is actually more complex (involves more steps and is more error-prone) than creating a new executable entry for SKSE. Making SKSE a separate executable makes it clear it's SSE + SKSE. Plain SSE remains available as its own executable in the menu, if needed. I reckon plain SSE is of limited value, but it may still be useful for certain vanilla-like testing profiles or for troubleshooting. Edit: Although it's not relevant to the STEP Guide: the NGIO Grass Precacher plugin for MO2 specifically looks for and launches skse64_loader.exe. So removing or omitting it is a bad idea for the grass precaching use case and possibly other use cases.

I wanted to share some Combined Worldspaces for LOD configurations I made for my Skyrim SE game, as a kind of showcase for this wonderful new feature in xLODGen and DynDOLOD. I hope it's useful and instructive. Changelog: Preliminary Remarks There are no restrictions on the use, modification or sharing of the provided configurations. All credit goes to sheson & co. for developing and providing such amazing tools for free. I merely leveraged their capabilities. All screenshots were taken at noon o'clock with Skyrim Clear weather for best visibility. Actual results in-game will vary depending on weather, time of day, lighting & weather mods. I don't know how the combined worldspaces look on the game's 3D map, as I use flat paper maps. They should look ok but may not be visible depending on how much the 3D map can be zoomed or panned. Purpose and Usage Example 1: Wyrmstooth in Skyrim As seen from: Solitude Lighthouse | Coast near Broken Oar Grotto | Fort Hraggstad Tower Analysis: Implementation: Configuration: Example 2: Solstheim in Skyrim As seen from: College of Winterhold Upper Walkway | Snow Veil Sanctum | Near the border with Morrowind The Vvardenfell island and the Red Mountain volcano seen above are not part of the combined worldspaces. They're something else. Implementation: Configuration: Example 3: Skyrim in Solstheim As seen from: Near Fahlbtharz | Atop an unnamed Broken Tower | On the Isle of Basalt Analysis: Implementation: Configuration: Installation Limitations Useful Resources

Using xLODGen beta 99. Tamriel -20,20 quad was selected for its good mix of hilly terrain, river coast, small islands and marsh. All meshes were generated at Quality 1 (default). Variations: Optimize Unseen OFF, ON, 50, 550, 700. Protect Borders option enabled. I tried to use a view perspective in NifSkope that shows the marsh, riverbed and river shore as much as possible, but rather than a top-down view, something closer to an in-game perspective. Solitude Stables are on the North side, Solitude Docks are in the North-East corner. All sequences are OFF > ON > 50 > 550 > 700. The title in the top left corner of each picture shows which variant is shown. View with water without wireframe View with water with wireframe View without water without wireframe View without water with wireframe

There's a whole 'Lines Expansion' series from the same MA: Bandit Lines Expansion (this mod) Civil War Lines Expansion Forsworn and Thalmor Lines Expansion Vampire Lines Expansion If you like this mod you may want to give the others a try.

errno 24 means "too many open files" Try setting MaxStdio in EngineFixes.toml to 4096 (or higher if that's still not high enough, 8192 maximum).

Correct. Same change applied to all 20 Sound Descriptor records in IHSS.esp.

For me this mod acting weird, some animals run on the bottom, some like running on the surface, some properly swimming.

I can download both files added on patreon without an account ...

Finished the guide and it looks great and works even though I skipped a few mods. Thanks for the help.

Just a heads up that the massive v2.0 update should hopefully be up within a week or so. 400+ hours went into it, it upgrades quite a lot. I will also update the low saturation patch Z provided. Thanks to Z for feedback/suggestions, and thanks to TechAngel for the comparison screenshots which were useful for checking how it looked on other setups than my own.

I'll elaborate: I saw sheson's reasonable remark about third party mods and decided to test it in full-vanilla environment (so not even MO2 or SKSE). It turned out that xLODGen works flawlessly in that environment (I just manually launched it outside of MO2 to be sure and used default output to data folder). So I simply compared ACMOS on/off and Vanilla/xLODGen (4 variations total). Turned out it was ACMOS doing something to the textures so not to clutter this thread I went back to that mod's page and asked about it - turned out there's "A Clear Map Of Skyrim - Textures.bsa" which contains worldmapoverray_n.dds and worldmapoverraysnow_n.dds that seem to add this gritty look to textures. DoubleYou recommended I simply delete those files. To quickly test it I hid the archive in MO2 and it worked so I replied here to make it clear that it was my bad. Seems like that was actually the intended look I just didn't like it and thought it was bugged. And again I did read and follow every manual/instruction/guide and my xLODGen files DO override ACMOS as is required in said manuals/instructions/guides. I even posted the order in which my left pane ends just so this question does not arise. It's just that in ACMOS .bsa file those .dds textures are located directly inside the Textures folder while in xLODGen output folder that Texture folder only has subfolders. So xLODGen has nothing to override those files with. TLDR it had nothing to do with xLODGen

Double-check and make sure 'Projected UV Diffuse Normals' is enabled 'Improved Shader' is disabled on the Visuals tab of BethINI.

This mod was updated recently but the MA still hasn't added the Ghostblade to the relevant Form List, despite it being listed as one of the effective weapons on the mod's description page and being notified about this omission in the comments section a while ago. Manual fix: add 00094a2b dunAnsilvundGhostblade to Form ID List 000D2058 defaultGhostWeaponFlickerList.

It looks like the instructions for reverting the SSE Display Tweak settings once testing is complete, are incomplete. They are: EnableVSync=true FramerateLimit=<previousValue> They should be: EnableVSync=true EnableTearing=false FramerateLimit=<previousValue> EnableTearing needs to be reverted to the previous value (false) as well, in order to fully re-enable VSync.

Never mind, seem to have fixed it. The original copy of Landscape Fixes I downloaded got corrupted or something. I redownloaded the mod and reinstalled and am no longer getting crashes. This thread can be marked as solved.

Uploaded a new DynDOLOD DLL version for Skyrim Special Edition 1.6.353 (Anniversary Edition). It requires SKSE64 2.1.5 or higher.

Sweet victory guys!!!! Everything is installed (except Oakwood) and LOOT is free of errors!!! I'm gonna finish off the tutorial and enjoy the oh so gorgeous Skyrim <3