My condolences and best regards, mate :cake: But bear with me please, have you any ideas on the save record format ? Or are you yet to think of one ?

Changing half variables to floats worked as per wrinklyninja's suggestion. Thanks wrinklyninja! I'd have tried your method too if I'd have known what you meant. Is one method better than the other performance/bug/other wise?

Setting the flag will remove the need to modify the shader file after each install.

Sadly OBGEv2 disables antialiasing for me, only just noticed. I'm only using old OBGE mods (Ambient Dungeons, Motion Blur and Move Forward Blur) so am using the obge packaged with motion blur and it works fine. Will keep an eye on development here tho.

I would like to make use of the plugins you guys have done, however it's not clear what kind of performance hit there is. I just don't want to turn my borderline slide show into a still image

The only thing you'll take a hit from is SSAO; everything else doesn't really do much to performance.

Good to know

Do you think it would be possible to implement a fake form of AA? Some games, like S.T.A.L.K.E.R., have a built in mechanic where you can implement a blur shader that acts as AA, since AA is not able to be used in it, which masks the jaggedness of edges without AA. That way, I guess it could be a temporary solution to the problem of not being able to use AA with OGE, and it could be a solution for those who wish to smooth the edges of objects while using HDR.

Just a question.

Actually, it's as optimized as I can get it until more scene information is made available. The surface normals will go a long way towards getting something that is half way decent performance wise, as well as the directional occlusion stuff everyone has been interested in. Most of the GPU power is going into extrapolating what the surface is doing, trying to replace the information the surface normals would have provided outright.

...but we won't see the normals for a while, I'm sensing.

I wasn't able to come up with any ways of getting any better performance out of the shader as it is now, but any one of you is free to try and optimize it yourself, or even just throw out some ideas. If something plausible comes about, I'd be happy to try it out.

I added edgeAA to the edge detection shader yesterday.

I`m glad that you stop by Scanti, hope you get better soon :wave:
Good luck with the save/load routines.

shadeMe, I was planning to reduce the pinkness level in your colormood.fx file and maybe add a little earth color (brow,red,orange), but I have no idea how to do it.
Could you please guide me on how to ? :angel:

Do you have the latest version ? I added a few more comments after the first upload. In any case, you'll need to change the moodR/G/B variable(s)' values. R = Red component of the filter, G and B = Green and blue components respectively. An orange palette should be essentially have the following values :

const float fRatio = 0.25;	// blend ratio (0-1)const float moodR = 0.50;	// mood color red componentconst float moodG = 0.35;	// mood color green componentconst float moodB = 0.2;	// mood color blue component

Thank you for your quick replay shadeMe :icecream:

Ha. I didn't even notice that it had that feature with it. All I could tell it could do from the screen shots was make Oblivion look more Borderlands-ish. Thanks for telling me that. :tops:

Tested out the values you add, liked it a lot, thank`s shadeMe :foodndrink:

What is the order that the fx are supposed to be listed in shaderlist.txt,

on first page never mind me..

No sense in making new post



Thank you for edge detection

almost has good looking has ATI AA and Edge Detect ..Far are Stuff in particular, and mid range stuff.

Here is some pics of your Edge Detection AA at work..Nice

http://i131.photobucket.com/albums/p305/corepc/ScreenShot544.jpg

http://i131.photobucket.com/albums/p305/corepc/ScreenShot545.jpg

I'm trying to get my head around this vertex shader stuff, got a couple of questions:

1. Can you have a shader with only a vertex shader part to it, or does there always need to be a pixel shader?

2. The pixel shader is run after the vertex shader, but does that run off the changes made by the vertex shader, or just from the original frame?

Thanks in advance for answers.

EDIT: Oh, and if someone could give me example code of a vertex colour change, and the same thing, but using the pixel shader, that'd be great. I understand pixel shader, but vertex is new to me.

Vertex processing can be further subdivided into a few major blocks of processing: notably, transformation, lighting, and to a limited extent, texture coordinate transformation. Transformation involves taking position data as it's stored in a vertex structure and transforming it into a 'screenspace' position. 'Screenspace' refers to the 2D plane that represents the viewer's window onto the world. If you like, it's the front of the monitor in the real world, and the viewer's position in the game world.

The pixel rasterizer will take all of the information passed through from the vertex processor and compute a final pixel color, based on these values. A basic example of its usage might be to take the diffuse color and multiply it with the texture color (using the texture coordinates to retrieve a color from the current texture).

Here's a sample of a single vertex shader:

Technique T0{	Pass P0	{		VertexShader = decl    		{			stream 0;			float v0[4]; // Position RH			float v7[2]; // Texture Coord1			float v8[2]; // Texture Coord2			float v9[2]; // Texture Coord3			float v10[2]; // Texture Coord4			float v11[2]; // Texture Coord5			float v12[2]; // Texture Coord6    		} asm {			vs.1.1			def c0,1,1,0,0			def c1,2,2,1,1			sge r0.xzw,v0,c0			slt r0.y,v0,c0			mul r0,r0,c1			sub r0,r0,c0			mov oPos,r0			mov oT0,v7		};	}}

Sorry, I don't speak ASM. HLSL for me. Though the bit about the rasteriser was what I wanted to know for my second question, thanks.

EDIT: I had a look at the MGE shaders, only VShader2.fx is an HLSL vertex shader, and I tried following it's example, but no matter what, when I set the PixelShader = NULL; the screen will be solid white (minus HUD of course). Anyone know why?

I feel dumb asking this...but what is the command to turn the shaders off?

As far as I know, there is none, yet.

I'm not sure there is one that you can use from the console. There's RemoveFullScreenShader, but that requires the output of LoadShader to run, which you can get using the console, unless you assign it to some random quest variable, which is a pretty bad idea.

The edgeAA screenshots haven't been included in the OP.


It just creates the illusion of AA, unlike ATi's edge detection AA ( which uses standard AA techniques on just geometric egdes, instead of sampling the whole screen ). Looking closely at the edges will show jaggies regardless of edgeAA. But what the heck - it's willing suspension of disbelief in any case

Now there are some images to post of edgeAA at work..

Now if you can get the close up cell to look that sharp has well that would be great.

If you want I could make a Comparsion shot has I cannot get the detail on mid range and far distant stuff to even be that sharp with AA 4x (12 Edge Detect Turned On) and AF 16XHQ Turned On with my 3650..

ShowTestShader 0