Spock

Dunno about crucial, I always got G.Skill. With G.Skill it used to be that all the clock and timing configurations have the same chips anyways. There was a list at Xtremesystems that showed which version numbers where which chip and then you could look at the OC results. Maybe there is something similar for Crucial. Also note that AMD CPUs are more sensitive to timing then Intel CPUs. That means more clock at relaxed timings isn't better for AMD. Try to find 7-7-7-x, 20<x<29 timing ram. Lastly, ram memory bandwidth isn't that important for most applications, they mostly bottleneck on other stuff. [edit] I did a little checking on newegg, it was a pain because you cannot sort ram by cl ratings. I found a decent cl 8 g.skill ram (cl is short for cas latency): https://www.newegg.com/Product/Product.aspx?Item=N82E16820231445 If you really don't want to overclock that one seems fine. You can even try to apply the latency configuration of this one in the bios and see if it's stable (no overclocking, just reduce the latency): https://www.newegg.com/Product/Product.aspx?Item=N82E16820231308 They are probably the same chip anyway, I got that RAM in a 3x2 gb configuration at 1.45 GHz. You might also want to check ebay, as many people think they have to upgrade to 16gb. G.Skill has livelong guarantee anyway. If you don't have quad channel on your CPU/Mobo, that is a very bad investment because using just two dimms with dual channel is faster and cheaper then using four.

Just checked, the helper comes with the performance download. You probably don't have the right ESPs enabled. Your weather and lighting setup needs to be ELE lite, RS and the weather plugin in the download. No ELFX no CoT or any other weather or lighting mod. For testing purposes I would give the weather and lighting esps very high priority in the load order.

Personally, I would highly recommend getting the r9 380 with 4gb over any Kepler GPU. The reason is that Kepler has very few shader units to begin with and lacks important architecture features. Maxwell and GCN shader units start work on the next instruction in the shader when they have to wait for the Vram. That is probably the reason Kepler sucks at Witcher 3 and I would expect more titles in the near future requiring those features for decent performance. Another argument for the r9 is, that post processing in games is the future. If two cards are comparable, I'd always go with the one with more shader power. Not to mention other non game related applications like madVR/SVP.

I'm currently on team red and have to problems whatsoever. I know there is a lot of NVidia love here but tbh, they make bad stuff too: gtx 970 and the whole Kepler generation with it's shitty shader architecture. I too prefer NVidia if their current architecture is good and affordable for their bigger driver staff, but currently it's not :/

Well, post processing AA other then Temporal AA cannot truly get rid of the shimmering when moving. They also have disadvantages and reduce image quality. SMAA is quite reasonable while FXAA is really bad in that regard (see my post in the Witcher 3 modding guide). Temporal AA always has some ghosting but I found the ENB TAA not too distracting last time I checked. The shimmer your scene produces is quite bad though, I usually only get it with fences and to some extend with foliage. Maybe something else is wrong? Check your CCC to see if everything is set to the first option except for texture filtering to max and vsync to what works with ENB. Try different AF handling (CCC or ENB), if nothing helps maybe try a different texture. It could also be an ENB setting exacerbating the problem, did you try different presets?

Well, that is odd. Make sure you have the correct lighting esp files enabled: RS and Enhanced Lighting for ENB and the weather esp from Lumen, no ELFX or CoT. Then make sure you got the helper dll in the correct spot. My guess would be a missing helper dll, what you describe is similar to what I saw when I forgot the helper.

On a sidenote: Personally I'd recommend against CoT and ELFX and go with the STEP lighting solution + Lumen ENB instead if your GPU can handle it (and if you are fine with 30 fps). It helps solve a lot of hassle with all the cell edits from ELFX/CoT and imho looks better because ENB weather handling gives more options then just an esp if done well (and Jafin is a genious, his ENB gets way not enough endorsements!). I also really need to make a new STEP patch, sorry for my poor support.

Thank you for the guide! I would highly advise against FXAA though. It blurs textures and thus reduces image detail. It also bugs with long edges. Here are some examples: https://m.hardocp.com/image.html?image=MTM3NzA1NzMxNkVZNWVSbllTcVpfNF81X2wucG5n https://i121.photobucket.com/albums/o240/walkingdog/fxaa%20smaa/GOTHIC3.jpg https://community.pcgamingwiki.com/uploads/gallery/album_34/gallery_371_34_32435.png https://i.imgur.com/NIi0A.png

Sorry for the double post but official benchmarks are leaked: https://videocardz.com/56711/amd-radeon-r9-fury-x-official-benchmarks-leaked They should be taken with a grain of salt though. Fury will probably benefit much more from it's memory bandwidth at 4k then at 1080p. Also, AMD will have picked the most unfavorible settings for NVidia.

I don't think HBM will have a huge effect on Gaming performance at 1080p. Afaik the latency of HBM is acutally not lower then GDDR 5, I doubt the extra bandwidth will be of much use. For compute this is a different ballpark. Afaik there are compute tasks which are severely bottlenecked by memory bandwidth. The better power efficiency and the advantages for the PCB layout will be huge for clusters. Also: 8.6 (theoretical) TFlops! THat shader performance will probably allow you to go bonkers with ENB settings. This will probably be the card that can handle Skyrim at 1440p/1600p with demanding ENB settings.

https://videocardz.com/56561/amd-unveils-radeon-r9-fury-series The price tag is much lower then expected. And it appearently caught up with Maxwell at resterization power efficiency. NVidia might have a problem untill Fermi gets released. Kepler just sucks because it lacks critical features, and the 970 has the vram issue. So they really have only 3 viable cards for team green and those are in the higher price range atm. More about the architecutres: [edit] Next gen NVidia is Pascal, not Fermi. Sorry for the blurp.

Well, I must say I like the visual style. It looks like a tool, not like crapware. The question is, is there crapware going on under the hood?

When it comes to compute, probably even more ;P My first guess would have been that your issue is due to a lack of vram. Are you sure you properly uninstalled all the textures related to that hut? Are you sure your tool displays the right vram usage? 200 mb seems really low even for vanilla (just intuition, didn't test it).

Do you know if actor fade as an impact on script load with stuff like footprints and wet and cold?

I would highly recommend against increasing the grass draw distance without increasing ugrids. The reason is that you get more popping on cell transitions, it is imho one of the few very well tweaked ini setting by bethesda. The maximum value for object and item fade without popping at ugrids 5 is 10.5 btw :) Personally I use 10 for items because I don't want daggers to fade in at the same time rocks do. You can also try fTreesMidLODSwitchDist=14000, it is a trade off which eases popping a little but makes trees switch to full foliage as you close in on them (still as far away as possible).

Interresting! bShadowsOnGrass and bDoDepthOfField should be enabled with an ENB. The first one makes grass look funny with an ENB for me, the second is required for some water effects. It took me quite some time to find out about the second one. I would be very interested to know more about the right LOD fade distances. I couldn't see any difference between high and ultra for stuff like fTreesMidLODSwitchDist and combined with the poor fLODFadeOutMult values I think they just cranked everything to max paying no attention to whether it looks better or not.

Out of curiosity: Are you also reconsidering choices for textures depending on the parallax effect for that pack?

Huh, I just read about the PowerDVD fluid motion. It seems to actually be a driver feature of the 14.12 omega drivers of AMD that does something similar to SVP. It may be better optimized for lower end GPUs.

Afaik that is lens flare. Try to set EnableLens=false under [effects] in the enbseries.ini.

AF can be kind of subtle depending on the scene. Stuff like normal mapping, parallax and post processing can mask the effect a little. This really depends on the scene. I suggested an even smaller angle simply because you can immediately tell then if AF is on or off. If it is off, the wall will become so blurred that you can immediately tell. Those corner shots look like AF is enabled in both of them though. As a general guideline, I would always keep AF at 16x, it is very cheap but usually has a great effect on quality, even if you cannot always pinpoint it. I just noticed my direct image link from my previous post doesn't work. It's the example from this article (scroll down to the AF section): https://www.tweakguides.com/Graphics_11.html

You will get better compares if you have your shot, then turn off your mouse, save the game and then take the comparison shots (without moving the mouse). Try to make the angle even smaller around the corner, you will definitely see the difference in AF. Here is a rather extreme example of what AF does (this is probably an older game with less post processing effects so it is more visible): https://www.tweakguides.com/images/GGDSG_22.jpg

Some of the comments gave me a good laugh :)

It becomes very obvious if you look at textures at a very small angle, like around the corner of a building.

Hmm... a laptop will probably not provide the performance to make SVP look good. I'd advise you to try the MadVR smooth motion, it helps quite a bit.

Those settings are quite lower then mine, I use defaults except for artifact masking: weakest and processing: blend adjacent frames. After a quick test of your settings, turning the frames interpolation mode back up to adaptive makes a huge difference for the smoothness. The MadVR smooth motion option looks better then SVP 2m imho.