TechAngel85

Install this: https://www.microsoft.com/en-us/download/details.aspx?id=8109 ENB will not support Windows 10. Boris doesn't support any OS past Windows 7.

I've edited the headers on my sandbox to be more in line with how they are typically used within pages and the formatting to match. I'll break down my reasoning and thoughts: H1 headers have not been used and left for the page name.All headers have been given a tiered top-margin with the H2 header having the largest margin and H5 headers having the smallest, but is still a least double the width that is found between normal paragraphs in order to better separate the content.Likewise, the font sizes are tiered and a small letter-spacing has been added to better differentiate the headers from the content text.The H2 and H3 headers have been given a bottom border to further section off different content with the H3 border being thinner. This makes more sense when you see it used as it is in the ModuleConfig.xml File section of the sandbox page. The H3 header's width has been limited to only 65% of the page width in order to limit the width of the border. This gives it a tiered appearance so readers know the new section is still part of the larger section defined by the H2 header above it. The width should not interfere with the header length because no header should expand that length anyway, and if one does, then a better header title needs to be thought up.Sandbox: https://wiki.step-project.com/User:TechAngel85/Sandbox2 CSS: https://wiki.step-project.com/User:TechAngel85/temp.css Overall I think the headers are better differentiated and make more sense. The spacing around them is also more optimal for reading. This theme should work for all wiki pages besides more custom pages like the STEP Guide...which has it's own CSS anyway.

I've used both Drupal and WordPress before. They are both good content management systems with Drupal being more on a technical side and WordPress more on a "anybody can use this" side. My last website was 100% WordPress because I didn't have a lot of time for managing it. I've never dug into creating queries from any sort of database though. It would be interesting to set this up on a VM to play with....I need a vacation to have to time to do everything I want to do...

Ess, can you upload the newest patches to the copy share? the ones that are up are still asking for The Choice Is Yours_Legendary.esp.

You're going to have to go ask Boris, if you want details in how the compression works. Technical details isn't the aim of the ENB Guides.

All the info in the Guide either came from Boris and his forums and changelog or from keithinhanoi.

Okay, cool. I don't remember if I had Real Snowflakes running or not. I will in my new setup, though.

The distant fog effect that covers the distant terrain didn't always work. I was using the Extended weathers with windy clouds plugin for vanilla. I don't have my old setup anymore to provide specific details, sorry!

Thanks. When I noticed that it wasn't always working I had never attempted to patch it. It wasn't working all of the time, out of the box. For this round, I'm going to use a custom patch for my testing to ensure I'm resolving any conflicts.

I don't pretend to know how everything works under the hood, but Boris's defaults are usually the recommended baseline settings. I think the description is clear and it's not causing any real strain on any system that meets the STEP minimum requirements. All the memory settings will be more system specific than the other settings. If having it enabled isn't working well on your system, disable it. The default setting works for the majority of users though.

Because, if I'm not mistaken, only STEP Staff level and above have those editing permissions.

Yep, you have to update the FOMOD for the plugin change for the new legendary version. That mod page should be updated as well to reflect.

Thanks, that is what I thought. The STEP Patches has CRF winning all conflicts. I'll have to look more deeply into this.

The most current is the STEP Compilation folder with the loose folder structure and zip archives. This is the one I set up because the patches and compilations were still separated for some reason, so I put it all together when I finished the FOMOD. You shouldn't have to change anything in the FOMOD itself since it's installing folders rather than files. I'll look into the RS/CRF stuff. JawZ said the RS should win as long as CRF isn't moving objects. I'll have to look at it in the CK.

JawZ, I'm curious about the conflicts between RS and Cutting Room Floor in regards to light placements. Both mods edit the placements and only slightly in some cases. Which should win the conflict?

You'll need to post over on the SRLE forums for a better solution. STEP doesn't do SRLE support. https://forum.step-project.com/forum/56-skyrim-revisited-skyrim/

Just when you thought you where done. The Choice is Yours updated with a Legendary version.

You shouldn't clean that ITM. It says not to on the mod page. Also, you shouldn't be sorting masters on an entire load order. Zilav (author of xEdit) has stated that it's dangerous.

They're not in there so if I do any patching tonight before you upload, I apologize if I post any redundant data.

Gotcha, my patch ended up fairly big. I'm going to redo it to note the forwards to see if they should have been in the Patches. I'm going to switch to the ELE version though because a lot of those forwards seemed to be lighting data. I noticed Cutting Room Floor is editing some light placements. I'm feeling RS should win the conflicts, but I'll ask JawZ before doing that.

V2? We've already updated the patches once, so wouldn't this be v3? Thanks, but don't need them. I'm using the Extended patches and forwarding any changes needed from the added mods to a custom patch. This helps me to get involved in the plugins a little more so a second pair of eyes is at least on them some of the time. I also do all my testing on an Extended profile, so should everyone else. If it doesn't work in Extended, then it's not going to work for Core. I wonder if our MTs even know how to do some basic patching for the mods they're testing? Speaking of, I didn't think about it until now, but I also found a few forwards between mods that needed to be made. These probably should be taken care of with the Patches...just don't remember what I forwarded. I'll note any future forwards to keep a record.

JawZ, Looks like there are some edits from USLEEP that should be forwarded into the Legendary version of the plugin. Looks like mainly regional data but there might be more.

Whatever is easiest. If you change the directory structure, don't forget to update the FOMOD. There's a ReadMe file I've put on the Copy Share to note any changes.

Ess, I think the patches need to be loaded after Non-essential Children's plugin. We're not directing our uses to give the patches a priority now and I've been looking around in xEdit. It seems LOOT puts the patch above Non-essential Children and it's causing some overwrites that don't look desired. Note that I'm using the Extended Non-ELE patch and I am filtering for conflict losers in xEdit. EDIT: Looks like there are a few others: NARCWhatever Paralyze.esp if front.

Dropping this one from testing. Wiseman303's Flora Fixes is better and more complete by fixing a couple other issues. Unmarked for Testing.