oqhansoloqo

I have never been to the areas in the game that the Gomorrah plugin would affect (I don't think). I haven't installed the crossbow mods yet due to that issue (I am waiting for SRB to figure out some kind of fix/edit for that). I haven't had much time to go back through everything to find out where the FPS killer(s) is/are, but I have noticed that installing the 2 huge landscape/misc texture mods hasn't seemed to drop performance under 60 FPS. Lol. I'll let everyone know where the issues are when I get to them.

I used the Skyrim Immersive Creatures option, so I don't know... but so far the wolves have gotten the correct textures in my setup - I haven't come across or actually tried to spawn all of the variants to see them. I guess I figured that if I notice an issue with something later on, it'll be easy enough to fix the issue without having to start a new game with this sort of mod.

If that's true, it would seem that the only thing that CQLA would be adding that BSW doesn't is stretching out the quiver meshes and thus distorting the textures (which is a negative thing) and placing them low on the back (which may or may not be liked - personally, I think BSW just flat out looks better). That would be for STEP Extended. But what about this: if the XPMS mod corrects the quiver distance from the back issue, STEP Core people aren't told to install that mod... so would they still have the quiver far away from the body with BSW (being that they wouldn't have the XPMS mod)?

Only what's in the F&L Guide. With Skyrim I got all kinds of extra mods over STEP Extended. With FNV, I only have what's in the guide (save a few mods that used to be in the guide that were removed from the guide only because they were taken down from the Nexus). EDIT: It's something in the guide - when I disable everything from the guide in MO and run the game it runs perfectly. I guess I just have to go through the tedious process of re-adding things back in until I start getting FPS killers and then take note.

For the life of me I cannot figure out why my FPS is so low these days in FNV. It typically sits around 45 and drops down to 30 often just walking around Goodsprings (and I tried to "COC Primm" just to see if it was a goodsprings worldspace issue and the FPS sucked there too). I have 1K optimized textures installed. I could have sworn a couple months ago when I played the game I had typical FPS around 55 maybe? I've got this massive headache trying to solve this and feel like pulling my hair out. It's such a drastic difference from Skyrim with better graphics, where my typical FPS is 60, and I use up to 2K textures (and ENBoost works nicely)! Damnit.

I ended up disabling it, because when I looked it up online it sounds like it was designed for coordinating vsync rates (or something like that) for multiple graphics cards in SLI rather than to be used for just 1 card.

I can't figure out what you did to run those textures through DDSOpt and have it correct the textures, because I ran them through at 2048x2048 and they didn't change at all (the ones that were originally 2K textures). I thought maybe it would fix the mipmaps or something. Was it the 2K textures that had an issue or just the 1K?

I don't think they are self-explanatory. Nor are the consequences memory-wise or stability-wise of using them. After doing a lot of hunting for information around the internet, I find out that supposedly using windowed mode tends to reduce stutter with Bethesda games (for a lot of people), increase game stability (less CTDs), and can actually increase FPS by a slight amount if none (which is opposite of what most games would do if forced into a window versus fullscreen). You also have to edit "bFull screen" in the main Skyrim or SkyrimPrefs (I forget which one) .ini file and make it "0" to actually make use of the ENB settings, otherwise setting either of those to "true" won't do anything (I think). Another setting that is not very self-explanatory that can use more information is "EnableUnsafeMemoryHacks". Why is it unsafe - unsafe in what way? Will it damage your hardware, driver installation, your saved game, cause CTDs that merely close the program? I'm guessing it can just cause CTDs in certain situations, and is not really "unsafe" to use... but the wording scares me without an explanation of the downsides to actually using it. While I don't use this for Skyrim, I noticed that in Fallout New Vegas that it's the only main memory tool setting in enblocal.ini that doesn't cause major stutter issues in that game when I try to make use of enblocal.

I was wrong about being able to Alt-Tab out of borderless window fullscreen - I actually never had that set right. I couldn't find anyone who gave a good explanation how to set up borderless window on the internet or in the STEP forums (the STEP Guide doesn't even explain this in their ENB guide currently - but that might change soon because I brought it up), but I think I figured it out - you have to set "bfull screen=" to "0" in fallout's .ini file first. I guess I previously wasn't in the windowed mode before... Once I changed the setting then I could no longer Alt-Tab out of the game without it crashing (like it's supposed to with EnableUnsafeSpeedHack). EDIT: Ugh... no actually, the Alt-Tab DOES work... just not during load screens or the intro screens prior to the main menu?

I wish the guide said more about "ForceBorderless" and "ForceBorderlessFullscreen". It's hard to find good information about this doing an internet search. The description about exactly what one each does is not very clear - feels like it expects the reader to already know what it's talking about. Seems like two settings that should be easy to specify clearly, yet no one does. When I do a search for information about this, it seems as though people talk about borderless window-mode and borderless fullscreen-mode interchangeably, as if they are the same exact thing - as an example...

That reminds me... I read things wrong previously and should have disabled ExpandSystemMemoryX64... So my setup should have had this "ExpandSystemMemoryX64=false".

I found an error with the guide info (highlighted yellow): "While the preceding warning does not apply to everyone under all circumstances (me for example, running DefaultHeapInitialAllocMB=768), credible testing here on STEP supports the notion that setting EnableUnsafeMemoryHacks=true can contribute to Skyrim CTD at startup when using sheson's memory patch. ~z929669 Talk 23:19, January 17, 2015 (EST)" That should say "ExpandSystemMemoryX64" in that specific place instead.

I have ExpandSystemMemoryX64 set to true and VideoMemorySizeMb set to 10240. Techangel, I know that you typically use baseline lower res textures which are usually about 1k, and I use 2k options. Then after all that, I decided to raise ReservedMemorySizeMb up to 768, because it improved stutter in my setup further from lower values. I think I might have tried a higher value than that and didn't really notice an improvement, so I stopped there. It seemed to be better than 512 though. EDIT: And I've spend many, many hours testing different configurations on my system.

So I decided to finally give ENBoost another try with FNV (it works nicely for Skyrim for me). I had tried to use it prior to the F&L Guide giving instructions on how to set it up, but I did not have luck. I tried it again using your instructions and I get the same results - massive stuttering after a few minutes when panning around. So I decided to try this: EnableUnsafeMemoryHacks=true As mentioned in the STEP guide: "Enabling this parameter is generally not safe. This is a workaround for users experiencing large amount of stuttering, typically on systems with large amount of VRAM (4GB+). When enabled, it does not use memory reallocation, compression, or enbhost.exe and will only work when ReduceSystemMemoryUsage is also enabled. A known bug is that Alt+tab will not work in fullscreen when this is enabled. Set to false if ExpandSystemMemoryX64 is enabled (see above)." I followed those instructions and the stuttering was gone - FPS still wasn't great, but the horrible stuttering was no longer there. Does anyone know why the description of this and the name of it says "unsafe" or "not safe"? Not safe to what - my hardware, my saved game, my game instance (IOW - might only cause seemingly random CTDs occasionally)? Also Alt+Tab worked just fine with it, and allowed me to Alt+Tab right back into the game borderless fullscreen window without crashing it... I'd like to get some more information about how it's unsafe before further testing with it, but it seemed to work for me.

What's the word on that, TechAngel?

I find improvement by disabling EnableCompression. First of all, I have 4 GB VRAM and 8 GB RAM, so I have a high amount of VRAM as well as a decent amount of RAM. I tried disabling the EnableCompression option and noticed that it drastically improved stutter issues - motion is much smoother for me. It didn't appear to alter FPS when recorded by Skyrim Performance Monitor, but the improved visual affect that I notice with my eyes is very apparent.

Good - that's what I figured, which is why I proposed that idea. :)

aiyen and techangel - I like to use the chicken near the Sleeping Giant Inn as an example. I stand back near the blacksmith's and look down the road at the chicken. If iBlurDeferredShadowMask is set above 1 I notice a very obvious halo glow around the edge of the chicken's body which makes the chicken look holy or something when it stands in the shadows. Objects should not be reflecting/emanating light like that - it just doesn't look right... That's how it looks for some of us. Maybe it doesn't do it with an ENB - I don't know because I don't use one currently. I do use RLO Weathers though, if that makes any difference. Maybe it is the darkened shadows of such a weather mod that makes the difference. Maybe if I used vanilla lighting I wouldn't notice anything, but vanilla lighting is lousy, "muddy", and totally lacking in contrast - when there's no light it should be nearly pitch black, not just dim, otherwise sneaking feels retarded and the game is visually... *blah*. Anyway, I may have tested a lot of it in the past to see the differences while choosing my game settings and mod preferences, but I don't remember...

So I finally got around to trying Skyrim Performance Monitor again with different settings - I use the carriage ride intro segment to test. With "iBlurDeferredShadowMask=1 and EnableZPrepass=true" versus "iBlurDeferredShadowMask=1 and EnableZPrepass=false" there was a no difference in average FPS. I also tried "iBlurDeferredShadowMask=3 and EnableZPrepass=true" for kicks - same story. All average FPS were 49 for me. EDIT: I know there's other ways ZPrepass can improve things besides FPS, like stutter, memory used, or stability (which could possibly not technically affect the FPS recorded), but anyways... it didn't appear to affect the FPS...

You don't understand my question aiyen - not "why did he develop it so that it has to be base settings?". What is the consequence of not using the default/base settings - does it cause a negative consequence (lag, CTD, etc) with zprepass enabled or just cause the zprepass to not do anything or maybe not work 100% as intended? When you are trying to figure out how to advise people in a guide that talks about tweaking lots and lots of different game settings, it's better to explain why you should or shouldn't do something with a simple reason rather than basically - "just don't do it". "fail or cause issues" doesn't explain much. I'm not trying to complain, I'm just trying to facilitate getting answers for me and everyone else.

What's his reason for all of the settings having to be default though: if they aren't default does it cause the zprepass to not do anything (no improvement and no hindrance), or does it cause errors or create lag or have some kind of negative consequence? It would be nice to know why.

Anyone mess around with "Vertical Sync Smooth AFR behavior"? I haven't spent a lot of time messing with it, but I just tried it out for a few minutes and it "seemed" like it smoothed out a lot of spots in the game that normally get very microstuttery. On the other hand, areas that don't normally get microstuttery seemed like they may have not been quite as smooth. Overall, I thought maybe what was occurring was it was moderating stutter and smooth motion so that motion wasn't as smooth when it normally is smoother and stutter wasn't as bad when it normally is more jarring. I guess that kind of fits the description though? Anyway, seemed like it overall produced a more smoother gameplay experience... but of course, that was just a quick observance of it without really doing any "good" analysis of the average FPS or anything.

I don't have an account in his forum, so I can't post there unless I create one. I really do not know what FixLag even does, but I did try to disable "maximum prerendered frames = 8" in Nvidia Inspector just in case that was causing the issue (since that may be a setting not a lot of people use?). It didn't help. I have an EVGA GEFORCE GTX 770 4GB GDDR5 with the newest driver. I only once had it actually get through the load screen into the game. Even before it got to the load screen, I noticed that in the main menu the mouse curser was lagging like with a low FPS. The load screen looked like it was lagging too. The one time where I got past the load screen I think I had pressed Ctrl-Alt-Del to close the program (since it was taking so long). Then I decided not close it and went back to the program, and that was when it immediately got past the loadscreen. I did a screen pan in the game and saw that it was lagging horribly turning left to right. I immediately decided that it was by far the opposite of an improvement and quit out. I have not been able to get past the load screen since with FixLag enabled.

Yikes... I just tried enabling the new FixLag ENB setting and it is NOT an improvement for me. It causes lag - very bad lag. Just KILLS the FPS. It also takes FOREVER to go through the load screen if it doesn't downright close the program after a long time. I have a Nvidia graphics card too - isn't this supposed to be an improvement for that type of card? I even have ForceBorderless (and ForceBorderlessFullscreen) enabled, so it's in windowed mode. Anyone else getting a severe downside to using this feature?

Check out the pictures of these same wolves on the mod page too - they give different angles and distances than the compares here in this forum.