Thac0

This is showing dropped for 2.2.0? N/m - Replace by ng version I presume:

Gah, yea, alright now the edges are eating at me. That's going to regularly bring me out of immersion. I think that's a pass on at least Terre's for me. I'm up in the air on CoverKhajiits.

This is tough. While I like the patterning on every vanilla asset better, I do think the new textures are a better quality. The finer brush strokes of the new textures add a significant amount of depth to looking like fur. But I completely see the arguments of hair length change and consistency. This mod does give the appearance of a short hair cat vs a med hair cat. I'd be happier if the consistency was better and either the new patterns were more in line with the vanilla even brindle pattern or kept the medium/long fur look. As is, I think the combination of fur pattern and length changes are different enough from vanilla to warrant dropping these two. EXCEPT, I think most gear would hide these shortcomings, and the improved textures are meaningful improvements over Tempered Skins alone. While I may be less happy with CoverKhajitts+Terre's during character creation, I think the experience while adventuring in the world would be improved for most players. As such, I would vote to accept/keep both of these despite their shortcomings. I think I flipped like 4 times while writing this. >-< Factoring in gear cinched it for me though. I'm pretty solid on keep. 5 times. Now I can't unsee the texture boundaries when they're uncovered.

No. I don't think I will. Requiem deviates from the vanilla experience, and Step is about providing a "a very stable game with an enhanced, vanilla experience." Also, maintaining a fork for a single mod as someone who only stops by every few years would be a terrible experience for everyone involved. Though if /you/ are interested in making a fork and maintaining it, I'd be happy to assist if you make a post in https://stepmodifications.org/forum/forum/205-unofficial-skyrim-se-guides/ . It's a great way to better understand how the whole system works. Peeking at the Requiem file list, it looks like there's gonna be several conflicts, but nothing that can't be worked out over a few weeks of testing.

Would there be value in pulling the file dates & names on Nexus for the guide?

Is there a discussion anywhere about 4k textures vs 2k textures and the vram load of the default Step install? I thought I remembered some discussion during the LE guide development, but I might not have access to those areas anymore. Search isn't turning up anything. I'm running on a 6800xt 16gb, and will be running the game at 3840 x 2160 ultrahd. Pretty sure I can use 4k/2k assets or maybe even 4k across the board. Thoughts?

I'm gonna go ahead and get started downloading everything. I'd rather get the bulk of it done now and make the modifications from the change log than wait. If there's a current change list you'd like me to beta, I'm happy to do that too. Just let me know.

Soon(TM). That could be after the holidays. Any particular reason to hold out?

Back from a long absence for a new install. Glad to see both new and old usernames! ^-^ Looking forward to see the new changes.

Attempting a full install of STEP Extended, ran into an issue with Loot. Suggest two quick edits to the wiki. Adding 12.5 to the baseline column. Adding a small notice in the detailed instructions: {{notice|text={{fc|important|'''STEP 2.10.0 users'''}}<br>Due to the removal of priorities in Loot 13.0, it is recommended to use Loot 12.5 when following Step 2.10.0}} Notice with link to proper build if appropriate: {{notice|text={{fc|important|'''STEP 2.10.0 users'''}}<br>Due to the removal of priorities in Loot 13.0, it is recommended to use [https://github.com/loot/loot/releases/tag/0.12.5 Loot 12.5] when following Step 2.10.0. }} I think I built that wiki code correctly ^-^ It's be a while.

what browser?Firefox 18... I've been having some issues with this version though.Same here. Losing your post after submitting is quite interesting. I've never experienced that. Not sure how I could attempt to duplicate it to try and find the culprit. Did you use "New Reply" or "Quick Reply" when this happened? I used the Quote button to replay. Typed in my text afterwards. Then clicked Post Reply. It only happens once in a blue moon.Not sure if it's related, but I always tend to hit the save button on the editor since the Post Reply button is usually off my screen. I'll start using the button instead and see if that makes a difference.You guys know I made a thread for all this stuff so we didn't have to clutter the changelog thread with forum issues right? =P

I've noticed this and some other issues too. Basically any time I try to trim/edit a quote in wysiwyg mode, it ends up leaving empty quote boxes. I have the best results if I edit any quotes in source mode, then flip back over to wysiwyg to finish my response. It also does some weird things when trying to format text. Try this for example: Type a line of text. Highlight that text.  Click strike-through Go back to your line of text and hit enter twice. Click the strike through button again. It doesn't close the strike-through tag, it removes it from all of the text. Same thing with italics. Bold and underline though, when you hit enter it closes the tag for you. All of this is on chrome. Haven't tried other browsers yet.

Oh, when I said major release I was thinking until 2.2.x was done at least and maybe until work started on 3.0 depending on how you guys like to version.

I think I found the line that's causing the issue: In the skin css <link rel="stylesheet" href="http://wiki.step-project.com/load.php?debug=false&lang=en&modules=mediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.special%7Cskins.step.css&only=styles&skin=step&*" />The search input is set to unselectable: input[type=search] { Â Â -webkit-appearance:none; Â Â -webkit-user-select:none; Â Â -webkit-box-sizing:content-box; }Just remove or comment out the user-select line and that should fix it.

Yep. I know just the reason behind that intro period. New blood often burns out quick, and leaves quite a bit of noise in it's wake. No reason to upset the core with some new upstart that isn't going to last. They also tend to point out quite a bit of work without doing much themselves. ^-^ I have no idea how long I will stick around past getting a friendly instruction set for my Dad (and myself), so I'm going to error on the side of caution and say that I'm not likely to stick around past the polish of this major release. But I plan on being as helpful as I can while not being a nuisance while I'm here. If I turn out to take a liking to the project, you'll likely know before I will.Â