Aiyen

Okay I just decided to test how well all that I learned doing this had stuck in my brain. Made the bow and uploaded a new version with it as well! Took only 4 hours to make the bow.. which I am quite impressed by... I also hope that people think the result at least look on par with the rest! Enjoy!

Skylight produce prettier dragon fires >_> I guess that would be my highly subjective and semi jokingly response to that questions! :) If I have to be serious about it then I would say that vividian goes more towards realism then skylight. Also skylight have stronger colors to help emphasize the bloom more which is something I really like. But overall it cannot compete with vididan in terms of polish.. since I have not spent the amount of time manga and benhat have on making unique looking weathers and all the extra goodies you get there. I prefer to keep things really simple and effective, and some seem to think it also looks rather good. As for the SSAO... higher quality (larger texture size and detail levels) means less performance. There is not really much more to it then that.

Well that cresent thing is just funky to say the least! Almost sad now that the sword texture is imo the worst of all of them lol!

For your convenience.... That should be about the lowest possible setting you can set the SSAO to without any major flickering or other artifacts appearing. You might have to adjust the amount and intensity settings ingame to suit your liking... but that should be about it. You can just copy paste into your enbseries.ini and replace. [sSAO_SSIL]UseIndirectLighting=trueUseComplexIndirectLighting=falseUseComplexAmbientOcclusion=falseUseAmbientIndirectLighting=trueSamplingQuality=2SamplingPrecision=2SamplingRange=0.31FadeFogRange=1.0 SizeScale=0.65SourceTexturesScale=0.5 FilterQuality=2FilterType=2AOAmount=1.85AOAmountInterior=1.75ILAmount=2.0ILAmountInterior=2.0AOIntensity=1.5AOIntensityInterior=1.0AOType=1AOMixingType=0AOMixingTypeInterior=2UseOldType=falseEnableDenoiser=trueEnableSupersampling=falseILType=0EnableComplexFilter=true

Well you can just use the shiny meshes if you want... I did not touch those this time around. I have been tempted to simply remodel and re-uv the models since imo they are a pain to work with... but decided that it would expand the scale of the project too much. One of the largest limitations I had to work around was that there only is a single material for the entire weapon.. and I kinda wanted both an obsidian material and two different metal ones... but that would again require a re-mesh. It took way way way too many variations to try to make the obsidian...and compared to the reference images I went from then it still does not capture the look 100%.. mainly because I only have one specular color... and not many. As for the metal then I had hoped I could do a gritty and dirty looking metal one.. and a polished one.. but sadly that is simply not possible to do using only the textures. Oh well at least people have been kind with the comments so far and seem to like the textures. Other then a few issues here and there that I want to correct then I think it is time to move on to other projects!

Parallax requires the graphics part of ENB to function... hence there is going to be some performance drop from having that on (even with everything disabled since it still means more code needs to run)... you can run ENBoost without the graphics part alltogether however. This is the reason for any confusion on the topic. Granted the performance drop when everything is disabled is not that massive.. and most machines should be able to handle that without much issue.

Yeah well this was only an educational experience for me! Mainly wanted to try out many different techniques to see which would be more effective. Only reason the bow is not included is because well... I got bored with daedric stuff and it was really annoying not having a drawing tablet... hand drawing details took forever! But yeah there are quite a few out there... but imo most of them kinda looked to much like vanilla which was a design I am not overly fond off... always looked kinda bland and boring considering it was the "endgame" items.

Without a drawing tablet then that will be far out into the future... it is just too aggravating to use a mouse to draw with! :S

Okay the first full release version it out and I have updated the OP. Enjoy ya all.

You will be fine to do as Nozzer66 suggests. Overwrites only depend on the install order. Once you are done installing then ofc. make sure your load order is sorted and all the proper patches are where they should be etc.

To sum up this... More VRAM = more texture memory use before you get stuttering and excessive slowdowns. Nothing else really. Ofc. if you try to simply load a silly amount of textures then the game will most likely still CTD due to lacking overall memory, since the bandwidth is simply just not enough to move the data in a reasonable amount of time.... causing timeout errors and what have you. However you are still quite able to run 2k textures with just 2Gb of VRAM.... You will notice some slowdown when changing cells etc. but depending on your expectations then it is all reasonable. It is only if you absolutely expect that everything loads in instantly and you absolutely hate popin and slow texture loading that you really need more. Also reading from memory is not excessively slow... it is still in the Gb/s bandwidth range depending on your MB and CPU etc. It is true that it is nothing compared to the insane bandwidth that GPU and VRAM communicates with though.. so if you can get stuff in there all the better. What is excessively slow is if you have to read from disk!

The main reason is that supersamping is a thing of the past. Most modern engines and games made on them do no longer support that mode at all. Mainly due to various effects that wont work. You can already see ENB effects that wont work with supersamping.. it is the same thing elsewhere. Also multi card solutions tend to not like supersamping at all... but mainly the first reason. In general if you can afford more pixels then it will always be the best solution... just like atm the best solutions are downsamping and some form of software based AA technique for Skyrim... at least if you want the best quality/performance ratio. However with these new bad boys then 4k resolution at acceptable framerates is within the reach of many systems since you no longer require a dedicated wind turbine to run your computer.

Seems like you are having only a lower level mip map loaded... Most often this will resolve it self given time to load in all the proper resolution textures. How long it takes depend on your hardware and the load you ask the game to load in that particular instance. It is a bit weird that it happens inside interiors since those are normally not demanding at all.

The ENB dev hates AMD with a fierce vengeance.... and that is not likely to change at all. Add that he also dislike multicard setups on top of that and well... I guess the simple way to say it is... if you accept that there is going to be issues then go for it.. otherwise then save ya money for a next generation card instead.

I think it once upon a time was an issue.. but Boris made changes to how they worked sometime in the past. For the current version of ENB the above mentioned scale range will work just fine.. as long as you got a system that can handle it.

I made my own enbeffect.fx file, and a few others have as well. In those the Use Original part of the code is simply removed.. since why have it? All it does is simply to trigger a loop in the default enbeffect.fx file which will then use the image space values and nothing else. But if those values are messed with then it wont really work as intended or at all.. depending on the code involved. The Scales are for both the sizescale and the source values... as I recall then going higher then 250% have no effect, just like going lower should not have an effect. I think it is vital to mention it, since those two values are what really control the performance to quality ratio of the effects. Especially for reflection you can go rather low without much visual loss, but if you go really high it will just cripple your system... and the extra quality is quite... let us just call it very shot dependent. For SSAO if it is too low then you will get flickering that can be quite bad. In general for both of them then it was also to show that you can go to values above 1.0 and still get even more quality... if you are doing those super epic screenshots etc.

Okay here goes There are quite a few entries which only have an effect if you use the default files. Use original Post processing: This will only work if the file is based on Boris´s default file. The object one will still have an effect since it is object specific. Bloom, lens etc. require that you have a corresponding .fx file to work. In the case of bloom then you technically have two options. The vanilla default and the ENB specific one you find in the .fx file. For lens then it both requires a texture and a .fx to work. For DoF then again you need a .fx file that actually does something. Also the bloom quality have no real effect... at least I cannot see any difference, but then again I have not tried to use the default file in ages.. and most do not use that anyways. For both the SSAO and reflection with the Scales then the following apply //------------------------//-- Scale Info --//------------------------//50% scaling : 0.5 -> best performance//60% scaling : 0.774596669241483//80% scaling : 0.894427190999915//100% scaling: 1.0//150% scaling: 1.224744871391589//250% scaling: 1.581138830084189 -> best quality You do not have to use those values specifically, but they show how the values progress. Hope that was all clear n stuff!

I will check it out in greater detail later, and hopefully be a bit more helpful.. just been a stressful week for me! Hopefully it will all clear up for next!

Some of those mods do use the ingame DoF to create effects, which when added on top of the ENB DoF just cause..... well it aint pretty in most cases! In the wet n cold case then it happens when it rains or when you are in the dragonborn content and there is an ash storm. As I recall there also is a radial blur when you are cold etc. in frostfall

Awwwwwwwwww I guess that is about all I have to say about the mod at this time! :)

No no ESB... if it is science then it must be a conspiracy... or magic.. but everybody knows that magic is a hoax! :) That said then thanks for a good laugh!

Well when politicians can govern countries that way... why cant we approve/disapprove mods the same way! :P

Hopefully I will soon get the cash to upgrade! Just one of those babies would be x2 the performance of what I have now! :) And really quite impressive power consumption... which is more what I go for these days then the raw number crunching.

It is because the Vanilla version runs on a different set of shaders then the vivid one.

No.. you have to know what to look for in the enbeffect.fx file. However most files that are more recent will have fairly good comments on what is what. Some of the older ones are still just a mayhem of various code fragments copy pasted in because.... it worked. And like all good programmers then the people who made them never documented what they wrote or how it worked! :)