TechAngel85

Oh, as for the patch for RWT, that should be in the installer with the main file. I didn't verify for classic Skyrim, but it's there in the SSE version of the mod.

I agree. Best to start your own topic if the solution to the issue didn't solve your problems because that means it's likely an entirely different issue.

Interesting fact. I was unaware. Checked my own logs to verify. Those errors are not usually benign when dealing with programs. Usually programmers would want to eliminate them. Carry on and ignore my suggestions besides checking to make sure your antivirus isn't interfering.

A c0000005 is a access violation. Basically this means the program tried to access something it wasn't allowed to or couldn't due to a broken file or something blocking it. First, disable your antivirus program and try it again. If it works, your antivirus is blocking the access. You'll need to add the executables to your exception list. If that doesn't work, try verifying your local cache in Steam for Skyrim. Be aware this will undo any cleaning you did to the masters, so hopefully you have those saved in MO. Else, you'll have to clean them again. If that fails, I would run a SFC scan: Start Button Type: CMD Right click on CMD.exe and run as admin Type: SFC /scannowThis scans your windows files to make sure nothing is corrupted with them and attempts to fix anything it finds. If those don't work, you can try this: https://www.wiki-errors.com/wiki-errors.php?wiki=c0000005 Be sure you run your virus scanner on it before running that program as I've never used it before.

I don't remember 2, 3, and 4 ever being in STEP and there are not Anthology threads for those mods. Of course this could have been ages ago because the Anthology forum was a thing. If you're sure they were, three's likely no record of why they were dropped. The wiki only goes back as far as v2.2.1. 5 and 6 I have no experience with. CACO works great with STEP, though it does need some patching. I used it in one of my recent plays. It'll likely make it into the Guide. Since you're a frequent flyer around here, I bumped you up to an Elevated Member which allows post editing.

Yes, we're moving to Mod Picker for our framework. We'll also be updating the forums and wiki. Finally, we'll be creating a new front-end. An actual website! This is where the Guide will be provided. Actually, much of the content that's on the wiki will be moved to the new website.

I've been lightly playing SSE for a bit and though there are some mods I can say that it definitely needs, it's not been a bad experience. A rather good one, actually. There's been very little of jumping through hoops to get things to work and some of the enhancements are noticeable and nice additions.

I think I can sum this all up with this: For mod compatibility, you'll need to check for yourself in xEdit. Unless someone comes along that has the STEP setup and those mods installed, you're not likely to get good answers. This is because being comfortable patching mods is a basic skill for building a custom setup beyond STEP. We provide the STEP Patches to give you a good head start on doing this. Some mods you install beyond STEP will need to be patched. For example, if you install iNeed it will need to be patched for RWT and possibly other mods. RWT already includes a patch for iNeed, though. The STEP Guide has become somewhat more advanced since the PDF days. We provide some good guides to help you learn the tools. Here's the xEdit Guide: https://wiki.step-project.com/Guide:XEdit

Don't replace. Replace deletes the files you've installed before it and replaces them with the new ones. Merging "adds" to the existing files and overwrites any files that conflict. Whether you merge or create a separate mod is entirely up to you. That's why instructions aren't listed in all cases. I, personally, merge the files to keep my list cleaner and more organized. Other prefer to have separate listing for each option they've installed. Just what the baseline says, high aggression. If you want the other stuff, you can install it too. It's optional. The Guide is a "guide". You don't have to follow it explicitly, though we recommend users new to modding do so until they learn more.

Nothing has changed much. Protect is still alive, but there hasn't been a Guide update in a while. We're currently working on updating the servers and then we'll be doing some big dev work.

Try it in 5-10 mins. It's usually either because there is a heavy server load due to a lot of requests (so constantly refreshes doesn't help) or due it it's own caching of pages. Server upgrades will hopefully be here sometime next month. We're getting closer, but it's slow going due to real life stuff with the staff.

If you don't already own it, if can play Fallout 4 for free this weekend (through the 28th) through Steam. Additionally, you can pick it up on Steam for under $20(US) this weekend. Guess I'll finally pick it up.

Funny how the community picks all this up. haha!

Well, at this moment, I have no idea. It was suppose to have already started, but...delays. Lets say it should be this year.

Yeah, the Guide is a...well...subject with me currently. I could certain push out a few updates and new Guide with what we have now, but we're suppose to be having some new development happening.

This is my bad guys. That issue was never fixed in NEC. It was actually this mod that I was thinking of. Carry on. Carry on.

I'm aware of the limit. The wiki was never meant to be used for such things as these large guides. That's why it's on the list to try to find a way to get these guides off the wiki and onto the new front-end we'll be developing.

Just run it after all mods are installed.

Thanks. It's an old link for some reason. The correct link is here: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=KPC6YX66EGP8N The wiki is being incredibly slow this morning so I'll try to fix it all up later this evening. I got it fixed on this guide.

Thanks, I must have missed that one. Guides that used the Pack form will not require it, for the moment. The pages will be left alone, but the form and pack structure will be going away with our move to STEP 3.0 and Mod Picker as our underlining structure. Mod Picker has the perfect structure for packs already in place. We'll just have it tweaked to for packs to be hosted on our website like the Guide will be.

Thanks, but we're perfectly okay with you putting up your own donation link, if you wanted, as long as the STEP one stays up too. You and others are doing the work, after all. :: I'm hoping that there will be some way we can get these popular guides you guys/gals are making off the wiki and onto our new front-end website once it's designed and ready. That's a good ways off, though.

Going forward all guides on the wiki will need to have the STEP donation button located at the top of the guide to help us cover our hosting expenses. I have added it. Feel free to change up the layout and add your own, personal donation links as well.

BethINI is perfectly safe to use and will be replacing the INI section in the next release...no "likely" about it. :: The only thing to remember when running it is to verify your grass settings in the installer because it doesn't always pick the right settings there. As for multi-card setups, I've never ran one but if I remember correctly, there seemed to be a couple hoops to jump through to get it all working correctly. If keeping it within 60FPS is one of the issues, just turn on the frame rate limiter in Inspector and gsync off. I'd recommend 59 FPS because it can fluctuate over 60 from time to time. I also doubt that you need ENBoost with that card. I could run without it on my 4GB GTX 760. That is, if you're not playing at really high resolutions and not using 4K textures everywhere. Just running STEP at 1920x1080, I never had any issues with my 4GB card and not running ENBoost. Shadows...try BethINI.

CSS extension is an addon to the wiki and it's being removed once we upgrade. That means all the CSS that these guides use will be reset to the default wiki style. Inline CSS is used via the "style" attribute within HTML tags. Templates are not something which you can edit. They are on protected pages. One of the staff will need to create the templates which can be used to replace the CSS used on these guides, but it will not be a priority. The STEP content comes first. If anyone knows enough about wiki coding who wants to create the templates, I can see about getting them access. Otherwise, something like this is low on our list right now.

1) Bashed Patch will merge your leveled lists for you so don't need custom ones beyond what the mods provide...unless you're wanting to specifically have the game place the items as loot and on enemies, but the mod doesn't provide that option. :: 2) Keep in mind...when the wiki is updated, the CSS Extension is taking an arrow to the knee so all that pretty work to make the guide a custom style will no longer work. Only inline CSS will work. Else everything will have to be built from templates (which is the proper way of doing it anyway).