TechAngel85

That imo, would still require a quick retest instead of just saying, "they're good now". Would need compares.

I agree. I figured we'd be further along than what we are but progress is slow going right now, I guess.

There's a Troubleshooting section here: https://wiki.step-project.com/Guide:ENB#tab=Troubleshooting . However, we could make one specifically for the enbseries.ini file on this Guide if need be.

You enblocal.ini is set up wrong if you're just running ENBoost. Either way you have the wrong values in the memory section.

I'm planning on converting most of the content I've maintained over to TOC and away from Headertabs. I've just focusing in on other things atm.

Not even close.

I've deleted the instructions. Turns out I think I had Original Post Processing active and the steps you provided here are the standard procedure...so no need for instructions. As for the Elys mod, I've tested it on STEP:Extended on several parameters and haven't had any issues. Typing works as expected.

This is probably the best practice. I don't think I ever do really large edits unless I'm either creating a page for the first time or if there is no header to edit under for what I'm needing to edit. In the second case (usually only when using header tabs), then I would be forced to do a page edit.

So I'm confused. Using the default files, I tried various senerios to get Procedural Correction to work. The instructions I posted was the only way I could get it to successfully show anything other than a black screen and work. If there is another and proper way to do this with the default files, please do lay out those instructions so that I can update them. But as far as I can tell, that's the only way with the default files. I will change the wording to ensure users know those instructions are from the default files and not custom enbeffect.fx files. I haven't been working with ENBs for very long but I've not experienced that issue with that mod yet. Whenever you guys can tell me the structure you want/need to do this on the wiki, I'll create it.

I've experienced what hishutup is explaining as well. Site seems to simply crawl at a snail's pace for up to a minute or two and then returns to normal. Rest of the web works as normal. It's just STEP that does it once in a while. Both those values are set to true for me.

I have actually gotten a few 504's within the last week. Sometimes the wiki seems to...crawl.

Only happens every once in a while I'm doing some quick edits and uploading compares to the wiki. Using Firefox (v33) and minimal plugins. Nothing new that would result in this new behavior. Security software is Microsoft Security Essentials. I mainly just ignore it.

So, I've been working on the wiki a lot lately and for the most post I haven't thought much of it; however, it seems to be happening more often. While editing, every once in a while the editor will not load properly as seen in the image below. You can still edit and save your work without issue; however, I just thought I'd mention it in case it's something that actually should be looked into.

Nevermind on that code for the original post processing. I figured it out myself from Aiyen's post....I think. Screenshot looks about right anyway.

Okay, so are the instructions on that page accurate for getting procedural working? Like I said, it was the only way I was able to get a picture to show up on the screen.

Yeah, will need some clarification on the palette before I can successfully get the correct point across. See...we're all learning something new!

What you're doing goes way beyond the scope of STEP so I'll probably be of little help to you.

Bundled with SKSE. SKSE version works perfectly. No reason to use anything else.

Add back in the code so that I can turn the original post processing on for the compare shot of it does. Just a quick Shift+F12 won't cut it for that parameter because that is actually the Global parameter for UseEffect. So I need someone to add the code back in for a quick compare. Nothing official, just for this one little thing and then I'll set it to the side and probably never use it again. As for the palette, that lil bit could be better wrote so I'll look into it this evening when I'm able.

The Color Correction section should be completely finished now. I need some keen eyes to go over it because I had to add in some instructions to getting UseProceduralCorrection to work (this is the only way I could get it to work). All notes that were added to this page (by Aiyen and JawZ...the rest of you are slacking...haha ) have been incorporated as well. I still need someone to download the experimental version of Vividian Vanilla and add back in the code so that I can get compares of the first effect.

That is just a logger to show you how much memory is being put into the memory block...nothing more. It does not "get Skyrim to call for more blocks of memory". It just writes the usage out to a log file. Unless you're needing to know this information for troubleshooting reasons, there is no point in having it. EDIT: To be clear, SKSE has everything you need for the memory patch. Just remove that line from the INI and you're good to go.

What memory patch are you trying to install because SKSE has it's own now...or is that what you meant? EDIT: You need to remove whatever this is from your SKSE.ini file... [NotPlacebo]GiveFirstBornToSheson=1...and then make sure you're using v1.7.1.

Follow this rather than the mod page and see if that helps: https://wiki.step-project.com/Guide:ENB#tab=ENBoost

It was mostly like the out of date drivers the entire time. Anytime you get new hardware you should always grab the latest drivers for it. Glad it's fixed!

Are you all keeping up with what you've already contributed to on the wiki? I thought I might just incorporate what is already there as I go and as I'm adding in compares for the parameters. Of course there hasn't been anything added past Adaptation yet.