Vond

Dynavision and Imaginator is compatible. Dynavision only so if you disable ENB's DoF obviously.

Diablo series is the only Blizzard series I can't understand what people like about. I mean I love the setting, but the mass-mouseclick-fest that was Diablo 1 and 2 just never did it for me. Now Warcraft (strategy games that is, not so much WoW) and especially the best games ever made, StarCraft 1 & 2, THAT I can understand. :) Enjoy the "time off" I guess~ ;)

Sounds interesting! Thanks for the update

Yep, and it's enabled by default

I have a i5-760 @2.8Ghz And glad I'm not the only one that would freak out in that situation! :)

Yep, guess I should've mentioned that. :) I forced Skyrim to use core 1 and 3 for whatever reason

Tried the Extended Launcher today, as I'm using Turbo rather than real OCing of my CPU, so figured I'd give it a go. Running Core Temps on the other monitor to see how cores were loading etc I noticed the 2 I assigned stayed very busy, as expected, when compared to using the .ini tweaks from first post. However, I also noticed the 2 cores got hot very fast. Normally my load temp is approx 60-63C. Using only those 2 cores, they went up to 80+C very quickly. As a sidenote as I mentioned I'm using turbo and could also notice that the cores were staying on the "max" frequency that turbo goes to whilst playing so I'm sure the performance would've been a bit better if I had actually dared to go on playing after noticing cores got warm so damn quick. :) Now, I've never done OCing etc so I'm not even sure if ~80-85C during load is bad but since it differed so much I got worried. Perhaps I should just try to figure out how to do some minor proper OCing instead. Only ever OCd GPUs in the past, for some reason.

No it does not. You'll find ENB at www.enbdev.com. You don't need to overwrite the d3d9 file, as I mentioned you can use the proxy function within ENB to make them both load. Rename the old d3d9.dll from RCRN to anything you like, let's say rcrn_d3d9.dll. Then open enbseries.ini and on top of the document there's settings for proxy. Make sure both are set to true, and type in the filename you chose, and now they'll both load together. Also try to familiarize yourself with the ini to disable things you don't want etc. If all you want is the parallax (and most likely the new improved shadows if you're using NVIDIA, no reason not to use them as they're excellent) then there's easy ways to set it up to only load tohse things, but there's another thread for that here on the forums. :)

Ofcourse, it's just meshes. And well since ENB is a requirement, yes ENB is compatible with RCRN if you use either the injector-version of ENB or use the proxy-library function to load RCRN's dll after renaming it. And I wouldn't call it "uncompatible" with SMIM, there are just some meshes that won't be parallaxed if you put it as lower priority in the WB installer. Or if you overwrite SMIM's files it's the other way around.

Yeah both have their up & downs, but atleast lately nvidia have bad better driver support I feel. No doubt things will change around again though for some time etc

I'll do something similar aswell, I never buy the newest stuff, way too pricey. :) But IF I was, I'd wait for that one.

You can change quality of the improved shadows too via enbseries.ini The default setting (1) is low qual, 0 is high qual, -1 is extreme qual

Honestly I'd wait until the fall when NVIDIA releases their real "high-end" card that they decided to hold on to due to AMD failing to deliver proper competition for it.

Hm, where else was that reported? o_O Been searching pretty much everywhere on the net all day and tried every single seting that I possibly could before changing it randomly because I was gonna play Morrowind for a few minutes (and that requires it off with the mods I use). Anyway updated the discussion page under Troubleshooting, simply added to the text about disabling Steam Overlay that this can also fix these issues. :) found one reference in these forums I'm pretty sure there was another more specific reference elsewhere though. Ah yeah there was a line there saying SMAA might be incompatible with Steam Overlay (which it isn't though, there is a fix for it in the ini for SMAA with 1.1 and 1.2), didn't bother checking that thread though as SMAA wasn't the issue. :) Anyway, considering this had issues in the past I guess I should've considered that earlier for ENB too.. Ah well, one day lost, not the end of the world!

Hm, where else was that reported? o_O Been searching pretty much everywhere on the net all day and tried every single seting that I possibly could before changing it randomly because I was gonna play Morrowind for a few minutes (and that requires it off with the mods I use). Anyway updated the discussion page under Troubleshooting, simply added to the text about disabling Steam Overlay that this can also fix these issues. :)

I'm using a single GTX580. I'm also running the .24 beta drivers. My question though is whether or not he remembered to disable FXAA. If he didn't, of course it will look the same. Check the post I made just seconds before your reply. :)

Found the AA issue with .110 and .111 and solved it (temporarily). Also figured why so few reported it. The issue is with the Steam in-game overlay. Settings > In-Game > Uncheck the "Enable Steam Community In-game" box and AA works fine again. Also less shimmering. This hasn't been an issue in previous ENB versions so atleast I know exactly what to report to Boris now! :)

Edit: @s4now: What is your GPU? Wondering if it could be bugged out on specific card only. Noone else is even reporting the AA bug and Boris couldn't repliate it as seen below. Mine is a GTX 560 Ti-448. Devide ID is 0x1087. From Boris:

No, it's not. You run the ENBInjector.exe before you start Skyrim

0.111 released with a bunch of fixes for ATI. Still no fix for the issues we were having though sadly as can be seen here: https://i.imgur.com/n0tib.jpg

And TES3 aswell for that matter. ;)

That specific screen looks like it used to do in Oblivion when 2 mods conflicted that added changes to that specific landscape (not changes to the textures that is, but actual changes to the landscape) but with different land-height. Not sure if that's very likely if you usually have it happen up in the sky though...

The problem with it is this: Ofcourse, TES5Edit would mean it didn't need to be fixed, but we don't have that yet. As it is, it causes crashes when used together with a lot of different mods due to deleting all those records. If not using any mods that conflict however it is safe to use, but it's often hard to know until you enter a specific cell.

Yeah, post-process AA works, but as s4now mentioned it doens't fix the really bad texture-shimmering that's present only with 0.110

Here's a pic in the same loc as the last 2 screens with the 0.109 dll and ini instead: https://i.imgur.com/0jOI6.jpg As you can AA works perfectly well there, and the ONLY difference is that it uses 109 rather than 110