Jump to content
TechAngel85

STEP v2.10.1 Development

Recommended Posts

Notice:

As of STEP 2.2.8, we are only actively supporting Skyrim Legendayr Ed. (all DLCs) - We continue to 'passively' support other DLC/non-DLC configurations as an artifact of having done so previously. However, moving forward, all new content will assume Legendary Ed. We will gradually phase out information pertaining to limited DLC components.


Overview:
STEP 2.10.1 marks the start of our new versioning scheme and how releases are handled. All changes to the Guide between minor releases will now be released as a packaged "hotfix" release. 

Reviewed our version scheme for more information.

Since this is a community driven project and site, we would like to encourage users to tag mods they'd like to see in STEP. To do this, please add a 'testing' tag to the desired mods. This will allow us to filter the mods and review them. Mods that we think fit into the STEP project will be officially marked for testing and mods that do not will simply have the 'testing' tag removed.

Dev Guide v2.10.1
Changelog (subject to developmental updates)
Mods currently in Testing



For replacers, the test case should be a high-quality screenshot compare. We don't need a lot, just two or three sets of compares on the thread marked [ TESTING ].

The idea is that testing --and logging of that activity on the threads-- will be touch & go for a lot of mods, and it should be pretty clear by anyone stumbling upon any mod thread what the end result is.

Let us know if you want to be a Mod Tester! We're always looking for official testers!



Changes for v2.10.1 (in no specific order)





2.10.1 Dev patches:

Share this post


Link to post
Share on other sites

Yeah, the staff just has to remember that any changes at all to the guide (even updates to the mod pages) need to be held off as they will be leased as "hotfixes". This will mean more frequent updates, but the updates will also be smaller.

Share this post


Link to post
Share on other sites

Some ideas on the current release that have come up while reinstalling today:

 

2.I Clothing and Equipment:

- There's currently a fair amount of conflicts going on in this section, mostly between RUSTIC CLOTHING and other mods, mostly due to mod ordering.

 

- Nightshade vampire armour:

    - Overwrites RUSTIC CLOTHING.

    - Personally, I prefer the RUSTIC textures:

        - There's significantly more detail on the belt areas of both female and male outfits

        - Better handling of the bracers on the male outfits in RUSTIC.

 

- NRHD Masque of Clavicus Vile:

  - Overwrites RUSTIC CLOTHING.

  - By the admission of the mod author, this is just a 'proof of concept', 'Slapped [together] in 3-5 minutes', consisting of a sharpen & distressing of vanilla textures.

  - RUSTIC provides a complete retexture, noticeably better specular, more detail in eyes/cloth neck covering, while keeping the overall weathered effect NRHD Clavicus Vile aimed for.

 

- Dragonborn Mage Robes Retexture Pack

  - Currently (completely) overwritten by RUSTIC CLOTHING.

  - Not sure what peoples opinions are on this one, I would say it is of around equal quality to RUSTIC, it is mostly just a stylistic choice between the two. Personally I quite like it.

  - Either way, it is doing nothing in its current position in the install order. Either needs moving after RUSTIC, or removing completely.

 

- Mage Outfit Texture Overhaul

  - IMO this should move to Extended from Core.

    - RUSTIC provides a quality retexture of vanilla robes, in line with Core mandate.

    - This mod expands on vanilla, keeping in line with it, but nevertheless an expansion on Bethesda's original intent - Extended/STEP Pack mandate.

 

I think there needs to be a bit of discussion of whether STEP should try and stick to one texture pack where possible or not. For weapons/armour, aMidianBorn's retextures provide a consistent art direction, just as there is a consistent design philosophy in the vanilla game - which I feel fulfills the STEP aim of being an almost imperceptible improvement over the base game. Using disparate texture packs obviously works against this to a greater or lesser extent; in some cases the individual textures can be superior, at some cost of consistency. Anyone who has installed Immersive Weapons will know what I mean - certain textures and models just leap out as completely different in style to the vanilla game, which to an extent can break the suspension of disbelief/internal consistency of the world. 

 

As RUSTIC CLOTHING now covers the entire clothing folder, (actually overwriting aMidianBorn's fur armour retexture - something else which I think could do with a look at) I think there needs to be a decision if STEP should use it wherever possible, or overwriting it with other mods that detract from its consistency, but may provide superior individual textures.

 

Apologies for the double post, I can't edit/remove my previous one for some reason.

Edited by sharrken

Share this post


Link to post
Share on other sites

A suggestion I was thinking of, was to specify locations where people could and should do a trial run, just to the point where your character is getting out of the wagon. That's the first point where we can escape out of the game. The reason for this suggestion is that, for some reason, I can start the game, through MO and SKSE while it's still raw. But, something keeps happening somewhere in the process, and by the time I get to the end, I can't even launch it. And, I have 'no' idea where I'm going wrong. I've had to start over completely three times, spending hundreds of hours trying to compile this thing, just to find out that, somewhere along the way, I screwed up somewhere. And, I have NO idea where! It's awfully frustrating. I'm sure it's something I'm doing wrong. I just don't know where. So what I was thinking, is that perhaps we could make a test run at the end of each section.

I was thinking I might like to do that this next time through. The problem is, the STEP process has us installing XP32 Maximum Skeleton Extended fairly early on, which requires running FNIS which isn't install until the END of the STEP program.

I was wondering if something could be done about the process to allow for test runs as we go, such as installing things like FNIS, and what ever other patchers might be needed earlier, even if it means having us rerun them a few more times as we go. It would be good practice for future additional modding anyway.

 

Just a thought. Maybe I'll try it anyway, just deactivating mods like "XP32 Maximum Skeleton Extended" or other's that require FNIS or the other Patchers. We'll see what happens.

 

I appreciate your thinking about this though. And, thank you for the great work you've all done already.

Share this post


Link to post
Share on other sites

A suggestion I was thinking of, was to specify locations where people could and should do a trial run, just to the point where your character is getting out of the wagon. That's the first point where we can escape out of the game. The reason for this suggestion is that, for some reason, I can start the game, through MO and SKSE while it's still raw. But, something keeps happening somewhere in the process, and by the time I get to the end, I can't even launch it. And, I have 'no' idea where I'm going wrong. I've had to start over completely three times, spending hundreds of hours trying to compile this thing, just to find out that, somewhere along the way, I screwed up somewhere. And, I have NO idea where! It's awfully frustrating. I'm sure it's something I'm doing wrong. I just don't know where. So what I was thinking, is that perhaps we could make a test run at the end of each section.

I was thinking I might like to do that this next time through. The problem is, the STEP process has us installing XP32 Maximum Skeleton Extended fairly early on, which requires running FNIS which isn't install until the END of the STEP program.

I was wondering if something could be done about the process to allow for test runs as we go, such as installing things like FNIS, and what ever other patchers might be needed earlier, even if it means having us rerun them a few more times as we go. It would be good practice for future additional modding anyway.

 

Just a thought. Maybe I'll try it anyway, just deactivating mods like "XP32 Maximum Skeleton Extended" or other's that require FNIS or the other Patchers. We'll see what happens.

 

I appreciate your thinking about this though. And, thank you for the great work you've all done already.

The easiest thing to do would be to install XPMSE but leave the mod unchecked in MO until you get to section N.

Share this post


Link to post
Share on other sites

The easiest thing to do would be to install XPMSE but leave the mod unchecked in MO until you get to section N.

That sounds like a good idea. I think I'll do that, testing after each section. Thanks.

Edited by Ewookie1

Share this post


Link to post
Share on other sites

Now that Nexus Mods disabled v1 of their API, the original Mod Organizer is no longer compatible with their site. Will efforts be taken to transition to MO2 as a recommended mod manager for STEP?

Edited by Zarggg

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By sheson
      This is a beta of [FNV|FO3|FO4|FO4VR|TES5|SSE|TES5VR|ENDERAL|ENDERALSE]LODGen/Edit with terrain LOD meshes and textures generation.
      This is for experienced mod authors and users that know how to use xEdit, xLODGen or DynDOLOD already.
      Installation and Setup
      Download
      xLODGen beta 94 - based on 4.1.4b
      Unzip into a dedicated folder outside of any Steam, game or mod manager folders or special Windows folders like Program Files.
      Rename xLODGen.exe to [game mode]LODGen.exe (TES5LODGen.exe for example) or start with command line parameter -fnv, -fo3, -fo4, -fo4vr, -tes5, tes5vr, -sse, -enderal, -enderalse
      Use -o:"c:\OutputPath\" command line parameter to change where files are generated to, default is the game folder.
      Do not generate into any game, any mod manager folders or special Windows folder like Program Files x86.
      Requirements
      Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 - Required by LODGen.exe/LODGenx64.exe and Texconv.exe/Texconvx64.exe. Get matching platform x86/x64 depending on which xLODGen.exe (x86) or xLODGenx64.exe (x64) is used.
      RTFM and Share Results
      See the included Skyrim-Occlusion-Readme.txt for a brief explanation of the Skyrim TVDT Occlusion data generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions or give feedback in the dedicated Skyrim TVDT - Occlusion Data thread.
      See the included Terrain-LOD-Readme.txt for a brief explanation of the settings for terrain LOD generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions about terrain LOD in this thread for a more in-depth explanation if required and share feedback (with screenshots) about results or problems.
      These tools generate LOD meshes and textures "exactly" like CK, but not like the meshes and textures which are shipping with the games (they are often manually edited).
      However, these tools provide more options and higher resolutions (use the x64 version if there are memory errors because you believe you require 4k or higher) and can be updated to add more useful features and options.
      I did some testing in the different games, but finding the best combinations of options and settings requires lots of testing and are a matter of personal opinion and which game is used, the load order, mods, even different worldspaces probably.
      That means, I am only able to give generic guidelines and hints to send you off to find and test for yourself and share your results. My main interested is that generations works correctly and without problems for now.
      Check out the thread xLODGen Terrain Settings Compare. Also refer to any modding guide which has a list of relevant mods close to your load order.
      The object and tree LOD generation is the same as the current versions of xEdit / xLODGen. Refer to their respective descriptions and explanations.
      Obviously, users of Skryim/Enderal/Skyrim SE/Skyrim VR/EnderalSE continue to use the easier and more comprehensive DynDOLOD for drastically improved object and tree LOD generation and only use xLODGen for terrain LOD (and maybe Occlusion) generation.
      First Time
      Here are suggestion to start without going crazy and that should be quick enough to generate:
      Set quality of meshes for LOD4 to 5 and then +5 for each next level. Or just set levels 8/16/32 to 10.
      Check protect cell borders (yes it fixes the ugly terrain drops at outer cell borders that still exist in Fallout 4).
      Use the max vertices setting only if you want to hard limit max file size.
      In Skyrim Special Edition or Skyrim VR, if you notice terrain briefly flickering when new areas are loading in, set [Display] bEnableLandFade=0 in Skyrim.INI
      Set Optimize Unseen to off for LOD4 for first generation. Start experimenting with a value of 550 with a quality setting of 10 or lower for LOD32 (used for map) and compare coastlines and file size to other settings.
      To quickly generate terrain LOD meshes just for the map, check only terrain LOD Meshes, check the Specific Chunk checkbox and set drop down to 32. Leave SW fields empty for complete map or set SW cell coordinates to same values as a *.btr filename to test a specific area with lots of water, river etc.
      Set texture sizes to 512 for a start. Larger sizes and large world spaces will take a considerable time (like 15 to 30 minutes or more easily). Each higher resolution means quadruple the work.
      Use DXT1 for diffuse and 565 (DXT1 if on Windows 7) for normal maps. If generating for Skyrim Special Edition and VRAM is not of concern use BC7. Uncheck mipmaps, raise steepness and Bake normal maps.
      For now, leave the Brightness, Contrast and Gamma at 0 and 1.0 respectively. It seems that only Skyrim CK and Skyrim SE CK are manipulating the intensity of the textures to adjust for the noise.dds and the god awful "improved" snow shader of Skyrim SE (just turn that thing off, really). If textures seem too dark in the game, brighten the noise.dds instead or vice versa. That way you can get perfectly matching LOD textures that look just like the textures in the loaded cells. For Skyrim a good average color of the noise texture seems to be around #C0. See below for a couple noise texture downloads.
      If you want to test larger texture sizes, use the chunk option to limit the number of textures that need to be generated. For example, check [x] Specific chunk, leave the drop down empty and set WS to the lower left cell coordinate of an 32x32 area, like 0, 0. It will then generate all textures up to 31,31. Not all worldspaces have their origin at 0,0 so you will have to check already generated meshes/texture filenames for their lower left coordinates.
      Questions and Feedback
      Obliviously anything related to terrain LOD should be posted in this thread.
      Posts related to Occlusion should be made here.
      Recommended Optionals
      TES5-Terrain-Tamriel.esm (Mega), SSE-Terrain-Tamriel.esm (Mega)
      TES5-Terrain-Tamriel-Extend.esm (Mega), SSE-Terrain-Tamriel-Extend.esm (Mega) - These extend the sea of ghost further to the north (see screenshots)
      SSE-Terrain-Tamriel-Full-Extend.esm (Mega) - Entire map from -96,-96 to 95,96 with northern ocean extension. Useful for mod authors.
      Put in game data folder obviously. Adds back terrain for Skyrim (Tamriel worldspace) at the outer edges so there is no missing terrain meshes/textures when generating terrain LOD for Skyrim.
      Load as early with lowest priority as possible, so that any other plugins overwriting or adding land records or cells with the same coordinates take precedence.
      Only required to be loaded when generating terrain LOD. No harm done when loaded in-game but typically the player can not get close to these areas. There are no effects outside the far away added cells.
      Noise
      Single color flat noise, Adjusted vanilla noise, HD Terrain Noise Texture SE
      Examples for Skyrim. Install to game folder like any other texture mod. The noise texture is applied in-game on top of terrain LOD textures, so no effect for LOD generation.
      Only the red channel is used in case the textures is not a grey channel format. MipMaps are ignored. The textures is tiled 3x3 per LOD quad, e.g. for LOD level 4, the noise texture is repeated 3 times to cover 4 cells, for LOD level 8, the noise texture is repeated 3 times to cover 8 cells and so on.
      Test-Terrain-Tamriel.7z
      For testing terrain LOD distances. Plain color terrain LOD textures for Tamriel with coordinates for every LOD quad. Green for LOD 4, yellow for LOD8, blue for LOD 16 and red for LOD 32.
    • By Lili_Cakez
      In the main YouTube tutorial I think it was said to redo the entire install if your load order changed,  but is that just for graphical mods that might affect LOD? I tend to find new outfits or jewelry I want to install mid playthrough and I was wondering if I can just install those without redoing TexGen and DynDOLOD. From what I can see, the load order for my graphics mods do not change as far as dependency when I run LOOT after installing a non graphical mod, but I wanted to check before I tried anything. Also, can a Bashed Patch be rebuilt without having to regenerate LOD?
    • By rolandito
      Anyone have thoughts/comments on their experience running Realistic AI Detection in STEP LE?
      I see that it's part of the loadout for STEP SE and wondered if there were some specific conflict or other reason it wasn't included in the LE guide?
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.