Nearox

I installed this mod once and only noticed it twice during a full playthrough... Not worth it imo.

Ah thank you for the explanation! With 'vanilla' they mean 'vanilla Sheson settings' I guess :P I noticed in the source code that there are numerous _MESSAGE. Where will we be able to see these warnings/notifications? In skse.log?

Thx for your enb suggestions! If I find the time I may actually mess with it, but for now I'll stick to mods :D

Yes, i saw it too. For those who do not use a steam version, i found in the source code that you need to launch skse with the forcesteamloader parameter in order for the fix to work. [Memory]DefaultHeapInitialAllocMB= Is this the equivalent of memblock1? If it is, why would they say vanilla is 512? ScrapHeapSizeMB=

Next time you come to a new forum, you should probably reconsider how you present yourself in your 1st or 2nd post.

Yep indeed :)

I believe what you are seeing is the dynamic range around the character within which the game does high-level rendering on some things, such as shadows. If you play more you'll notice there's this rendering circle around you. Don't ask me about the technical details but I have the same thing in my game and if you check youtube videos you'll see most others have it as well. It's likely an engine limitation for which I have not found a solution up till today. I'm fairly sure there is no INI edit to remedy it. You can ask someone like ewi65 @ nexus if there is, but I highly doubt it. Afetr a while I just stopped noticing it. There's 2 things you can do to reduce the effects: - ENBs can reduce the more obvious effects of this range, and the ENB you are using already does that to some extent. - Use Memory Patch 3.0 (which you should be using regardless) and put it at higher uGrids value. Although this will not change the way lighting works within the dynamic range, it will increase the overall LOD quality of your game immensely.

VL is my favorite as well. Especially think that the parallax effect is very nicely done on the exterior walls. Makes it look like they are thick and solid, just like I would imagine such walls to be for the Skyrim setting. In addition I also like it that it gives forts a distinct look compared to cities, which all (except some aprts of riften) have more "organized" bricks in the walls whereas VL sets forts apart by a less organized, 'cheaper' and chaotic brick layering style that I think fits better to the type of enemies that usually inhabit these structures.

Agree. THere are dozens of mods out there which do the same thing... If people don't want to use LBSS then they can probably chose an alternative themselves :P

Ghehe indeed... Well Unreal cinema is simply too much of a performance hog on my system, dipping below 32 fps most of the time. That's why i don't use it :P Since I'm not talented enough to mess around with enbseries.ini stuff, I opted for a performance version of RealVision which reduces fps by approx 15 instead of 25-30 from Unreal Cinema (or most other ENBs for that matter). Phinix is also brilliant but again too heavy for my system :(

If you are using MO, then the log file will be put in the overwrite folder instead :)

Thx Neo. I don't use Unreal ENB so I skipped that part... :P

What section

That is indeed expected behaviour. Boris says though that with regards to reservedmemory, setting it too high reduces stutter but may also increase the chance for CTDs. So one should start with 64, see if it stutters. If it does, increase to 128, 256 etc. until stutter stop. This is the best procedure to find the optimal value, assuming you have correct values set in the other parameters.

Discussion thread: Skyrim Search Plugin by qbx2 Wiki Link Useful tool for modders! Helps you find stuff ingame. Nice addition to STATUS imo. It incorporates all data from your loaded esp/esm list. Video and pictures say more than words here: [video=youtube]http://www.youtube.com/watch?v=lOJR6RmES10

Nope, not at all. I was getting microstutter previous to using any ENB. Could someone please read the post above and confirm my findings under different GPU/RAM? Well, for what it's worth, I never had any stuttering in Skyrim when NOT using ENB. The cause of stuttering issues tend to be different depending on type of card and/or individual system configurations. I know at the AMD boards some people have huge problems with a particular model while others have no issues with the same model (and same game). In my experience on my HD6950, some vsync software works better than others, but this is also circumstantial. For instance, RadeonPro Vsync is superb for most games but with ME3 (or Skyrim) I cannot use radeonpro vsync because there is still tearing even though the fps is at 60. With regards to ENB vsync, if I use ENBoost but do NOT enable the ENB vsync ánd leave the game's vsync (ipresentinterval) enabled, then the result is screen tearing all over the place. Stutter on my system is completely dependent on the memory settings I choose for ENBoost.Â

If I remember correctly, when it was announced that the enbseries.ini fixes were moved to enblocal.ini it was primarily so they could be enabled without having to use the effects of enbseries.ini. Also remember some discussion between PPR author and Boris @ enbdev where Boris basically said it's not possible to single out parallax effects from other effects. EDIT: Boris said Link Believe me, I have fiddled with ENB/ENBoost for many months trying to get rid of the overhead for parallax. Think we even discussed this or something similar in a previous thread some time ago :) No doubt you have much more experience with ENB as I do. Nevertheless, regardless of using stock ENB, any other ENB, putting literally every setting to 'false' in enbseries.ini and having tried various combinations of false and true: on my system it costs between 5 and 10 FPS with the newer ENBs no matter what I do. Going from 58-60fps in most areas to approximately 50 fps. Results differ depending on hardware of course. I'm pretty sure by now that I have tried everything save from editing numerical value parameters in enbseries.ini as I have no clue what they do and doubt they are linked to it. This has led me simply opt for realvision performance version, as it comes with only a relatively slightly higher fps cost (approx 15) compared to only using parallax and I get more quality in return than using enboost + parallax + sweetfx.

By the way I got the info about ReservedMemorySzieMB from Skyrim Stability Guide. It is the most clear and logical explanation of the parameter I've seen so far:

Scratch that. SIC & CH are not the cause at all. Just had a lucky streak where I didn't crash a few times for an hour. After disablign all mods, I was still getting an occasional crash, though rare. Concluded it must be something else than mods or ini settings. All SKSE minidumps indicated memory corruption, though the underlying cause cannot be derived from them. Checked my enblocal.ini and noticed that DisableDriverMemoryManager=false. I initially left it like that because that is the default 0.246 setting and because the online config tool for ENBoost memory settings no longer states that it must be set to 'true' for AMD users. However, once I put it back to 'true' the crashes have stopped. This is using the latest AMD drivers and an HD6950 2GB. Didn't crash for 2.5 hours now, keeping my fingers crossed. Will report back how it goes, as it might be something to mention for AMD users of SRLE.Â

Note that putting UsePatchSpeedhackWithoutGraphics=false and UseEffect=false does not enable parallax effects, regardless of whether FixParallaxBugs= set to false or true. The useffect=true parameter is necessary to enable this effect, as well as a few others in enblocal.ini. Not sure why these settings got transferred over to enblocal.ini some time ago as they need enbseries.ini useffect in order to be activated, but alas. Even if you disable all feature individually in enbseries.ini and only leave the parallax effect enabled in enblocal.ini, there is still a 5-10fps performance impact depending on the ENB version used. Earlier versions like 0.221 have less performance impact than e.g. 0.246. Some effects are always enabled when UseEffect is set to true. Edit: Anyone know why the config tool no longer recommends to set DisableDriverMemoryManager=true for AMD users?

Thx for that recommendation kryptopyr. I somehow missed that patch in yesterday's nexus updates. EDIT: By the way patches for WAF and CCF were already made by xathra, published @Â https://www.nexusmods.com/skyrim/mods/48629/? Haven't used them in a full playthrough yet so can't speak about the quality, but so far (up to lvl 12) every item I encountered seems properly reprocced.

I reverted back to skse version of the patch and used MemoryBlocsLog to verify if the blocks exceeds their default values, but they doesn't . logging of blocks enabled logging max values only Block1 Max 512MB Block2 Max 256MB snip Block1 262The CTDs appears randomly when I try to move from outside to inside area of Windhelm. Block1 exceeded the default value (256)

Does RCRN use a dll injector? If it does then you need to configure it via ENBlocal.ini

Noticed that https://wiki.step-project.com/Skyrim_Script_Extender#Recommendations says that SKSE should be installed via mod organizer. This is wrong and will make beginners who don't realize it, to crash their game. I'd say it should read that users either: 1) install SKSE fully outside MO 2) install skse_loader.exe and the 2 dll files outside of MO in the Skyrim directory, and put the scripts of the data folder of the archive into a new mod within MO (aka Neo's instructions of SR). EDIT: Noticed also that the latest versions of ENBoost have an option to automatically configure memory sizes. Also they have been optimized for lower reservedmemorysizemb values. I think it is 64mb now and that at least 0.246 has as default this value so the 256mb of the screenshot is probably outdated.Â

Yep I made very sure of that. I think the issue is with the skin texture (*_sk).Â