TES Skyrim 0.215

[electricsheep26354]

The only reason I used SweetFX is that I liked it's Vibrance effect. Today I decided to bite the bullet and try to port it to an effect.txt. I am embarrassingly pleased with myself to have got it to work, took me about half an hour ...

Would you consider posting your code for this? I (and I'm sure others) would be interested to try this

Many Thanks

[ENBSeries]

Looked in to code and found that precision of shader parameters already available, but not used by editor only, probably i did this for the future, don't remember. If someone need it, use annotation "UIStep" or "uistep", i'll try to implement precision in editor only for shader variables to not fall in to complex changes of my code. If it will fail, then uistep simply will not be usable and i'll try to force 3 digit precision.

[Winterlove]

Would you consider posting your code for this? I (and I'm sure others) would be interested to try this

Many Thanks

Yeah, why not. Provided it's clearly understood that I'm posting it as-is and my ability to offer support is very limited. It's very rough-and-ready and could probably do with some polish, but it seems to work. You can find it at http://skyrim.nexusmods.com/mods/41905/? . Have fun.

[electricsheep26354]

Yeah, why not. Provided it's clearly understood that I'm posting it as-is and my ability to offer support is very limited. It's very rough-and-ready and could probably do with some polish, but it seems to work. You can find it at http://skyrim.nexusmods.com/mods/41905/? . Have fun.

Thanks Winterlove - works a treat!

[Rexawl]

Transparency AA включено, либо edge aa.

Во всём оказалась виновата моя жопорукость. Я читал где-то что вы НЕ рекомендуете лезть в NVIDIA Control Panel, поэтому я полез туда и сделал все настройки по умолчанию. Размытость пропала.
Спасибо и простите за беспокойство.

[ENBSeries]

Okay, i did UIStep for "float" shader variables only, will be in next version.

[MOTOSXORPIO]

Would I be able to simply add new shader code to MTichenor's enbeffect.fx without a whole rewrite?

[--JawZ--]

Directives will need to be replaced with statements, if {} instead of #if #endif.
Then you need to remove the current tweak commands, float = 1.0; with the GUI tweak commands.

The Equalizer is the one thing that can cause problems with GUI implementation.

If that was the thing you where referring to by "new shader code". Otherwise any HLSL code can be added or removed within any of the .fx files and .txt file no matter what.

[MOTOSXORPIO]

Directives will need to be replaced with statements, if {} instead of #if #endif.
Then you need to remove the current tweak commands, float = 1.0; with the GUI tweak commands.

The Equalizer is the one thing that can cause problems with GUI implementation.

If that was the thing you where referring to by "new shader code". Otherwise any HLSL code can be added or removed within any of the .fx files and .txt file no matter what.

Thanks for the tips, --JawZ--

[ENBSeries]

Instead of "if {} else {}" better to use them in vertex shader to change vertices of quad, while ach pass in technique with own vertex shader will be used as "if else". Something like this:

VS_OUTPUT_POST VS_PostProcess2(VS_INPUT_POST IN)
{
VS_OUTPUT_POST OUT;

float4 pos=float4(IN.pos.x,IN.pos.y,IN.pos.z,1.0);

//move outside of screen all vertices:
if (ShaderType!=2) pos=10000.0;//v1 as int
//if (EnableSomething2==false) pos=10000.0;//v2 as bool

OUT.vpos=pos;
OUT.txcoord.xy=IN.txcoord.xy;

return OUT;
}

technique PostProcess
{
//only drawed when some parameter 1 set true
pass P0
{
VertexShader=compile vs_3_0 VS_PostProcess1();
PixelShader =compile ps_3_0 PS_PostProcess1();
}
//only drawed when some parameter 2 set true
pass P1
{
VertexShader=compile vs_3_0 VS_PostProcess2();
PixelShader =compile ps_3_0 PS_PostProcess2();
}
}