Shadriss

Interesting... I'm getting capped at 1MB as a non-premium (spread over all downloads I do at once, something that the Nexus has informed people of repeatedly). The 200 - 300 kpbs being reported is very odd if it's a single download.

STEP will be updating in the relatively near future... the 3.0 guide is in the last bits of preparation, last I heard. No idea when it will actually drop, but it is on it's way. As to using 2.10 (current version), it's still mostly doable... There's a few threads hanging around that talk about some of the issues some of the other users have run into in recent months. In short, it's still a good guide if you consider that it is just that - a guide.

The consistency patches do exactly what you think - they touch the stats and (in some cases) the crafting recipe. One of the guys went through them over a few weeks and changed the stats to be closer and more inline with the materials used in their crafting. Pepper brought up using the Great Equalizer script, which used to be part of this guide, but that has been gone for a few months or so - supposedly it redid all the weapon and armor stats to make things a little less OP/UP, but according to Lexy, it never really worked all that well. The short version is that you can add whatever you want, though I'd wait until after the base installation of the guide and put them at the end. Where the other armor mods you are looking at are concerned, just be aware that they may end up being more OP or UP than you would like.

Hard to say - depends entirely on your rig. Even without an ENB, this is a pretty intensive guide. That said, with a 1070 and Rembrant ENB, I manage all outside areas around the high 40s to low 50s... so if you are only getting 31 in Solitude with no ENB at all, this guide MAY be too much for your rig without giving up some things. Something to consider... nothing more. Unlikely. I've been running the pre-releases of 2.1.6 for a while now and have no problems with SKSE showing up... it autodetects the files when they are dropped into the correct locations. I haven't done the full update yet, but I think it, as I said, unlikely to break a core portion of the program that had no reason to be altered in the first place. The last line in the window before the shut down said it was looking for BSHeartland.esm. Make sure that the mod for it is loaded and checked in the right pane and that it's loaded near the top of the list, then give it another shot. If it's still not working, then you might want to open another thread in the xEdit forums to get some help with the issue.

I run Lexy's at 1080p on a 1070... and depending on the ENB you run the results will vary. I run Rembrandt, a bit heavier than the Franken-Phoenix that the guide recommends (I think), and I typically run FPS in the high 40s to low 50s. On a 980... well, I don't think you're gonna get up that high.

1) MCM is always finicky, but I've not seen it behave quite like that. If all the options do come up eventually, then it's not something I'd worry about over much. 2) There are a couple places you can do paints - handpaints are a leftover from the LE version that (as far as I know) still hasn't been ported over completely. Facepaints can be applied in two places, IIRC - once on the face features page and again much much later. That second one is like the handpaints above, so if you are trying to do it there, that would be the issue. This was set up like this to allow multiple facepaints at once, and isn't supported in SE just yet. Again, that's my understanding of it, so I could be way off base. Not like that hasn't happened before. 3) I know the place - SW of the crossroads near a bandit fort. Happens every time I pass by. That's intended. 4) Those pouches are being added in by Bandolier, and are not adjustable at the moment. Once CCOR gets updated (Christmas present, please, Kryptopter?) there will be an MCM page that will allow for that, but for now, we're stuck. It's meant more to allow you to carry more stuff back to the museum at once, but as you've seen, in practice it allows for other uses as well. If it bothers you that much, just police yourself - that's about all that can be done. 5) Not the rate of regain, no. There is an option in Vigor (?) that controls when it kicks in (one of the MCM settings Lexy mentions in the guide), but the actual rate of regain is not controllable. 6) Yes, but a couple mods also make adjustments to them (Wildcat for sure, possible one or two more) so they kind of all need to be tweaked in concert. Overall difficulty is still controlled by that main setting though, so use that as a first tweak, then use the mods to tweak it in the rest of the way to a place you like. See you on the flip side, Lexy. You and the hubby enjoy the time off.

@ Malacia: Agree with Mr. Lexy (Darth Mathias)... that looks normal. From what I can see, you are heading from inside to outside, and I think the game assumes you are always heading into icy/snowy conditions. Not a big deal, and nothing to worry about. @Rayhne: That's very dependent on taste - I'm using Rembrandt myself, but it's very FPS hungry and can get more desaturated during storms than you may like... as in it's almost completely black and white, much like Seattle for most of the year. You can use ANY ENB you desire, you just may have to tweak a few settings in it to suit your taste.

Screenshot? If we're talking behind doors and the like when transitioning, I'm not sure that I'd worry about it too much, but a screenshot to show the issue might be useful here.

Yeah... you're getting a lot of odd errors. Starting from pure scratch might be the only option - don't be discouraged though. A great many of us have done that AT LEAST twice. Some a LOT more than that. Take it slow, take it deliberate, and ask questions if anything doesn't make sense - we'll help you get through it.

Apologies - been a busy week and a half of finals, plus all the work I'm doing at the VA helping other students get ready for Spring Semester. In short, look at Godescalus' comments, and keep in mind that where this guide is concerned, there are no definative answers. There is a reason it's marked as an advanced setup - I'm operating at the extent of my modest modding knowledge. If you have specific questions, I would, at this point, refer you to the Discord. Just avoid irritating Bumbles by using the search box to look for common issues first. :) FPS is mostly killed by the ENB. Depending on which preset you use, some have more impact than others, so it's a matter of taste and what you can stand FPS-wise. As to the other, for the most part yes. There might be a few that are still in the CR patches (Looking at you, Sofia!), but most of them aren't in the CR. Experiment and check. :) You aren't the first, you won't be the last. Lexy knows *I* have done that exact same thing a few times. :) As Lexy indicated - no issues. Carry on in a semi-intelligent manner. Simple answer - if there is no popup marking NoMerge, then there's nothing to worry about. I think it's a leftover from long ago, and left in as a Just In Case Measure. (Side note, I once served with a cook on board my submarine whose name was Justin Case. You can't make this crap up.) I can't speak for everyone else, but I put them at the end, after all the main mods but before Bashed Patch and the rest of the finishing line items. Seems to work well enough there. Of the ones you list, I use 1, 2, 3, and 10, so can tell you those won't cause problems. SOS might, depending on how much CR'ing will be involved. Can't speak to the rest... though I can tell from some of them you are a dirty man. :)

If the My Games folder doesn't exist, you likely didn't start SSE once through Steam - it creates all of that when you do. Or should anyhow. Give that one more shot - I think I remember that being advised at least once.

(Deep Breath) Armor mesh replacers would conflict with Guide instructions, so would need to have the guide solutions removed in favor of yours (or at least have yours loaded after the guide ones to cover any that yours wouldn't). Again, any CR'ing involved in this would be on you. CBBE can be used, but see previous note on CR'ing. Also, you may want to visit the Discord server - this one has come up there a few times, and so some previous discussions there may be of use to you, as well as other modders' solutions to CBBE WRT this guide. I don't do a lot of merging, but so long as any mods you merge that use scripts have Relinker (or zMerge if you use that) run on them, there shouldn't be too much in the way of issues... however, there's a lot of ifs/ands involved in that process, and I don't know enough about it to give you a definitive answer. Aaaaaaaand finally... nope. No ideas. Did you set up your account credentials in MO2 properly? (breathes again)

Quick Version Answers: A) You CAN leave out mods - however, if those mods are masters in the CR files that Lexy provides, you will have to clean those masters out using xEdit. There's a quick guide for how to do that in the Troubleshooting portion of the guide (links at the bottom of the main page, IIRC). As to if it does terrible things or not... who knows? Only way to find out... B) Straight texture replacements aren't an issue... C) Meshes MAY be an issue... and D) NPC stuffs likely WILL be an issue, and will require you to do your own CR'ing. There's a lot of NPC related CR'ing in the base guide and making those play together nicely with anything you may pile on top of that may result in Black Face or any number of other issues. Not saying it can't be done, but *I* wouldn't want to try it. Then again, I'm not a 1337 modder like Lexy and Crew. :)

The SSEEdit Cache is created by SSEEdit (go figure right?) as a set of files, on a per mod basis, that has all the information that SSEEdit collects on load for that mod. In short, it helps SSEEdit load up quicker once you select the mods you want to look at. It can be safely deleted if you wish, but otherwise, what I (and others) have done is create a mod folder for it and move the data from Overwrite into that mod. It won't affect your game doing that, but it will speed up SSEEdit load times significantly. Since xLODGEN and DYNDOLOD are both built off of SSEEdit, it's likely that the folder shows up as a result of running those programs. If it's empty, again, no worries, and it can be safely ignored.

Cleaning the original ESMs is covered in Prerequisites here. BETHIni is also in Prerequisites, covered here. Performance monitor is completely optional and I, personally, have never had a use for it. DLL Plugin loaders are generally unneeded, as we don't have any mods that require it... the possible exception is DynDOLOD, depending on which version of it you are using, though for the moment we're not using the DLL version. SKSE in prerequisites does mention to only install a few files at that time, but is never brought up again that I can find, so that's a valid change that likely needs to be made.

Which means, Resc, that you need to look in the MCM menus for those characters and see if they have a similar setting. Just in case that wasn't clear.

Which looks, essentially, to be what Osta did... which means the reinstall would likely be the next T/S Step.

OK, I'm about to head off to classes for a bit, but here's two things to try while I'm gone: A) Remove the -o argument completely. That is only used to designate an output path, and if you have it going into xLODGen's main folder (which is what it looks like to me), that's where it defaults to anyhow. B) If the above doesn't change the result, I'd look at downloading and reinstalling. Nothing obvious is jumping out at me, so that is likely to be the next step in this case. Good luck - I'll try to check in later.

The DLL isn't corrupted - it's written for a much older version of the mod. Minor difference, I know. IIRC, the DLL involved is actually from Papyrus utilities and was included for some unknown reason (instead of just telling people to download the Utilities and install). If you load Papyrus Utilities after Simply Knock, the file will use Utilities instead of the one provided by SK, and you should be fine. Then again, I'm getting old, so I may be misremembering.

Yes. Likely a good idea, yes. True statement. Anytime you see 'delinquent' masters, this means that the Master File is being loaded AFTER the one that needs it - a big no-no. LOOT is your go-to tool for getting these kind of things fixed. The errors with ICAIO are expected and can be ignored. As to the LODGen problem, the -sse tag is correct, but I think your -o arguement may not be entered correctly... pretty sure that there are supposed to be some " in there at the beginning and end of the file path. GO back to the Prerequisites page and verify you've entered it in right - once that's been confirmed and we know that it's good, we'll have a place to start from.

That's how I would do it, yes - by the book (guide), just don't turn them on.

Last I recall, you said that it MIGHT create a cyclic. Is it actually creating one, or have you tried this yet? Pretty sure that if it was, Lexy would have addressed it already.

Leave them in the Bashed Patch. That's what it's there for. If you aren't specifically directed to do something, chances are you aren't supposed to. Either solution works, but the later one might be easier for reasons of Conflict Resolution. If you remove them completely, you will have to ensure that all patches that go with them are also removed. This might (and here, I'm thinking more likely not, but...) also impact the larger CR patches that Lexys provides as well. If you want to go through all the files to deal with any possible resulting issues, then go on ahead. Otherwise, just turn them off/don't use them. Really, the only three involved are Campfire/Frostfall/iNeed. Campfire doesn't really affect anything, so nothing to shut off, Frostfall won't turn on unless you tell it to, and iNeed can be turned off with one menu selection. Far easier than running through all the files. 'Misspelled' and 'embarrassing' as well. :P Glad to hear it was something simple - I was about certain it was something to do with anything but DynDOLOD, as if that had been the problem, your issue would have been reported more. Have fun in Winterhold... in the blizzards... with the sabrecats. You'll likely have to redo some of the merges, but MOST should be fine. If the classic classes isn't there, a reinstall of OMEGA is really the only way to fix that, though. As a general rule, don't worry about visual errors in-game until after the full guide is completed. If you get to the end and it's still horked, THEN worry. That said, Lexy pretty much covered the answer in this case, so I'll leave it at that. Well, if it's updating, I wouldn't worry too much - wait a day or two (or an hour or two) and check back. There's no ESP file involved in this one, so it's safe to add in later, and if Lexy updates the INI file in response, again this can be done mid-game. Regardless, no worries.

Frostfall will do it, but really, ANY change of equipment or spells will do it. I usually trigger it by equipping Spark after all the SKSE message spam and loading messages fade out (usually a minute or so of staring at a wall). If it's not popping up, there is most definately something wrong, and you should look to ensure that it's: A) Turned On (I know, you said it was checked - I'm going through the list here) -OR- B) Not missing files (IE, a re-download may be needed) The modified metadata you list is needed, or the grass clogs the roads in Dragon's Bridge. You can always alter Dragon's Bridge data to ensure it loads first, if it is causing cyclic. If it isn't, then no worries.

Well... let's just say you don't wanna hit Bleak Falls barrow before level 10-ish without either a flotilla of followers (one user reported clearing it at level 6 with three followers... barely) or a trigger happy save button finger. Most I've seen talking seem to recommend doing a lot of 'other' stuff for a while first to build up your level and gear... usually things like local missives quests and roaming bandits in the Greater Whiterun Area. It's not vanilla easy, that is for certain, but a lot of it is going to depend on how you decide to play it. It will be harder, but it's certainly playable... and more importantly, enjoyable.