Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 02/27/2014 in all areas

  1. 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.
    4 points
  2. 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
    3 points
  3. 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:
    3 points
  4. 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.
    3 points
  5. 3 points
  6. 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.
    3 points
  7. 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.
    3 points
  8. 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.
    3 points
  9. 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
    3 points
  10. 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!
    3 points
  11. 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.
    3 points
  12. I've updated the mod with some additional customizable settings for the plume.
    3 points
  13. 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.
    3 points
  14. 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.
    3 points
  15. As a workaround, I ended up increasing the "Mass" value of the involved lanterns. Most had a mass of 30. I increased this value to 170. Works well so far in my game.
    2 points
  16. Mod was updated to version 3.1.0. Improved flames that appear on actors so that they are smoother now. Improved smoke from fires for smoother animation and less popping. Added an option to not use the Master for users who do not use DynDOLOD. Added a customization option to reduce actor flames for improved 1st person visibility. Updated the Houses Shops and Inns SE patch to be load order agnostic. FOMOD instructions need to be updated on the guide. The plugin selection doesn't have the "Standard" option anymore. It's now "ESP + Master" or "No Master (no DynDOLOD)". Pretty obvious which one to pick as it pertains to the STEP Guide, just thought I'd mention it anyways.
    2 points
  17. 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.
    2 points
  18. Animation in Skyrim is a rabbit hole of its own. This is an annotated list of the 'Animation and Physics' Mods currently in discussion on the SE forum, listing their respective forum links but also their (possible) prerequesites and dependencies with other mods. This is for me to keep track of developments and the mods i am already using in addition to Step as well as for others to add another perspective on how to test and play with different compilations of animation mods. Hopefully this also might restart some of the discussions on the forum and possibly contribute a bit to the next iteration of Step. The (yellow) color-coded annotations signify the mods I already play with as an extension to current Step 2.3 without any further conflicts or need for patches. Thank you. Open Animation Replacer The open-source successor to 'Dynamic Animation Replacer' which lets you organize, prioritize and replace animations based on configurable conditions. This is the suggested baseline mod for the following list to work. This would be set up in category '02 - Extenders'. Animation Queue Fix A prerequisite for 'Open Animation Replacer'. Since this mod also works independently to handle queueing large amounts of animations, this is set in category '09 - Fixes'. Paired Animation Improvements A second prerequisite for 'Open Animation Replacer'. This could be set up in category '02 - Extenders' as well as alphabetically in category '05 - Animation and Physics'. Category 05 - Animation and Physics Arm Movement Animations (OAR) Variants of NPC arm movements, gestures and animations. 'Open Animation Replacer' is required. (This is an example mod for altogether three mods by the same author expanding on NPC animations and idles, 'NPC Animation Remix' and 'Gesture Animation Remix', which can be used together or as separate mods.) Assorted Animation Fixes A variety of separate animation replacers. One module requires 'Open Animation Replacer' to function. Divines Prayer Animations Variety of prayer animations. Requires 'Open Animation Replacer' and 'Keyword Item Distributor' to function. Flute Animation Fix Fixes the wrong positioning of flutes played by bards via different animation replacers depending on the skeleton used. 'Open Animation Replacer' is required. Ice skating fixed for real - No more attack sliding movement Already in Step. Might be noteworthy that with its latest version the mod can function as a simple animation replacer without the need for 'Nemesis'. Jarl Sitting Animation Replacer Alternating and randomized animations for Jarls sitting. 'Open Animation Replacer' is required. No More Swimming In Air Simple 'SwimIdle.hkx' animation replacer. Open Animation Replacer - IED Conditions Prerequisite for 'Weapon Styles - Draw-Sheathe animations for IED'. 'Open Animation Replacer' is required. Stronger Swimming Animation SE Already in Step. In its latest version 'Open Animation Replacer' is required for alternating between different swimming animations. Take a Seat - New Sitting Animations for OAR or DAR New sitting animations for Player and NPC. 'Open Animation Replacer' is required. Weapon Styles - Draw-Sheathe animations for IED Style-fitting animations for 'Immersive Equipment Displays'. 'Open Animation Replacer' and 'Open Animation Replacer - IED Conditions' is required.
    2 points
  19. That's not quite true as in the guide also says So when I saw there was something else ticked by default it made it seem like it was missed. And I know the guide is very specific and pedantic which is why I took "ONLY tick the following options" to imply that those options should be ticked by me. Not that I should UNtick other options.
    2 points
  20. For the last maby 5-6 years i almost never get further than maby L20 ingame before i rebuild my load order. I play MO2 more than Skyrim. THIS is a good place to put additional guides (addons) for Step Guide. To have different animation/combat directly within the guide will be to messy i think. People already confused by the different Step Patches and the different Post Processing options. But if we do add more animations in the Step Guide, it would be convenient to be very clear what mods adds new animations, and what mods just fixes vanilla.
    2 points
  21. We need to make one small additional change to the STEP - CR or STEP - Lighting and Weather CR (not sure which this would be for) If you load xEdit and look at SightlessNavFix.esp and conflict check to that file only you will see the lighting mod Ambiance loads before it. The XCLL lighting data you want from Ambiance for FormID 00025195 - Abandoned Cave will lose to SightlessNavFix.esp (Navigator Navmesh Fixes) gaining back the default Skyrim colorspace values.
    2 points
  22. 2 points
  23. This mod has a Hotfix uploaded 23 Aug 2024. The guide does not direct the user to download this hotfix.
    2 points
  24. With the addition of 'Immersive Equipment Displays' to the guide you now seem to have two opposing concepts of display, at least when it comes to quivers/bolts. While 'IED' wants to show everything equipped and favorited, 'Unequip Quiver SE' wants to hide quivers/bolts or only show them in certain conditions. In testing both mods together they worked fine, but depending on conditions akwardly contradicted each other, so I eventually ended up deactivating 'Unequip Quiver SE'. It seems that if a user wants to set all the main conditions of hiding quivers/bolts 'Unequip Quiver SE' does, they can also do so now via setting manually conditions in 'IED' alone, as explained in 'Immersive Equipment Displays - Tutorials and presets', making 'Unequip Quiver SE' redundant in the long run? (There is also a preset available to disable the quiver when a bow or crossbow is not equipped/displayed).
    2 points
  25. Ah, well, I believe it's mainly because of accuracy being worse than vanilla at low skill level. For example, if default setting for AimVariance is 0.9 at skill level 20 it will be 1.4 (almost 50% worse). It will, however, catch on with vanilla value at skill 37 and then will be improving from there. Your questions brought be to a quite deep analysis now I realized that accuracy multiplier is more sensitive than precision, and I should probably adjust those values independently.
    2 points
  26. The FOMOD layout appears to have changed. Attached are screenshots of the new layout. The instructions may need tweaking to match the new layout.
    2 points
  27. Judging by my Wrye Bash, the STEP patches involved will need some major work, especially on the level lists.
    2 points
  28. 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.
    2 points
  29. 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
    2 points
  30. You may have noticed this mod displays a popup banner in the center of the main menu screen while the game starts, and a popup progress bar in the top-right corner of the screen while it loads animations, both using very bright coloring and style reminiscent of 1980s personal computers. I dislike both. What if every SKSE mod displayed its own banner on the screen, it would be a mess. They can be turned off by editing settings in [...]\SKSE\Plugins\OpenAnimationReplacer.ini: To turn off the popup banner, set bShowWelcomeBanner to false: bShowWelcomeBanner = false To turn off the popup progress bar, set bEnableAnimationQueueProgressBar to false: bEnableAnimationQueueProgressBar = false I'd recommend to leave them on (the default) initially, so you can see the mod is starting up properly. Once you've seen them a dozen times and you've had enough, you may want to turn them off.
    2 points
  31. 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
    2 points
  32. Mod updated to 1.9.0 and now includes the optional update files.
    2 points
  33. I've been using this mod (Warm Text variant) ever since it was released. It set it up a while ago, so my memory is a bit rough. Installation Options FOMOD > Sleep-Wait Menu > Install Sleep-Wait Menu replacer? Yes. The configuration panel is shown twice in a row on the wiki page: FOMOD > HUD Menu > Install HUD? Yes. Should be 'No'. This option doesn't apply to STEP Guide, as it requires SkyHUD, which is currently not included in STEP Guide and is not even in Testing. I personally use it and would recommend it, though at this point I'd be hard pressed to tell you exactly what SkyHUD does and how it differs from/improves upon vanilla. FOMOD > Compass Navigation Overhaul > Yes, beige markers. Should be 'No'. This option doesn't apply to STEP Guide, as it requires Compass Navigation Overhaul, which is currently not included in STEP Guide. I see CNO is currently in 'Testing' though, so it could be considered. Beware however that DDDM is not compatible with CNO 2.x (the compass will be completely broken when both are used together, even with DDDM compatibility option). This can be fixed by borrowing the compass SWF from other DDDM-based mods, albeit with a vanilla-white style. I personally use CNO with DDDM, with the manual borrowed SWF overwrite hack, and would recommend it. FOMOD > Quick Loot Menu > Install QuickLootRE replacer? > Yes, Quick Loot EE. I don't use Quick Loot EE or RE so can't comment on that. FOMOD > Wheel Menu > Install Wheel Menu replacer? > Yes. Should be 'No'. This option doesn't apply to STEP Guide, as it requires UIExtensions, which is currently not included in STEP Guide and is not even in Testing. I don't use it so can't comment on that. Seems to be geared towards console controller users. FOMOD > Cursors > Replace the cursor? > Yes, static. The cursor replacers, even the static one, are too fancy/distracting for me and not in the same flat style as the overall design. I prefer the vanilla flat cursor style of Small Vanilla Cursors currently included in STEP Guide, even though they have different color (white vs. DDDM gold). FOMOD > Font > Replace the main font? > ENG (Latin). This will conflict with Font Overhaul. I don't care much for the main 'Friz Quadrata' font so I don't use it but I like the 'Consolas' font for the console so I kept it. Requires manual editing of fontconfig.txt to pick and choose fonts from DDDM vs. Font Overhaul. FOMOD > New UI Sounds > Install new UI sounds? > No. You may want to give the new UI sounds a try. I think they're nice. They're softer than the vanilla sounds. For example, vanilla has a loud 'whoosh-bang' sound for crafting potions at an alchemy table, while DDDM uses a more natural and subdued 'gurgle' sound. Conflicts As noted on the mod page, this should be installed dead last in the UI mod group and overwrite everything. Font Overhaul See previous point above. Icons For Skyrim Character Sheet Redundant, can be removed as DDDM provides its own complete set when the Skyrim Character Sheet option is selected in FOMOD. Wider MCM Menu for SkyUI Better Dialogue Controls Better MessageBox Controls Redundant, can be removed as DDDM fully incorporates them. Convenient Reading UI While DDDM incorporates the main reading UI from that mod (same MA), I'd recommend keeping and overwriting Convenient Reading UI for its other features that are not included, such as faster page turning animations and other stuff I can't think of at the moment. Other Oxygen Meter should be replaced by Oxygen Meter 2. The original Oxygen Meter uses the enchantment charge bar for its widget. Oxygen Meter 2 uses a custom widget. DDDM replaces the custom widget with its own DDDM-style widget, similar to Magik/Health/Stamina bars, integrating seamlessly with the UI theme. Final Words The 'Warm text' variant and its golden-colored theme may not be to everyone taste and may cause issues with vision-impaired users. While I prefer it over White, you may want to evaluate and consider the more neutral White option as the default. This mod is a beast with all its components and dependencies. Customizing it requires navigating a maze of configurations, and identifying the source of issues can be a hassle. This might create technical support headaches. Nevertheless I like this mod a lot and can't imagine playing without it. I made a few tweaks to the configuration, matter of personal preferences. Can be discussed later if needed, if I can find/remember what changes I made and why.
    2 points
  34. Correct. Same change applied to all 20 Sound Descriptor records in IHSS.esp.
    2 points
  35. For me this mod acting weird, some animals run on the bottom, some like running on the surface, some properly swimming.
    2 points
  36. I installed the updated HD Local Map mod the day before my save game crashes started occurring (HD Local Map has nothing to do with my crashes). The mod was working well for me. The unexplored areas were hidden.
    2 points
  37. Just to add to the praise and to confirm that it works: I can now run TexGen using the 'working version' using the release version of MO2. Thank you for your help! What a fantastic and responsive dev!
    2 points
  38. Removing existing display drivers with DDU and reinstalling the most current version appears to have fixed the problem, as i've yet to reproduce the error in several hours of play. Hopefully this thread helps someone out in the future.
    2 points
  39. 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.
    2 points
  40. It doesn't really make sense to merge Position and Rotation X/Y/Z fields, they both should be treated together as a cohesive whole in the context of their respective mod. Pick the version from the mod you want to win and copy both the whole Position and Rotation fields to your patch, without mixing Position or Rotation or X, Y or Z. It's easier and better. In general there are 3 possible reasons for mods to change the position/rotation of an object: a) to fix an issue, b) to cosmetically "improve" the scenery, or c) to make space for placing their own objects or as functional requirement for their own purpose. As a rule of thumb, you'd want to keep the version from the mod that's the most impactful and important for your gameplay, that is in order of priority: (c), then (b) then (a). If several mods conflict on the Position or Rotation and have the same level of impact, the rule of thumb is not good enough and it'll likely be necessary to visually inspect their respective changes in-game or in Creation Kit, in order to make a decision on which one should win. In your particular case, you'd probably want to keep the Position & Rotation changes from BDA. And since BDA is probably sorted after SMIM by LOOT in your load order, there may be no need to patch the conflict in the first place.
    2 points
  41. The SSE version of the mod includes these two files: "textures\objects\lockpicking\skeletonkeylockpicking.dds" "textures\objects\lockpicking\skeletonkeylockpicking_n.dds" The vanilla textures which this mod is supposed to replace are located at: "textures\interface\objects\lockpicking\skeletonkeylockpicking.dds" "textures\interface\objects\lockpicking\skeletonkeylockpicking_n.dds" It's missing \interface\ in the path. Not a big deal, I'm just pointing out because we can adjust ourselves instead of just have the files sitting there without being loaded ingame.
    2 points
  42. It has been quiet from me for a while here in the forum. I'm still here and updating this build. I'm just letting you know that the site has been completely rebuilt and it now also has a nexus page. I don't think there are many users atm, but it's there for anyone that wants. STEP currently seems to adopt EnaiSiaion's suite of mods that alters magic, skill, races, abilities etc. This build uses SimonMagus suite instead, for anyone that is intrested in that. Thats it! Same link as usual: https://dreadflopp.github.io/dreadsskyrimbuild/
    2 points
  43. No surprise I suppose but this turned out to be very true. There was one thing I forgot to mention: I installed the True 3D Sound for heaphones mod after following your instructions above, and before starting a new game. Silly, I know. It just didn't occur to me because I regarded that mod to be ultra safe and not conflict with anything. Big mistake as it turns out, because I found this in a support post "The DLL file included in this mod caused me to CTD upon starting a new game. Was tearing my hair out trying to figure out what mod it was in MO2, and even on an unmodded game, only to realise it was this. Everything works fine without it installed." followed by: "Actually I'm willing to bet you have Alternate Start - Live Another Life installed. This 3D Sound mod is not compatible with the starting prison cell in that mod, because those cells have some custom sound settings in its ESP that seem to not play well with 3D sound (in my experience normally when having Immersive Sounds Integration installed as well... possibly due to a conflict with that sound mod and the ASLAL cell). Simply rename the DLL, start the game, create your character, leave the starting cell, then name the DLL back to its normal name. Voila! Working 3D Sound. Just be sure to remember to rename the DLL temporarily again if you start another new game. This DLL doesn't affect your save in any way, so it won't harm anything to disable mid-playthrough." That mod is old now by the way. The newer version is Binaural 3D Surround Sound for Headphones - HRTF. But there are two issues with the new version as well: 1. The sound conflict is still there - I got a CTD before arriving in the cell of ASLAL. 2. "Audio Overhaul is not compatible for some users." (from the description page). Issue 1 can easily be avoided by doing the highlighted text above (from the support posts), or by doing like I did; simply wait to install it after leaving the ASLAL prison cell. Issue 2 I have no clue about. I have Audio Overhaul installed (as per the Skyrim SE guide) and I don't have any issues. Yet. The mod can't be installed using MO2 or Vortex. Just like ENB the files have to be manually copied to the Skyrim SE game folder. The files look like this: So the dll file and the hrtf folder containing the mhr files go into the Skyrim SE folder. But they have to be removed every time you want to start a new game (using ASLAL) and then copied back after leaving the cell. At least that's my experience. Just thought I'd mention this here for completeness sake.
    2 points
×
×
  • Create New...

Important Information

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