Aiyen

So you have crashes on save ? Or do you have a crash after 3 hours of playing , and then when you try to save ? I am not entirely sure what you mean. If you can play for prolonged periods of time (1h +) with just one crash your game is about as stable as it gets...

That setting control how detailed a texture is loaded in. By reducing it you can reduce the memory use, but you will get more blurry textures. It should always be on very high unless you run on a very old computer. It has nothing to do with the game,but more how the computer in general handles texture display.

Sounds like you have hardware AA enabled. At least in general it sounds like a driver issue.

When in doubt set it to your VRAM amount... if the game is stable.. play, if it is not then try to adjust it a bit up and down.

Which perspective altering mods do you use ?

It is mainly AMD cards that have some driver issues which that setting is supposed to help fix. But for certain Nvidia drivers it might also be useful. If you get increased stuttering, CTD´s etc. then just disable it again!

Windowed mode as opposite to full screen mode. And yes some people experience issues with it, some do not. You enable and disable the mode in the skyrimprefs.ini, also the borderless window mod needs to be disabled etc. Never EVER run the game through stream except the first time around. After that you always start the game via your mod manager! It cannot be said enough times!

You only ever need to enter the steam launcher one time! After that default ini´s are created. Those are then copied over to MO´s profiles and you can alter them there to your hearts content, while knowing that the default ones are safe and sound in their usual documents spot. SMAA is done by external injection, not by any .ini file. So not entirely sure what you mean.

Splitters and other exotic setups! Just another day at the troubleshooting forum! :)

Best advice is to play around with the ENBoost values and optimize them to your system! There are no "golden values" that work for all. If it persist in being a problem then try to disable features like AO etc. and see if that helps. It is not longer easy to troubleshoot these issues with the new memory additions, since every user more or less need to optimize for their own setup!

Hehehe brilliant! :) Good thing that I went away from SweetFX again the other day! As for other software.... like it was said, if you need to run that, then you do not need to be running ENB! Simple enough. Also all those weird memory optimizers.... they are pointless! Most of what SweetFX offers can be coded into ENB... the only reason it has not already is that there have been no motivation to do it. For now there is no point in upgrading, but in the future perhaps!

It is a known fact that skyrims physics engine goes totally nuts when the FPS increases way past 60. This is mainly because the game is optimized to be run at 30 FPS which is what the consoles do. The game should be vsync limited at 60 FPS if it is just with standard settings. Your gfx card should most likely not be able to push the game much beyond 60 at any rate. You should never start the game through the skyrim menu expect the very first time to create the very first ini files. After that you should always start through your mod manager. Otherwise weird things can also happen. Sounds like you got some conflicting settings all around... try to delete inspector settings, and just force through global and see if that fixes it. If it still acts up try to roll back to a 314 version instead of a 320.

ENB is a modification that alters how the game handles memory, and what you see on the screen, and it also adds special effects to the game that it otherwise would not have. The main reason to use it for many is that it fixes shadow rendering! Also the flickering you see. Z-fighting... lean to live with it! The only solution currently will produce Infinite loading screens (ILS) with even a moderate amount of mods installed. You turn off AA because ENB does not work with driver based AA. This is mainly because the extra effects it add conflicts with the AA code. You do not have to set skyrim to windowed mode. In fact I advice against it unless you absolutely must be able to alt tab out of the game and back in again without any big issues. However it is also suspected that running the game in windows mode with ENB causes some conflicts that will result in game crashes or ILS.

Man those Z fighting ones are hard to kill.... do not ever use them if you get ILS! They are the first that should go down the drain.

Good that you figured it out on your own! Never alter the default lib´s ... it just causes trouble!

RCRN uses its own external .dll´s which ENB does not support. It might work, but it wont be optimal. Even less in the newer versions. ENBoost is implemented in all ENB versions from 200+ The only reason it has its own release is because it has a feature that disables all the graphics enhancements of ENB so only the memory functions are used. However it still requires the .dll, and hence have all the same issues you might have with ENB and other programs that try to access the game in the same way (certain monitor programs and OC ulitities). Try to mess around with the VideoMemorySizeMb value making it lower or higher piecewise and see if the problem persist. If you use AMD cards then DisableDriverMemoryManager should be set to true as it might also help. Finally then setting DisablePreloadToVRAM to false will help a great deal with ILS during load, since then the game does not have to wait for all textures to be loaded in before entering the game. It will cause increased stuttering though.Â

7200RPM... the wonderful thing about having huge amounts of RAM is that the application can then copy in everything into RAM and you do not have to wait for that slow HDD! My initital load times are rather abysmal (2 mins sometimes!) as a result though, but once I get playing... almost instant! Also messing with the new ENB memory values. If I put in 2048 then the game starts, and everything but there is a bit of input lag at the 20-30FPS range. If I alter it to 8192 then most of that is gone but the FPS is the same. From what I have been reading then the values are entirely setup dependent... but the gist of it should be that you should never set the value to your max amount of RAM unless you ONLY have skyrim running. Since I had no ILS etc. before then it is kinda hard for me to test though... for now I am just gonna let it remain at this value until I get an issue!

Okay... just for funsies.. and because I am tried at messing with textures I tried out the good ol ILS/CTD city test. Entered the game with coc in dragons reach. From there went around just about all buildings in whiterun. No issues.. transitions got faster to the point of instant after a few buildings. Finally did a test of running out of the city and in again. process use up around 5Gb. After whiterun I coc to solitude.... ran in and out of several buildings, and in and out of the city.. no issues. Proceded to windhelm... the same, and no issues there either. I did notice that the amount of memory used increase quite a bit after just a few buildings visited. For my then it topped of at Skyrim and ENBhost process using up around 5Gb of RAM... properly all of the VRAM. My current texture load is full 2k on all major packs, and most accesories. Currently in the process of making grass and plants 2k as well. But all in all, no ILS on my setup. At least nothing that can be easily reproduced. So I cannot see it being an issue with the patch... since it obviously works here, unless I missed something. If ya can come up with a test run I should do then by all means let me know!

Most of those are fixed by ENB. But there are game engine limitations. At least I run with fov 85 with out noticing that issue.

Remember to shut off papyrus unless you are actively testing for something.... the strain of having it on can produce CTD´s and ILS in its own way... since the engine now have to perform yet another task.

Shadow flickering is a part of the vanilla game. ENB can fix that issue if that is what you are referring too. Really need a screenshot of the flicker to say what it is... AA and driver settings can also produce said effect. It should not be there in the default ini´s. Well other then the shadow flickering.

It is not just the F2P model... it can be very good if implemented correctly. Sadly that requires good gameplay for people to cash in. The general issue is the MMO model in general. If wow was released today (with updated graphics bla bla bla) then it would also fail horribly since its gameplay is so shallow. MMO´s biggest weakness is that the developers always try to make sure that everybody have access to the same content, which then quickly turns the game into a grind with the same repetitive quest types over and over. One of the reason WoW was great before the first expansion (And still good in it.) was that there was content that required effort to see! This made that content special, and it was a TRUE achievement to actually see it! While I can understand the reasons for trying to make ALL content easily available... I just do not agree with it... since it hollows out the game. Special content that you cannot just buy your way too should be a part of all MMO´s to make them stand out... sadly the developers can no longer do this because the marketing departments have forgotten that it was that sort of thing that made WoW big to begin with!

If the fast travel does not work then try to use the console to jump there instead. A bit immersion breaking but sometimes it helps. As for the log then it looks like you have removed a few mods that it is trying to find still... which is properly causing issues.

the 209 version is the 207 .. just with the added feature that you can input your VRAM instead of it being autodetected. There are some issues for people with Titan´s where the game cannot detect more then 4Gb. Boris made it because he got tired of trying to explain people that dx9 is not 64bit.. and it does not have commands that allow further memory use. There was also a few cases of 4Gb cards only registering 2Gb... So if you have that issue then you can upgrade to it.. or just stick with 207 since they are the same.

Easy now! It came out a bit harsh, but the intent is good enough! The point remains, for SSD users (I am semi staff... and I do not have a SSD btw :P) then saving space is always good! For people with large external drive capacity then it is ofc. no worry!