oqhansoloqo

EDIT: I don't see how the results are even: 4 to 7? That's what I counted. phazer11, Octopuss, EssArrBee, TechAngel - for STEP box. WilliamImm, Aiyen, Harpalus, darkside, kryptopyr, Neovalen, oqhansoloqo - for BG (Gamwich option, presumably) box.

Oh, yes, you are right. I missed that before, probably because I thought the fadingsignal version looked so much like the vanilla box I didn't realize it was an improvement. After reviewing again, it (fadingsignal's version) is an improvement, but just not much of one. So actually, Harpalus poses a good question. I'm still going to assume that people meant the Gamwich version though.

The instructions for CCO in STEP say "Install the Complete Crafting Overhaul main file and the Complete Crafting Overhaul - Hotfix optional file." What about the optional file for the mod called "CCO Compatibility Patch for WAF True Weapons"? It says this for that file's description on the Nexus mod page: "Compatibility patch for use with either Weapons & Armor Fixes Legendary Plus or True Orcish and Daedric Weapons. This file should take the place of Weapons & Armor_TrueWeaponsLvlLists.esp and should be placed at the very bottom of your load order." It was uploaded on the same day as version 1.6 of the main file, which are both 1 day after WAF's newest version appeared on the Nexus. Do the STEP instructions need to be updated?

When they say "the textures from this mod", I assume them to mean "Barenziah's Glory". Apparently the box texture from this mod was either provided to Saerileth by Gamwich or Saerileth was given permission by Gamwich to include Gamwich's box design in Barenziah's Glory. I don't understand where your question about "fadingsignal" is coming from. What does that mod author have to do with this - did that mod author contribute in some way to SLOD or Barenziah's Glory?

Me too - though I don't feel strongly about which box, I do prefer this mod's for the reasons I previously mentioned.

My only question right now is: why did it take this long for this mod to be accepted? :)

In the mod author's own Nexus description tab, he says that one of the "Known Issues" is "Going into ragdoll mode when weapons are out causes you to be launched into the air." So did he already describe it perfectly as it is, or is his description incorrect (i.e. what happens if you put your weapon away [in other words - go out of combat mode] and get hit with a knockdown then - does it still cause the issue?)?

I like Saerilith's (AKA Gamwich's). While Dracomies' box does look pretty good with the choice of contrasting textures/color shades, when compared to vanilla, it is more of a deviation from vanilla than Saerilith's design. Saerilith's design seems more consistent in quality throughout the whole object, while Dracomies feels kind of only partly done. Also, Saerilith's (and the vanilla design) feels almost like a dwarven design, versus Dracomies' which feels like something completely different. Just my observations...

How soon - if it sounds like it's going to take a while, maybe it should be held off like True Wolves of Skyrim for now?

It does sound like a great idea for windows in general, but I agree that the fact that it's limited to farmhouses lessens the usability of the mod - the farmhouse windows thus become pretty inconsistent with the windows of other buildings in this way. If anything, farmhouses should have the cheapest windows that aren't so nice and clear, versus some other wealthier building windows that would be of finer quality.

One thing I wonder about is what it (the arrow issue) looks like in 1st person with a female character using the Enhanced Camera mod, since EssArrBee is pushing for that one to be in the guide. Has anyone tested it? I've never installed the Enhanced Camera mod, but I'm interested in it possibly in the future (if it's determined to not cause other issues) since I always play in 1st person. Other than that - I prefer to have the BSW quivers over CQLA distorted quivers... EDIT: Oh, just realized that Enhanced Camera is now accepted into the guide, which makes the question even more pertinent.

If that's the case, why don't they have another mod page with the name of something like the "Unofficial SKSE Patch" to be able to cover all of the fixes that require SKSE? It would be easy to do that in order to cover those types of fixes, so I'm thinking that maybe they just don't want to, because of the simple fact that they didn't decide to create a separate Nexus mod page to do this. It would be a welcomed endeavor though. Then people can go to one source to rely on a number of these sorts of fixes in one single plugin file, instead of a whole bunch of different mod pages that each have their own separate plugin files to cover the different fixes.

OK, found it. Thanks. :)

Where is the admin dev thread (I used to know but forget now), because I can't stand doing conflict resolutions on stuff already included in STEP. It's just too much hassle for me, especially when I know that I will be having to go back into my custom patch at a later date to remove all of the edits that the STEP patch ends up covering anyway. I prefer to only resolve conflicts in my custom patch with extra stuff that I add in on top of STEP (the only exception to this that I can think of is all of the UP fixes that EBQO doesn't forward, because I think those are pretty major). EDIT: Another element to this is that I don't always know what STEP's vision is with choosing the edit of one plugin over another, since I don't always understand exactly why different plugins have different values or the reason behind the decisions (for example - the differences between Clothing and Clutter Fixes values versus WAF values or CCO values). I prefer you (STEP) to make these decisions for me, since I trust that you have a much more in-depth understanding of all of that since you talk about this stuff with the mod authors and coordinate changes between them with the authors oftentimes. On the other hand, when I install my own custom mods on top of STEP, I know why I am adding those mods on top of STEP and I am also forced to make judgement calls... so I do it because I have to. If I start making extra judgement calls on STEP-included mods, then I foresee a much higher likelihood for unwanted and unintended consequences of making the wrong decisions.

SRB's not really been spending much time with FNV lately - his first priority has been Skyrim STEP stuff and probably will be until STEP 2.2.9.1 is out.

I don't even know what "SPIKEWeapElvenBlade [KYWD:01DA014F]" does really, but it's a keyword not carried over by the STEP Patch for Weapon - POIMageBorvirsDagger from Weapons and Armor Fixes Remade.esp. This may have been from WAF's newest version or there previously also - not sure. Just thought I would mention it. EDIT: Damage for Weapon - The LongHammer from WAF TrueOrcish(etc)...esp needs to be changed to 11 in the STEP Patch too now, and the weapon value, etc...

The STEP installation instructions are confusing and wrong now. I see part of the mod instructions were updated yesterday, but they still don't make sense. It still says this: "After the main file is installed, install the optional ''Improved Closefaced Helmets _ WAF compatible version'' file. Choose merge, activate the plugin, and run LOOT to sort and add the rule below."

This mod seems intriguing...

I think with any of the lighting mods that are in plugin (esp/esm) format, you are going to run into issues with conflicts with a lot of other mods that make "Cell" and "Worldspace" edits. What I did is go through a very tedious process of "Cell" and "Worldspace" manual custom conflict resolution. IOW - I used TES5Edit, with all my mods selected and filtered to show conflicts, to create my own patch plugin that combines values from all conflicting plugin mods. I manually went through all yellow and red highlighted values and grabbed the desired values and placed them into my overriding custom patch plugin.

Agreed - that can take up a crapload of prime real estate space.

Isoku - your contributions to Skyrim modding are greatly appreciated, and you are still improving your creations. Thank you so much for all of your work and for sharing it with all of us.

The meshes would also have to be compatible with vanilla-compatible textures too - right?

Sorry, I took this discussion off topic a bit..

OK - I was under the impression that 1st person perspective mods took only 3rd person animations and allowed the player to see them in 1st person. I am unsure as to whether or not it does this with all animations (even animations that normally have 1st person views), or just does it for the ones that normally don't (and leaves the animations that can normally be viewed in 1st person the same). I tend to think it would replace all of the animations with the 3rd person ones (viewed from 1st person), but maybe (hopefully) I'm wrong.

BTW - the guide mentions marks the mod as having a HQ option. I don't see one on the mod's page - is that a mistake?