z929669

OK, thanks again On another note: I updated the "Detailed Instructions Available" template so that when clicked in mod notes on the Guide, it opens into a new tab rather than advancing to the mod page and forcing users to use the 'back' browser function (which is a real PITA when following the guide).

This is intended. HQ Snw diffuse maps are still an enhancement (See the OP ... the HQ Snow version is how it looks with TB normals and HQ Snow diffuse) The performance version of TB (on the Nexus) is already optimized via DDSopt. It converts from 888 uncompressed to Ethatron's 565 uncompressed (not to DXT compressed), which shaves off about a third of the size without any noticeable impact on quality.

Patches updated on the Nexus Removed in 2.2.6

Nope, you guys are correct :P I DO NOT have Extended installed :facepalm: I'll change it all back ... Looks like Bugs got fixed already (thanks). Distant Decals should be fine though (if we even need that one anymore)

@z, I already did they should be up now. I already 'fixed' according to roots' post, so go ahead and revise if you want ... I checked overwrites, and Bugs should not overwrite if users install according to our recommendations ... Bellyache's should not be replacing any bug textures ... ?

But in game, vanilla texture looks totally fine. This is exact same thing with a color difference only, no? If you think the color is more realistic, then I am in favor. This particular mod is worse than vanilla, IMO, because it is unrealistically 'perfect', and the history of this thread reveals that others agree. It is not that big a deal, but certainly if a mod does not present an obviously better result than vanilla ... in all ways ... then it should not be used, right?

@SRB I ask this again. Do we even need AOS patches, since we have the STEP Patch?? EDIT: NM, I see now :P Also, this and AOS were both missing from the 2.2.8 guide until just this minute. Where did you have them in your install when you created the patch??

I move to drop this mod ... anyone adamantly disagree?

Best make a new patch version then, since STEP is a precursor to larger builds. Thanks (and I agree on dropping Septims HD ... will post on that.)

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. As per the 2.2.7 release, STEP:Core is essentially final with the 2.2.8 release and is represented by only installing mods marked as "Core" in the STEP Guide. We are gathering screens of this base install now and verifying that it includes everything necessary but nothing more than that --all according to the new STEP:Core Mandate. Anyone that has not yet read that, please do so to better understand the direction we are heading. Now begins our focus on STEP:Extended for the 2.2.9 release according to the STEP:Extended Mandate, which opens up the door to new possibilities. This is our final step towards 2.3.0, which will fully integrate Packs and the new paradigm alluded to in our Nexus article. Once STEP:Extended is finalized in the 2.2.9 release, we will be ready for the paradigm shift. This shift will not be that drastic, since we will have made most of the really obvious changes already, not least of all, those introduce in 2.2.8. v2.2.9 ChangeLog 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 in Mod Testing (MT) marked [ TESTING ]. For non-replacers, please head over to MS and read the Announcement. Then go into the testing thread and contribute some test ideas or some of your own test results. 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!

BUG REPORTS ONLY PLEASE! Please post any bugs or issues that you think may be related to this release on this thread. Those issues will be fixed, if possible, in the next STEP update. Progress on the next STEP release can be found in this forum. Make sure to check back often for updates! v2.2.8 Changelog (changes made since initial release)

I am inclined to simply package each of your patches separately. It should be obvious how to use then, given your ReadMe, the STEP Patch 'mod' instructions and the Nexus descriptions I am about to load now .... Also, users should only use one, but even if they for some reason used both, it would not matter (unless they did not install Extended). If they both exist in a BAIN installer, then far more people would wind up installing both I think Yes, I will be definitely polishing up the User contributions area, noting the immense help of SoubleYou and EssArrBee this release ;) Agree that the STEP Patches should be 'installed' last, but that it does not matter much, since there are no resource conflicts with the patches. They must be sorted and activated accordingly only. (do we have a not in to the BOSS team about these patches? They should always be installed last, just before the Bashed Patch.) @EssArrBee You will need to train me in maintaining your patches, just in case you win the lottery or something. It is always good to have a backup ;) @DoubleYou I agree with all of your proposed methods, so if you are inclined to make those updates ... EDIT: Also, we desperately need representative screens of STEP 2.2.8. Something more than just landscape screens. Any volunteers or ideas about getting them?

Thanks for confirming that it works! Next questions: Was it easier to follow 2.2.8 than previous versions?Did you follow 2.2.8 exactly, or did you use it more as a guided setup?The 2.2.8 guide is in much better shape than 2.2.7 ever was. :) I used the entire STEP 2.2.8 Extended almost to the letter, selecting HQ options wherever possible. I did add Clothing and Clutter fixes and replaced Ars Metallica with Complete Crafting Overhaul, so the STEP patch wouldn't work for me anyway. Next step is to create my own, personal STEP patch by combining some .esp files in Tes5edit. The guide is still missing a short clarification about patches in general: while you DO have to follow the installation order for mods in general, patches that are specific to conflict resolution can only be installed but NOT enabled until the mod that specific patch is for has been installed. Trying to benchmark STEP after 2.D. Fixes will cause a CTD otherwise, and will continue to do so until 2.M. Gameplay mods have been installed. However, there's no need for the user to worry about .esp sorting mid-install (missed this clarification, badly, during 2.2.7 install), just use BOSS for it if benchmarking is required. A short notice after each section about which .esp files are safe to activate at that point would be nice. Skyfalls & Skymills and Improved Closefaced Helmets have .esp files that BOSS doesn't currently recognize, a short notice about possibly needing BUM for these two could also be in order. Quick edit: Real beginners to modding could also need a pointer that yes, they need to manually activate DG, HF and DB .esm files in MO since those aren't activated using MO's default settings. Quick edit 2: A note about updating FNIS, DSR and Bashed Patch is needed. It's ok to make their output into new mods the first time, but I'm assuming you need to do some manual copying from overwrite to their respective "mods" if anything else happens to the load order after the initial STEP install and these need to be rerun. Very nice feedback. @DoublYou, EssArrBee or anyone else Would you care to address some of these issues in the guide? I am going to get started with the update procedures for Nexus. Should we move the STEP Patches to end of the install?

I think the main thing people worried about is unknown executables. Not that you are doing anything wrong but the internet is terrible place. Sent from my iPhone using Tapatalk Agree. Since it has been brought up already multiple times, would you be so kind as to post the source to validate that you have no malicious intent? Just as a courtesy? Making your source always available for all version releases is just polite in these cases, no?

Thanks for confirming that it works! Next questions: Was it easier to follow 2.2.8 than previous versions?Did you follow 2.2.8 exactly, or did you use it more as a guided setup?

You call it R&B, I call it hip/hop and rap (not a fan myself) ... R&B was The Spinners and Barry White (see my post p1) and EW&F. I also don't play nicely with C&W, but I generally like almost everything else (see my post)

Fair enough, but youare missing out. STEP 2.2.8 will default to MO, and life is much simpler if you do use it. Many very nice tools are included (Trust me, I am the last convert over here ... I was dedicated Wrye Bash until this past Fall). RE sheson's solution (the topic of this thread). STEP will give it honorable mention and point users to the three variant methods by which to employ this currently, but we won't be including this as an official 'mod' until it stabilizes intot he final SKSE solution (I only hope that they incorporate the entire thing in the most sustainable manner possible).

Yep. Lets give it all honorable mention in Troubleshooting for CTDs and ILS but leave it out as a 'mod' until it stabilizes. We can then dynamically add it to the live release.

Relighting Skyrim just got some updates, and this is the most likely mod that would ever make it into STEP:Extended.

I am not sure we should be recommending the new SKSE build (or even sheson's patch in the guide). The solution needs to evolve to final resolution (and STEP does not really suffer from the issues this solution addresses). ENBoost MM takes care of borderless windows ... Let's determine if/how we integrate MemPatch 3.0, since it will likely morph drastically over the next week or two.

Need some of the STEP people to provide feedback on this. Does it resolve standing issues? Does it provide a better solution than existing mods? Is it simpler to use? Who should be using it?

1024 is fine.

Should we be using this, given that we have the STEP Patches? It may be redundant, as this adds several plugins.

Then this is a conflict and we should hide the SkyFalls meshes, no? I've found FPS limiter, where do I set PresetInterval? I have following settings avaiable: OGL_TRIPLE_BUFFER_ENABLED OGL_TRIPLE_BUFFER_ENABLED 0x00000000 (Overwatch Systems Remoteview Pro, BAE Systems SOCET GXP) 0x00000001 (ISD HiCAD, Overwatch Systems RemoteView, BAE Systems SOCET SET)Don't use FPS limiter unless you really have to. Use enblocal.ini vsync instead, which should yield a much better result. FPS limiter (enblocal.ini) should be used only if vsync (enblocal.ini) does not behave for some reason. (vsync and FPS limits should not be used in conjunction ... it is redundant in almost all cases) iPresentInterval is in skyrimprefs ini under [Display]