z929669

I think that any transparency AA will affect Skyrim regardless, just as SSAA does. It is even possible that MSAA does, but with AMD cards, it must be the exact same technique used, as there is no discernible difference.

@SRB What about the Improved closed-faced armors patch from WAF? is that still needed with the STEP patches or are they merged?

We are sorely lacking in the MT department. None of our official MTs are doing any testing for us, and we will likely need to solicit others to replace them. Hopefully, this will improve once we release 2.3.0 (or 2.2.8 for that matter) Tech is out, so there is nobody really rallying the crew anymore, and I don't have the time, so I just solo the guide, release and website dev with s4n.

Sounds fine to me. Any conflicting issues with STEP?

Yep, lots of rules get broken, and they are not enforced with regard to mod permissions unless the original author comes crying to Nexus staff ... it is too much maintenance for them to police mods proactively, so they are reactive. This means that any mod author with a grudge could go complaining about somebody and likely get them banned or closely scrutinized without providing much beyond their word.

Yes, lots of good info in the guide, but it just was not ready for serving as an ancillary guide to the STEP main guide.

New readme is much better. Thanks!

To add this to the wiki, just load up the page: https://wiki.step-project.com/Form:Mod then enter the name of the mod and proceed.

If Core is good for 2.2.8 (have you looked at the 2.2.8 Core mod list?), then that is all I am worried about. Also, what readme? they are all out on Git.

Discussion thread: Clothing and Clutter Fixes by kryptopyr Wiki Link Clothing & Clutter Fixes ... seems like an obvious addition for STEP. I'll be testing in my own game, but any advocates out there? Accepted for STEP:Core 2.2.9 MT Notes: To Do Notes: Would be a good idea to open up in TES5Edit with Core and then Extended to see what this conflicts with. Evaluate the need of Diverse Priests, which the author, kryptopyr, said is not needed any more. Decided on Core or Extended placement.

I get that a lot of people like this mod. It is well done and convenient. I just personally don't agree with the premise, and I think it is better suited as a Pack mod.

Question: Why on Earth would you want to throw that kind of money into a GFX card? It will be worthless in two years ... If you have loads of cash to burn and are set for life, I get it. But if you are a normal person, never buy top of the line. Shoot for high-mid end and pay no more than $400 for a video card. That will buy you plenty of power for any game. I got my Radeon 7970 recently for $280, and my frame rates and GFX are fantastic and will be for any game over the next two years ....

Regarding patch for Extended and WL ... WL is dropped for now and may even be the case for 2.2.8. (see that thread in Mod Testing for details), and Extended will be going through significant changes in either 2.2.8 or 2.2.9, so expend energy as you wish with that in mind. WB Bashed Patch for Skyrim has only limited functionality (one of the reasons we support MO for STEP now), as the main developers are our of the picture as far AFAIK. It would not surprise me if the stats were buggy or broken. Only merge and LL work last I checked. I really want someone to write a plugin for MO that will handle the dynamic, load-based patching and mergers as the BP is supposed to work.

nice trees and web!

You should definitely limit FPS and follow the advice of the Nvidia Inspector guide on this tab. It has nothing to do with performance for your card and everything to do with quality (remove microstutter with maximized FPS and avoid screen tear, optimize AA in for Skyrim, etc). Can't help you with the mod troubles, Im afraid. You should post on the mod thread or in support & troubleshooting on that topic.

It turns out that I have been looking at this exact issue for a few days now and am adding our "official" instructions to the STEP 2.2.8 guide now. Basically, if you have a high end video card that is capable of pushing frame rate beyond the monitor refresh rate at least some of the time if not more frequently, then it is worthwhile to cap frame rate to 2/3 of the monitor refresh rate, enable triple buffering, and set vsync to "always on". Do as much as possible using the graphics software and turn off ENB and Skyrim INI redundancies. For low to mid end cards, this is all optional and should be done only if performance is unaffected (i.e., FPS do not suffer more than a frame or two on average). The ATI and Nvidia wiki guides are updated to reflect this advice.

You did mention to only use one patch ... STEP Core patch or STEP Sos Patch? (I assume that you could use both, because why would anyone use a STEP patch if STEP was not installed, and if STEP is installed, STEP:Core must be installed). Also, I am still not clear on the Bashed Patch by your explanation preceding. Do you or do you not tag the STEP patches with stats? Only when not using a Bashedd Patch? If so, then that does not make sense, since tagging is done in WB, and it makes no sense to use WB and NOT use the Bashed Patch. Anyway, my point is that the readme needs to spell every angle out explicitly, or people that think too much (or don't think enough) will fill in the gaps with other info, which will usually be incorrect info ;) Anyway, thanks for working on these. They will be great additions. (you may want to add a note about how others could use the STEP Core patch "to grow off of and fork" as you stated above.)

Great request, and I would also like to know about sorting mods by install order in MO and using a mod-order config file to define (i.e., the WB Installers.dat file for instance). About mos sorting/arrangement in MO: WB allows moving mods within the order in multiples by selecting all, right clicking and entering a number that applies to all, moving them but keeping their relative order. This is very convenient in designing manual algorithms to achieve a particular install order en masse, so I am wondering if such context-menu functionality can be implemented in MO (unless it already is and I am just not seeing it).

Before I put these onto the Nexus page, I think that the readme will need just a bit more explanation on the SoS patch and the lanterns patches (if still applicable) ... SoS = Sounds of Skyrim? Can you describe why users should use all of these patches and under what conditions they would or would not use? TIA EDIT: also the readme mentions adding the WB stats tag and loading the patches last before building the Bashed Patch, but above you mention not to check stats for BP. Also, what is the load order of STEP patches if more than one is used? Lastly, what needs to be done for 2.2.8 (see the guide in progress, as more has been added to core and there are a couple of mod changes)?

A NMM installer would be great. I have added more options to the original, so if you create an installer, be sure to use the most updated main file (1.5.4) and follow the wizard for all correct options. I can add you as a contributor if you want ... Done.

Great, thanks. I'll update the 2.2.8 dev guide accordingly.

Nope, just do as you have been. I mainly wanted to determine how much the patch overlapped with the BP once it was built. I will need to add instructions to install WB for creation of the Bashed Patch and will note the crime radius and timescale tweaks.

OK, so tell me how this works with the Bashed Patch ... is BP even needed with this patch? I would suppose not, but what about the WB crime radius fix and timescale adjustment functions of the BP? Can these be incorporated?