Farlo

*double facepalm* (for myself and the OP), and here I thought he just didn't use periods in version numbers. Â Locking this thread.

Actually it does have a basis.  Steam automatically updates the game (even if you tell it not to, known bug) so unless you saved a copy from about a year ago there's no way to obtain v1.1 legally.  If that's the case I have to ask... why? Either way I highly recommend you update to v1.8, a lot of the ESP and gameplay mods aren't going to work very reliably (if at all) with v1.1 and like I said, I'm a little surprised the DLCs do.  I also suggest you find a proper mod manager (Mod Organizer or Wrye Bash) and ditch NMM. I explained in a bit more detail as to why here.

Split this off into it's own thread and added a link to the guide (hope I didn't EC you), might as well keep them separate. Just a note for when you're uploading files: could you please add [[Category:Lighting Guide Images]]to the description so the images are kept track of. Â I've already done it to the files you've uploaded so far so no worries on those. Â Thanks and keep up the good work.

I had to Google that. I lol'd. I say that all the time at work.That's pretty good, I'll have to remember that one. Might be because your probably using a pirated copy of the game, re: skyrim update v11.Yeah... sounds pretty sketchy to me. Â Also, neither we nor most of the mods on Nexus support v1.1 of the game (v1.8 is the latest). Â Either find a better rip or just shell out the $40 for the game. Â Unfortunately you missed a ton of sales where it was even less than that.

This question can be answered either way, and it really depends on how comfortable you are with modding.  First off, I'd highly recommend you ditch NMM and use a proper manager such as Mod Organizer or Wrye Bash.  They have a bit of a learning curve (the latter moreso) but they're way more powerful and are required to update mods without the possibility of breaking them.  For instance, if you install Mod A which uses some various texture files, then you install Mod B that uses those same textures NMM will simply overwrite Mod A and not bother to keep a backup.  Then if you update Mod A to a new version, it'll simply overwrite Mod B's files again.  This means you'll not only have a lot of issues keeping them updated and working correctly, but if you ever decide to remove Mod A it won't replace it with Mod B, so both will be broken.  With MO and WB each mod is managed independently and even though you'll have to manually check for updates you'll never have to worry about overwrites. On the the actual question.  As I mentioned above, if you're comfortable modding there shouldn't be a huge issue with updating as long as you follow any instructions the mod may require.  Obviously if the mod introduces new features (especially on the scripting/ESP side) then you may run into problems.  Assuming you're using a proper mod manager then it should be really easy to install the update as a new mod "on top of" the old version to do a little testing and then replace the old one when you're sure it'll work.  If you're not comfortable with the modding procedure (or continue to use NMM) then it might be best to just leave it all alone.  Unless the version you grabbed has a bug that we didn't know about when we wrote the guide then you won't be missing anything.  All that said, if you do decide to update a mod and something abnormal happens, please come back and make a post in the mod's thread (use Search!).

Just a thought about how you specify FPS boosts/decreases, and you guys may have a better counter-argument. Because everyone's rig is different and will react differently to these settings I think it'd be better to stay away from specific numbers and instead use more vague terms (yes, saying that hurts me very much).

Stop using red! Apparently I need to dig around and see if we can just disable that color, it looks so ugly. Use Maroon, Brown, or Saddle Brown instead.

Deathwing, I updated your post to utilize the Highslide gallery.

Weird, according to the Admin CP you should be able to do those thing... hard refresh perhaps? Or maybe it just takes a few minutes to update? That's quite a rig you got there, I look forward to seeing screenshots when you're all done :P

That was my response... the Vanilla UI is horrendous, but to each his own I suppose.

Oh, when I said that I did the "save game cleaning procedure" that's the one I meant, I should've been more specific :p Whoops, my bad, reading intermittently at work >.< Unfortunately I don't have any more advice, so unless someone else can chime in here I'd suggest you post on the mod's Nexus thread. No worries. Do you mean the STEP 'mod' on Nexus? I hadn't even thought of that, to be honest! No, you'll likely encounter the same people there as you would here :P I meant iHUD's thread on the Nexus.

You essentially only need WB, I just like MO because of the folder virtualization.  It creates a private "data" folder for each mod so nothing actually gets overwritten, it's all done virtually by MO when you launch Skyrim.  I actually don't use the updating/downloading capabilities of MO either, although from the few times I've tested it it works fine.  In the end though, WB is all you need and if you can learn to use that there's no reason to use anything else (unless you don't like visiting the Nexus to find mod updates).  I tried Eve a few times, but after a couple months it started getting really boring as skills took forever to train.  So instead I'm playing Dust514 at the moment, it's really fun and unique but still feels very Eve-esque.  It has a lot of potential and I hope it's a successful project when it actually launches.

Oh, when I said that I did the "save game cleaning procedure" that's the one I meant, I should've been more specific :p Whoops, my bad, reading intermittently at work >.< Unfortunately I don't have any more advice, so unless someone else can chime in here I'd suggest you post on the mod's Nexus thread.

I definitely recommend getting STEP set up entirely before you begin. Adding (and even worse: removing) mods to current saves can introduce a lot of errors. The PDF should say this, but before you begin make sure to go through the Skyrim Installation Guide so you have a backup and all that. Also, I encourage you to learn how to use either Wrye Bash (more complex, more powerful) or Mod Organizer (simpler, less powerful) to handle your mods and stay away from NMM; it will make the whole maintenance/update process a lot easier.  I also recommend you start the game and run through the introduction sequence (at least up to character creation) after every dozen or so mods, just to make sure everything's still running by the time your finished.  I'm really excited to hear that STEP is being passed around by word-of-mouth even in the real world and I wish the best of luck in your modding endeavors!  Congratulations on the retirement and if you really like the game we'd love to have you stick around and contribute whenever you can.

I hope it's not outdated any, but you can try the savegame cleaning instructions on our Wiki here.

Disabling them in the launcher should be enough as it should prevent that mod's resources from being loaded.

That's one helluva snow storm! Unfortunately I have no idea how that may be happening. Best way to determine if it's an ESP problem is to go through and disable a few at a time until something changes and try to boil the problem down to one mod.

While it's easy to provide a STEP guide for the Baseline and high-end systems, supporting low-end systems is another endeavor entirely.  STEP was originally started to provide the best visual enhancements the community has to offer and as such we've always encouraged users to make the decision to install particular mods on their own.  Keep in mind that STEP is a guide first and only offers our personal preferences (although we try to be as objective as we can).  Starting with v2.3 we'll have a lot more empirical test results to evaluate mods with, but in the end the guide will contain everything we suggest for the best experience.  Because modding can be very machine-specific and individual we merely list our suggestions and leave it up to the user to pick the mods they want to (and can) use.  The Impact column can be a little more helpful (and it hopefully will be in the next version) as far as distinguishing mods that are resource-intensive, but at the end of the day, each user has their own limit as to how much they can add to the game and there's no way we can account for all possible configurations and situations, especially not if we're going to aim for specific framerates (as those can change drastically just based on what you're running in the background).  To that end, I doubt we'll ever release separated guides, but we will always try to provide as much relevant information about a mod as we can so that users can make the best decisions for their system. Obviously we want to offer optimizations that will benefit everyone, and as far as INI tweaks we can probably suggest different values based on performance, so we'll look at that.  Most mods in STEP that affect FPS are textures, and the reason they do so is because of their resolution and filesize.  This process will be explained a lot better in v2.3, but basically you can simply run DDSopt with a resolution constraint to bring all the STEP mods down to Vanilla resolution, and that will reduce a lot of the impact these mods have on the game (although every texture may not scale down so well and this is something that deserves a forum thread of its own).  The ENB page does need some attention and it'll likely be revamped for v2.3 as we'll be introducing a "Post-Processing Pack" that will offer an array of options for all system and personality types. I wish I could say "I'll look into those right away", but to be honest we're a lot more focused on building a framework for analyzing and testing mods going forward so unfortunately quite a bit is being left for when that's all done and we're back in mod-testing and guide-writing mode.  As I said above, we encourage users to make decisions for themselves and look at modding as a learning experience.  Obviously this ideology doesn't work for everyone as some people just want a "plug-and-play" experience with modding.  Unfortunately that's not how Skyrim mods work and attempting to reduce it to that will always fail.  Of course we're looking at ways to make the experience less tedious and one of our admins is working on a program that can fetch mods from the Nexus for you (similar to NMM), that's a long ways off and will still involve the user selecting with mods will be used.  New users definitely don't fall into this category, and the process can seem complex when you're first introduced to it.  To that end, we're looking for ways to make the installation process as easy as extracting the files to a folder and then using a mod manager such as Wrye Bash or Mod Organizer to handle overwrites.  That way new users don't have to deal with installation order and all that while we can leave the door open for more experienced users to experiment on their own. As I said above, the Impact column needs some work; that was introduced with good intentions, but there was never enough data to do anything really helpful with it.  As far as the rest: my apologies, it's pretty hard to keep several hundred mod descriptions up-to-date, and some authors may have changed their offerings between guide revisions.  At least before every big STEP release I go through the installation process and make sure everything's there, so most of them should be addressed sooner or later, but if not it's generally one of those "its up to the user to decide which they want" type of deals.  I'll look at these to see if we need to fix anything for v2.2.0b (our next bug-fixing release), and in the mean time if you find any begs or errors in the guide, please post here. The whole testing section is going to be re-written, that page is quite outdated, and we'll definitely be including a program that monitors FPS, VRAM usage, CPU usage, etc.  As I said above, the ENB page was put together quickly and hasn't been updated in a while.  I'll ask the ENB author who volunteered to write it if they can update it a bit, but besides that it's going to have to wait for v2.3 :(.  Same goes for the SMAA link, I'm not too keen on all the ENB stuff so I don't know where to find an alternative. For mod suggestions (and reviews!) remember to use the search tool to find the thread or post about it in the Mod Suggestions forum.  Get Snowy's thead can be found here, and it looks like there haven't been any posts recently.

Sounds like a problem with SKSE, so you'll want to make sure both Skyrim and SKSE are updated. To check Skyrim's version, right-click on TESV.exe and go to Properties, then Details, it should say there. Assuming you have v1.8 installed, also make sure you have the latest, v1.8 compatible SKSE (available here) installed entirely and correctly.

i.e., set CCC to force vsync (and optionally triple buffering) if you are not already using CrossfireX (which should force this regardless).I think that's the opposite of what Besidilo said.Ahh, you are correct ... In that case, I have to disagree that there is any problem with forcing vsync through the drivers. I agree with Mothergoose on this one, as I have ATI and can verify that tearing is fixed by doing this. Is there a "standard vsync" provided by the game engine? If so, I am not aware of it ... I can't remember the name, but there's a value for Vsync in one of the INIs.

i.e., set CCC to force vsync (and optionally triple buffering) if you are not already using CrossfireX (which should force this regardless).I think that's the opposite of what Besidilo said.

This is a good starting point. Make sure they're getting enough power too. BTW, PCI-E 2.0 x8 makes almost no difference performance-wise compared to PCI-E 3.0 x16, so if you get to that point anyhow, no f***s should be given. Really? I figured the much higher bandwidth from the x16 would be necessary, although I guess most SLI/Crossfire setups run on dual x8's. If this is true, what's the big to-do about PCI-e 3.0?

I would suggest a good run through of STEP. There were a few places that I see that could use an update. For example, after my first install I discovered in my BOSS log a few things that needed correcting. One was a different version of a mod and the other was a mod conflict; however, thinking back that was a mod outside of STEP that I added. The instructions could use updating and more detail in some areas and with what do to with some mods too. I found myself confused at several different points and had to go in to do some research on proper install and which options to install as well.Yeah, the ENB guide was rather hastily put together as a quick fix. Â If anyone's knowledgable on the subject go ahead and toss me a PM with your corrections or whatever and I'll see about changing the Wiki. Â If the instructions aren't clear somewhere please explain, we're always looking to make this already bothersome process as easy as it can be. Â Point us to any place(s) you were confused and we'll try to fix it in v2.2.0b. Â As Pioneer and thalastwon said, there are a couple hiccups with the current release, although we haven't spotted anything major. Â Unless we find more errors I'm tempted to say v2.2.0b will be out within a week, but don't quote me.

I had this problem a few weeks ago, fixed it by reseating the card.