c0c0c0

Okay, went to a save where things got wonky fast and was able to generate this fast: [spoiler=MemoryBlocksLog.log]logging of blocks enabled logging max values only Timer disabled Block1 Block2 256MB 256MB 85 8 85 8 85 9 85 10 85 11 85 12 85 13 85 14 85 15 85 16 85 17 85 18 85 19 85 20 85 21 85 22 85 23 85 24 85 25 85 26 85 27 85 28 85 29 85 30 85 31 85 32 85 33 85 34 85 35 85 36 85 37 85 38 85 39 85 40 85 41 85 42 85 43 85 44 85 45 85 46 85 47 85 48 85 49 85 50 85 51 85 52 85 53 85 54 85 55 85 56 85 57 85 58 85 59 85 60 85 61 85 62 85 63 85 64 85 65 85 66 85 67 85 68 85 69 85 70 85 71 85 72 85 73 85 74 85 75 85 76 85 77 85 78 85 79 85 80 85 81 85 82 85 83 85 84 85 85 85 86 85 87 85 88 85 89 85 90 85 91 85 92 85 93 85 94 85 95 85 96 85 97 85 98 85 99 85 100 85 101 85 102 85 103 85 104 85 105 85 106 85 107 85 108 85 109 85 110 85 111 85 112 85 113 85 114 85 115 85 116 85 117 85 118 85 119 85 120 85 121 85 122 85 123 92 123 92 124 92 125 92 126 92 127 92 128 92 129 92 130 92 131 92 132 100 132 100 133 100 134 100 135 100 136 100 137 100 138 100 139 100 140 100 141 100 142 100 143 100 144 100 145 100 146 114 146 116 146 116 147 119 147 122 147 127 147 127 148 127 149 128 149 129 149 130 149 131 149 132 149 133 149 134 149 135 149 136 149 136 150 137 150 138 150 139 150 140 150 141 150 142 150 143 150 144 150 150 150 151 150 152 150 153 150 154 150 155 150 156 150 157 150 158 150 163 150 164 150 165 150 166 150 167 150 168 150 169 150 169 151 170 151 175 151 177 151 177 152 178 152 179 152 179 153 180 153 181 153 182 153 183 153 184 153 185 153 185 154 186 154 187 154 188 154 189 154 189 155 189 156 189 157 189 158 190 158 191 158 191 159 192 159 193 159 194 159 195 159 196 159 197 159 198 159 199 159 200 159 201 159 202 159 203 159 204 159 205 159 206 159 207 159 208 159 209 159 210 159 211 159 212 159 213 159 214 159 215 159 216 159 217 159 218 159 219 159 220 159 221 159 222 159 223 159 224 159 225 159 226 159 227 159 228 159 229 159 230 159 231 159 232 159 233 159 234 159 235 159 236 159 237 159 238 159 239 159 240 159 241 159 242 159 242 160 243 160 247 160 248 160 249 160 250 160 251 160 252 160 253 160 254 160 255 160 256 160 256 161 256 162 256 163 256 164 256 165 256 166 256 167 256 168 Now, that surprises me. Here's my memory setting from skse 1.07.01: [Memory] DefaultHeapInitialAllocMB=768 ScrapHeapSizeMB=256 Looks like it's being ignored, no?

No, that's what I was talking about. Your suggestion leads to a good chunk of viewing material. Who knows? it might even point to the solution without the need for posting the log. Thanks for the info.

Phew. A good link, leading to other links. And a 42 minute video. This'll take a while. :-)

This is not strictly a "STEP" issue, but I'm counting on you guys to have some ideas on how I might approach this. I'm at around 25th level on my current game, too far to just start over, and I am crashing at what appears to be random times. Maybe every 10 minutes outside, and every 30 minutes inside. Worse in some areas. It's driving me nuts and I need some ideas on where to look to fix it. I'm playing what started out to be a basic STEP install, that has grown to 161 esps (counting the bashed patch). I'm running in LOOT order, with 12 GB of memory, and a brand new GTX 970. I'm running the latest SKSE, + uGridsToLoad, MindfluxParticles, and SafetyLoad. I believe my ini's are STEP default, but I may have made a few minor tweaks setting up my ENB (Phinix) or trying to figure out why I keep crashing. Neither the SKSE nor the Papyrus logs make any noise just prior to the crash. I ran a script cleaner on my save, but nothing came up as orphaned or otherwise odd. I should note that I am running one ESP with a single missing navmesh (Eagle's Nest). I think that's why I crash a lot along the road from Helgen to Riverwood. I've run it before with no major issues, though, so it's hard to fault this for me having a CTD while checking out my inventory in a dungeon. I can be doing anything when I crash. Mousing over my inventory, running down the road, looking around, whatever. Combat seems to be the largest cause of crashes, but by no means the only one. So, is this just what I should expect playing a 32 bit game with 161 esps, or is there something else I can look at? Is there any truth to some of these quick-fixes I've seen on the boards about extreme memory settings that make better use of my PC's resources? I'm not asking for anyone to fix this for me (I made this mess), but I'd like a few more ideas on what I can look for.

No, the instructions specifically mention using the "Load After" feature. "Changing Priority" is just a number. RE: Bash Tags: They are mentioned in the Meta Rules for the STEP patch, before the topic is brought up in the next step for the Bashed Patch. The STEP patch tags are not mentioned in the later step. In retrospect, it might make sense to move everything related to Meta Rules to right before the Bashed Patch.

No idea where you're getting this from because it's not from the mod page.It's linked from the meta rule instructions. THe path is: https://wiki.step-project.com/STEP:2.2.9 https://wiki.step-project.com/AMidianBorn_Book_of_Silence#Recommendations https://wiki.step-project.com/LOOT/Meta_Rule_Instructions

I am in awe of the user-friendly detail someone has laboriously added to all the "Detailed instructions available" sections. The obscure but essentially changes via TES5Edit, all the FOMOD decisions, all the Meta Rule Instructions. This is an incredible resource for less experienced modders, and it saddens me when I see would-be-modders attempt to do this on their own. That said, there are a few places where this instruction, in my humble opinion, could be a little clearer. Explanation of BCF files. They are all over the guide, but I had to dig to find out what they were, and why I could safely ignore them. Locking in load order positioning. The current instructions for Book of Silence say: Toward top right, tick the Show only conflicting plugins box. The list of plugins will be much shorter as only conflicting plugins are shown. Drag and drop the conflicting plugin into the Load After window. That doesn't work in this case, and only in about 50% of other cases. The listed anchor esp doesn't show up as conflicting, and the one that does show up won't drag. I had to manually enter the anchor esp in. Adding bash tags. I see there's a neat tool in LOOT for this. Nothing on the site I could find mentioned it, with all forum comments mentioning the old Wrye method. The guide itself, and the LOOT feedback, is silent on the topic, only saying that it needs to happen. Somehow. Handling of later mods. STEP core sells itself as a great starting point. Install this our way, and everything later builds nicely upon it. But there doesn't seem to be any acknowledgement of how this impacts core mod installation. For example, there are mods that have specific options for Falskaar and Wyrmstooth, which many people install but we don't mention. When these get installed, later after Core is completed, what is the modder supposed to do about those unselected options from earlier in the process? Interaction with STEP patches and interim benchmarking. Several of the mods have special instructions on how they are to be modified, with the understanding that you will eventually install the STEP patch. You can't install the STEP patch until the end because of dependencies, but if you edit the mods without the patch and run a benchmark, you might get unexpected results. Seems like there should be a step after patching where you go back and handle all the edits to the now-redundant-EPSs and such. All that said, I want to commend and thank the STEP team for all the effort they have put into this guide. It's truly a game-change (no pun intended)(okay maybe a little). I hope these suggestions can make it even better. {EDIT} "Seems like there should be a step after patching where you go back and handle all the edits to the now-redundant-EPSs and such." - Looks there actually is one. My bad. Maybe we could add more clarity during the intial installs on how this will eventually be handled.

I find that, in the early stages of a build out, I do change out ENBs often. I want to try different ones, and compare them to each other. Even after I've settled on one I like, I still still see a new one pop up every once in a while promising more dazzle with better performance. Of course, that's usually a lie so I'll grant that, at least at that point, there's no real value in a manager.

FWIW, my issues turned out to be related to a dying video card (it's been a rough week for hardware at my house). When I swapped out an older video card I had lying around, the "ENB Manager" managed ENBs worked just fine. I dunno what "crap" you may have heard was being dumped into the Skyrim root, but the one I'm using just covers over whatever you tell it to. Even it's file manifest is kept out of the root. At this point, I suspect anyone who was having problems using a manager may have just not been using it right.

Okay, i figured this out (with a little help from my friends). I ran memtestG80 and got a kajillion errors so it was pretty certain a problem with my GPU. I had a pretty decent one laying around (GTX 670) from my recently exploded PC, so I swapped it out, and now Fraps is showing me a pegged "60" FPS on the ride in. I can now burn half of that on mods! And probably more if I can get my new GPU RMA's. Thanks for all the suggestions!

NVidia *did* install their GeForce Experience thing, and it *did* say I wasn't optimized. But I was optimizing with NVidia Inspector per this page: https://wiki.step-project.com/Guide:NVIDIA_Inspector#tab=Custom_Profiles_and_Settings My settings look exactly like those shown on the guide. I'm assuming these override anything from GeForce Experience, no? EDIT: Just for giggles, I went ahead and applied the GFE "Optimal" settings. My FPS is now a fairly steady 8. I should also clarify that the scene I am playing, over an over again, is the first one. The ride in with Ralof. I play from fade-in until he first speaks to me.

No ENB involved. This is clean, vanilla Skyrim. Not even any changes to the ini files. Set to "High", but that shouldn't be a problem, I wouldn't think.

I thought I was doing something wrong with ENB, but after a fresh install, right off of Steam, things are even worse. The installer chose the "Low" setting for for me, so I bumped it up to high, thinking Ulta was probably more accurate, then I ran Fraps and started a new game. An FPS of 10. With nothing modded or added. These are my specs: OS:Windows 8.1 (x64) (build 9600)Processor:3.50 gigahertz Intel Core i5-4690K256 kilobyte primary memory cache1024 kilobyte secondary memory cache6144 kilobyte tertiary memory cache64-bit readyMulti-core (4 total)Not hyper-threadedDrives:Hitachi HDS721010CLA332 [Hard drive] (1000.20 GB) -- drive 0, s/n JP9911HZ1VW5EU, rev JP4OA3MA, SMART Status: HealthySamsung SSD 840 EVO 120GB [Hard drive] (120.03 GB) -- drive 2, s/n S1D5NSBF631082W, rev EXT0BB6Q, SMART Status: HealthyMemory:16254 Megabytes Usable Installed MemoryVideo:NVIDIA GeForce GTX 780 [Display adapter] This is a brand new PC with better equipment that what was running close to 200 mods just a couple weeks ago. Any reason why I don't see better than 10 FPS without anything changed?

I've been running a pretty solid STEP config for over a year now but, due to an exploding waterblock, I'm having to do it all again on a new PC. At least it's all newer hardware, right? Anyway, I'm stuck at the ENBoost section of the build-out because I'm getting about 10 FPS the moment I try running with any variety of ENB. I started out just setting up my old ENB (Phinix) but when that performed poorly, I went back and actually did a straight ENBoost, per the STEP instructions. That gets me past the ILS but the performance is still horrible. I've tried just about everything, including restoring the entire Skyrim folder from archive, and I keep getting the same issue. I'm about to do this again, from scratch, exactly per the instructions. Before I do this, I want to ask about the one place I am definitely not following the guide: I'm using the ENB Manager java app to manage ENBs. Seems like a safer way to go, and follows much the same thinking that went into Mod Manager. Is there any reason why this might be causing me problems getting ENBoost running smoothly? Thanks!

Still would be nice to know what it means.

Might want to add a blurb along the lines, "We've found these presets to be high quality and usually up to date, but you should feel fry to try any that interest you, following these guide lines: ...". Blah blah good community blah blah recent ENB ... I've been using PNENB.

I get it on occasion going either way. Running .207.

.207 is da bomb. I'm going to need a reason to "upgrade".

Kinda frozen by that update. I'm running .206 right now, and it's mostly okay. Is the general consensus here that .207 is definitely better than .206, and that .208 is step backwards?

Is it just texture loads, or do ENB settings figure in as well? I use only 1K textures for exterior settings, with a mix on interiors (but a preference for 2k). I'm wondering if I can do something like increasing the reserved memory, and pay for it with SSAO, or something like that. I could also disable some of my texture packs, but I want to know if there is anything I can more easily live without. Also, doors appear to be particularly problematic. Is there a trick to minimize the risk of a CTD, like waiting a few seconds to open it, or hitting Shift-F12, or any voodoo like that?

What if I go the other way? Â I've got a 2 gig card, and I'm still getting fair regular CTDs and ILSs (Infinite Loading Screens). Â I'd definitely give up some FPS to cut back on that. Â What would happen if I went with, say, 768?

I use this mod. Actually seems like there is a war on, now. And it's less intrusive than most of the alternatives.

This is a bit of a post-necro (from way back in July!), but I've seen this posted different on other forums. Â Isn't this important for Borderless Windows, which I presume we will still endorse? Â I set this to "true" based upon reports that not doing so would lead to hang-ups on Alt-Tab, but I haven't run without it so I don't really know.

There are a TON of these, and no easy way to filter them out on the Nexus. Â In fact, they are among the most endorsed, from momentum if nothing else. Â I'm sure our recommendations will, though, so maybe that's will end up being our solution, at least in part.

I would suggest that we at least mention it in the same breath, and maybe link to the discussion. Â For someone who is already using ENB for the graphical enhancement, the fact that ENBoost is included with certain pre-sets, but not others, and that you can't run ENBoost along side your old favorite pre-set if it uses <0.193 are key facts to have when trying to set this up.