STEP SE Core Beta Released

[z929669]

Running through the System Setup Guide, I got to driver install and saw the AMD & Nvidia sections but couldn't find either of the Setting Guides mentioned. Are these TBD or are they intended to be an external link?

These guides are outdated and in need of update to the relevant application versions and the current guide for SE (now that we are not using things like ENBoost). I have added the links back for some hints and so that someone with the latest hardware/drivers can do that.

[z929669]

From the Tools Installation section

I'd recommend changing this to

 

Standalone applications and portable applications are generally the same. Their installation locations aren't registered with the OS, so other applications don't know where to find them. Which is great when you want to have multiple installations for different games. If the intention is to have tools registered with the OS so that they're used by all games, shouldn't we be recommending the installer versions over the standalone?

Most if not all of these applications likely do not register properly with the OS, or they do so in such a way that complicates their use as portable apps that can be applied to different applicable games (for example, some may be configured to recognize Skyrim but not Skyrim SE ... or Steam vs non-Steam games, etc.).

[Thac0]

*nods* I can understand not using the installers due to issues with OS registration. Maybe 

      "This means we store data in a users profile instead of the application's installation directory so the tool can be used for all games"

 

instead of 

 

      "This means a tool is installed once and used for all games." 

 

*shrugs* I'm not sure why, but that phrase just rings as problematic in my head. If this doesn't bother anyone else, just ignore me ^-^.
---
While I'm going through this install process, is it worth capturing minor discrepancies in the FOMOD instructions (such as a forced option not included in the wiki)? Will tracking those differences now help the site rebuild down the road? I know the wiki is just temp, so I don't want to suggest busy work changes.

[Decopauge123]

*nods* I can understand not using the installers due to issues with OS registration. Maybe 

      "This means we store data in a users profile instead of the application's installation directory so the tool can be used for all games"

 

instead of 

 

      "This means a tool is installed once and used for all games." 

 

*shrugs* I'm not sure why, but that phrase just rings as problematic in my head. If this doesn't bother anyone else, just ignore me ^-^.

---

While I'm going through this install process, is it worth capturing minor discrepancies in the FOMOD instructions (such as a forced option not included in the wiki)? Will tracking those differences now help the site rebuild down the road? I know the wiki is just temp, so I don't want to suggest busy work changes.

Both sentences (I think) get the point across, but yours is (to me) less ambiguous because it briefly describes the process.

[TechAngel85]

*nods* I can understand not using the installers due to issues with OS registration. Maybe 

      "This means we store data in a users profile instead of the application's installation directory so the tool can be used for all games"

 

instead of 

 

      "This means a tool is installed once and used for all games." 

 

*shrugs* I'm not sure why, but that phrase just rings as problematic in my head. If this doesn't bother anyone else, just ignore me ^-^.

---

While I'm going through this install process, is it worth capturing minor discrepancies in the FOMOD instructions (such as a forced option not included in the wiki)? Will tracking those differences now help the site rebuild down the road? I know the wiki is just temp, so I don't want to suggest busy work changes.

If you're wanting more detail, then your statement is not accurate because users can install the tools anywhere (i.e., to a separate drive, which all users on the system can access). Therefore, "This means each tool is installed once to a single location and that install is used for all games it supports." ...is more accurate.

 

You can note them and I can fix them. We'll be redoing everything from scratch when we port it to the new website because the wiki templates can't be copied over to our new widget feature. So they'll be redone instead of just copied and pasted over.

[Thac0]

 

You can note them and I can fix them. We'll be redoing everything from scratch when we port it to the new website because the wiki templates can't be copied over to our new widget feature. So they'll be redone instead of just copied and pasted over.

I'll try to stick to the ones that seem easily tripped over then. No need to clean them all up if the original installer is going to be referenced for the rebuild rather than the wiki. Happy to volunteer for some of that when it's time. 

[TechAngel85]

Updated the Lighting & Weather Patch for Cathedral Weathers and Seasons v2.0.

[Thac0]

I've installed down to FNIS, started double checking all my installs to make sure I didn't miss any detailed instructions (I did). I'm trying to view this from a non-tech savvy user's POV. Here's my notes so far. Feel free to discard anything not useful:

STEP SE Core Guide -> There should really be a warning about how time consuming this process is at the front of the guide in bold somewhere, with a recommendation to take breaks. In the site redesign, I'd highly recommend some hourly break points or time estimations. 
---
Mod Organizer, After step 5, Mod Organizer prompts to "handle nxm links". 

 

Mod Organizer -> Tool Setup -> Step 4: -o:"Path\to output\folder". (Recommended location? Also doesn't use <path> convention)

 

BethINI asks if it should Modify Custom INIs. 

 

Standard Cleaning Procedures pt 1 -> Step 5. No prompt was given.

Standard Cleaning Procedures pt 2 -> Step 1. MasterName.esm doesn't follow <> convention.

Standard Cleaning Procedures pt 2  -> Step 3. Suggest adding "In a new window, open..." to prevent user from reusing window.

 

Dawnguard.esm - Manual cleaning instructions hit a dead end due to SSEEdit change. See comment https://www.afkmods.com/index.php?/topic/4110-manual-cleaning-skyrim-and-skyrim-se-master-files/&do=findComment&comment=175204 . May be worth writing these instructions into the guide given the OP isn't maintaining the post anymore. Or include a script to be run if that's possible?

 

----

STEP SE Core Modlist (General Suggestions)
- Use "Detailed Instructions" instead of "Detailed Instructions Available". Some of the detail instructions look to have required steps. "Available" could be misread as "optional". Or perhaps add a note about detailed instructions to the "keep the following in mind" list.

- Might be worth a note at the top of this section that File names and Nexus mod names can be radically different from each other. It can be easy to get lost.
- Might be worth noting some downloads will take a while under the free plan. Might be worth making a list of the largest mods to start downloading the night before.

 

SKSE Detailed Instructions - Consider adding note in install instructions that File download can only be found under mirrors.

SKSE Detailed Instructions -> Scripts step 2 - Consider specifying SKSE64 so SKSE64/SKSE isn't used by mistake (Yes, the image makes this clear, but it might save someone a step)

 

Skyrim Skill Uncapper -> Might mention that xSHADOWMANx's DLL loader isn't needed. nexusmods doesn't make this readily clear.

 

aMidianBorn Book of Silence -> Bottom of detailed instructions -> Doesn't walk through hiding a folder. First instance of needing to do so in this guide.

 

Detailing the Eldrich (SE) -> Not packaged properly. May need detailed instructions to walk users through fix.

 

Dragon Priest -> FOMOD Option - Modified inhale effect as preferred? 

 

Sabercat -> FOMOD option - Valecat? (Given some previous mods don't use specific files due to using another mods textures, this option looks like I could break something down the line)

SKELETON -> FOMOD options - Skin only; skin, clutter, sounds; skin, clutter, no sounds? (These look like I could break something if I chose the wrong one.)

 

The Elder Scrolls V Rewritten - Arvak SE -> Not the optional file. Maybe specify version or "main file" to improve clarity. Potentially confusing due to significant name difference between Nexus name and File name.

 

Vistant's HD Night Sky SE - FOMOD options? (These look friendly to chose\customize from, but suggestions might be useful to some)

 

Better Animal Footsteps - FOMOD option - All footstep sounds as preferred?

Coverkhajits - Notes should read "both Main files" not "both Mail files"

 

Vanilla Makeup HD - Should femalelowereyesocket fix be installed?

 

SSE Engine Fixes - Detailed instructions, last sentence - "Leave the rest of the settings at their defaults"

 

Mors Arrows Be Gone - Packaged incorrectly. Might be worth noting that October update breaks save game compatibility.

 

FNIS - Packaged incorrectly. 

 

----

Happy New Years everyone! Time for me to take a break. ^-^

[TechAngel85]

 

I've installed down to FNIS, started double checking all my installs to make sure I didn't miss any detailed instructions (I did). I'm trying to view this from a non-tech savvy user's POV. Here's my notes so far. Feel free to discard anything not useful:

 

STEP SE Core Guide -> There should really be a warning about how time consuming this process is at the front of the guide in bold somewhere, with a recommendation to take breaks. In the site redesign, I'd highly recommend some hourly break points or time estimations. 

---

Mod Organizer, After step 5, Mod Organizer prompts to "handle nxm links". 

 

Mod Organizer -> Tool Setup -> Step 4: -o:"Path\to output\folder". (Recommended location? Also doesn't use convention)

 

BethINI asks if it should Modify Custom INIs. 

 

Standard Cleaning Procedures pt 1 -> Step 5. No prompt was given.

Standard Cleaning Procedures pt 2 -> Step 1. MasterName.esm doesn't follow convention.

Standard Cleaning Procedures pt 2  -> Step 3. Suggest adding "In a new window, open..." to prevent user from reusing window.

 

Dawnguard.esm - Manual cleaning instructions hit a dead end due to SSEEdit change. See comment https://www.afkmods.com/index.php?/topic/4110-manual-cleaning-skyrim-and-skyrim-se-master-files/&do=findComment&comment=175204 . May be worth writing these instructions into the guide given the OP isn't maintaining the post anymore. Or include a script to be run if that's possible?

 

----

STEP SE Core Modlist (General Suggestions)

- Use "Detailed Instructions" instead of "Detailed Instructions Available". Some of the detail instructions look to have required steps. "Available" could be misread as "optional". Or perhaps add a note about detailed instructions to the "keep the following in mind" list.

- Might be worth a note at the top of this section that File names and Nexus mod names can be radically different from each other. It can be easy to get lost.

- Might be worth noting some downloads will take a while under the free plan. Might be worth making a list of the largest mods to start downloading the night before.

 

SKSE Detailed Instructions - Consider adding note in install instructions that File download can only be found under mirrors.

SKSE Detailed Instructions -> Scripts step 2 - Consider specifying SKSE64 so SKSE64/SKSE isn't used by mistake (Yes, the image makes this clear, but it might save someone a step)

 

Skyrim Skill Uncapper -> Might mention that xSHADOWMANx's DLL loader isn't needed. nexusmods doesn't make this readily clear.

 

aMidianBorn Book of Silence -> Bottom of detailed instructions -> Doesn't walk through hiding a folder. First instance of needing to do so in this guide.

 

Detailing the Eldrich (SE) -> Not packaged properly. May need detailed instructions to walk users through fix.

 

Dragon Priest -> FOMOD Option - Modified inhale effect as preferred? 

 

Sabercat -> FOMOD option - Valecat? (Given some previous mods don't use specific files due to using another mods textures, this option looks like I could break something down the line)

SKELETON -> FOMOD options - Skin only; skin, clutter, sounds; skin, clutter, no sounds? (These look like I could break something if I chose the wrong one.)

 

The Elder Scrolls V Rewritten - Arvak SE -> Not the optional file. Maybe specify version or "main file" to improve clarity. Potentially confusing due to significant name difference between Nexus name and File name.

 

Vistant's HD Night Sky SE - FOMOD options? (These look friendly to chose\customize from, but suggestions might be useful to some)

 

Better Animal Footsteps - FOMOD option - All footstep sounds as preferred?

Coverkhajits - Notes should read "both Main files" not "both Mail files"

 

Vanilla Makeup HD - Should femalelowereyesocket fix be installed?

 

SSE Engine Fixes - Detailed instructions, last sentence - "Leave the rest of the settings at their defaults"

 

Mors Arrows Be Gone - Packaged incorrectly. Might be worth noting that October update breaks save game compatibility.

 

FNIS - Packaged incorrectly. 

 

----

 

Happy New Years everyone! Time for me to take a break. ^-^

 

Thanks for this report! It was really helpful in tracking down small bugs like that! I've taken care of most of it in one way or another. You can see the changelog.

 

I'll get to Vistant's HD Night Sky SE whenever it become available again (it's currently hidden for an update).

[TechAngel85]

For general support on the STEP SE Core Guide, please use the new support forum.

 

This thread can be continued to be used for general feedback. If you're posts are missing, I've split them out and moved them to the support forum.

[DreamerSteamer]

Little question, the mods that are marked as accepted in the STEP SE Mod Anthology but not included in the guide like CACO, are they just not implemented yet and will be in the full release or are they accepted for a possible future STEP Extended? (I know, there is no STEP Extended on the horizon right now)

[TechAngel85]

Little question, the mods that are marked as accepted in the STEP SE Mod Anthology but not included in the guide like CACO, are they just not implemented yet and will be in the full release or are they accepted for a possible future STEP Extended? (I know, there is no STEP Extended on the horizon right now)

They're accepted for an upcoming v0.2.0 release that I just need to sure up some things on.

[wojsku]

Just wanted to say that I'm very excited and I can't wait for the new release of the guide. Some fantastic mods have been accepted.

 

Also, I want to mention that the guide is really performance friendly. I travel for work quite a bit and I only have a work laptop available when I'm away. I was stunned the other day when, I was able to play in 1080p with the full mods install from the guide on my work laptop. The laptop has GTX 1050 and does 45-60 fps. It is a result of a fantastic work that everyone involved put into it. Well done everyone and big thank you.

[TechAngel85]

I've gotten busy with work and my free time I've been spending doing some things that allow me to destress. I've worked on the Guide some more tonight, though. I need to sure up the Patches and then do a test run.