New Shader class in SFML 2 to replace PostFx

[OniLinkPlus]

And it works, but I get blank spots on the sides of the screen

Can you show a screenshot? Have you tried to disable smoothing on your image?

and there is much lag

You didn't have it before?

Can you show a screenshot? Have you tried to disable smoothing on your image?

I just disabled smoothing, and the glitch changed slightly to this:

It also does get blackness on the top and bottom of the screen once every second, and when that happens, the darker area is on the sides.

You didn't have it before?

No, I did not. I emulated a Windows program using build 1245 or so with sf::PostFX, and it ran lag-free.
I ran a native Linux program using build 1262 with sf::Shader, and I'm getting piles of lag.

[Laurent]

No, I did not. I emulated a Windows program using build 1245 or so with sf::PostFX, and it ran lag-free.
I ran a native Linux program using build 1262 with sf::Shader, and I'm getting piles of lag.

But what about native Linux program using revision 1245?

Can you upload your project so that I can test it?

I'm surprised because the internal OpenGL code related to shaders hasn't changed at all, my modifications were almost all to the public API.

[OniLinkPlus]

I updated to SFML 1268, and the glitch with the tearing and blackness is gone, but I still have the lag.
Here's the demo with SFML 1268.
http://willhostforfood.com/access.php?fileid=93440
Use run.sh to use the local .so files.

[dunce]

My laptop with ATI Radeon Mobility HD3465, Catalist 9.4 (AFAIK the last version with HD3465 support) refused to compile wave.sfx. Other shaders are Ok. Investigations showed that it had stuck at the line:

vec2 texoffset = texture2D(wave, (gl_TexCoord[0].xy * offset).xy);

If I use vec2 explicit construction, everything is Ok.

vec2 texoffset = vec2(texture2D(wave, (gl_TexCoord[0].xy * offset).xy));

I'm far far away from being a glsl guru. May this behavior be caused by the sfml current shader's version incompatibility with my hardware?

[Laurent]

Ah, true. I'll fix it as soon as possible

[Laurent]

I updated to SFML 1268, and the glitch with the tearing and blackness is gone, but I still have the lag.
Here's the demo with SFML 1268.
http://willhostforfood.com/access.php?fileid=93440
Use run.sh to use the local .so files.

I couldn't use the local .so files (my system has a problem and needs a modified version of SFML), but I tried shaders with the latest revision:
- the Shader sample runs perfectly
- I can see the lag in your application

Can you show your source code? Did you try the Shader sample?

[OniLinkPlus]

Hello!
float edge = sqrt(hEdge.rgb * hEdge.rgb + vEdge.rgb * vEdge.rgb);
That's some good coding right there.

[Laurent]

float edge = sqrt(hEdge.rgb * hEdge.rgb + vEdge.rgb * vEdge.rgb);
That's some good coding right there.

?

[OniLinkPlus]

float edge = sqrt(hEdge.rgb * hEdge.rgb + vEdge.rgb * vEdge.rgb);
That's some good coding right there.

?

The sqrt returns a vec3, since the value sent to it is a vec3. vec3s cannot be assigned to floats.

[OniLinkPlus]

I updated to SFML 1268, and the glitch with the tearing and blackness is gone, but I still have the lag.
Here's the demo with SFML 1268.
http://willhostforfood.com/access.php?fileid=93440
Use run.sh to use the local .so files.

I couldn't use the local .so files (my system has a problem and needs a modified version of SFML), but I tried shaders with the latest revision:
- the Shader sample runs perfectly
- I can see the lag in your application

Can you show your source code? Did you try the Shader sample?

Here's our repository: http://mke.svn.sourceforge.net/viewvc/mke/
I tried to Shader sample, and it works fine, so I dunno what's going on.

[Laurent]

The sqrt returns a vec3, since the value sent to it is a vec3. vec3s cannot be assigned to floats.

Ah, true (my driver accepts so many errors...).
I fixed the code, thanks.

[Laurent]

Here's our repository: http://mke.svn.sourceforge.net/viewvc/mke/
I tried to Shader sample, and it works fine, so I dunno what's going on.

It seems like clock() has a very low resolution on Linux. Using a sf::Clock solves the problem.

[OniLinkPlus]

Here's our repository: http://mke.svn.sourceforge.net/viewvc/mke/
I tried to Shader sample, and it works fine, so I dunno what's going on.

It seems like clock() has a very low resolution on Linux. Using a sf::Clock solves the problem.

Alright then. Thanks for the help! I switched to sf::Clock and it works perfect!

On the shader sample, global fisheye Y coordinates are flipped for me. It doesn't do this with background, and I can't tell on flower.

[OniLinkPlus]

So I am trying to make the screen draw two shaders, right? Here's the shader code in the Title Screen in Main.cpp of my repository(not committed yet):

Code: [Select]

       if (sf::Shader::IsAvailable()){
            Water.SetTexture("screen", sf::Shader::CurrentTexture);
            Water.SetParameter("time", Clock.GetElapsedTime()*1000.f);
            Blend.SetTexture("screen", sf::Shader::CurrentTexture);
            Blend.SetParameter("color", 0.5, 0.0, 0.5);
            Blend.SetParameter("alpha", 1.0);
            sf::RenderImage Screen;
            Screen.Draw(BG);
            Screen.Display();
            Window.Draw(sf::Sprite(Screen.GetImage()));
        }
Guess what? I just get a white screen. Why is this? When I replace the Window.Draw line with Window.Draw(BG); it works fine. When I use this code, it absolutely fails. What am I doing wrong? I'm drawing the BG to the RenderImage, Displaying the RenderImage, then drawing the RenderImage to the Screen, and I get White. :S

[Laurent]

On the shader sample, global fisheye Y coordinates are flipped for me. It doesn't do this with background, and I can't tell on flower.

I know, this is a bug in the code of the shader.

Guess what? I just get a white screen. Why is this? When I replace the Window.Draw line with Window.Draw(BG); it works fine. When I use this code, it absolutely fails. What am I doing wrong? I'm drawing the BG to the RenderImage, Displaying the RenderImage, then drawing the RenderImage to the Screen, and I get White. :S

Your RenderImage instance gets destroyed after the call to Draw; but SFML delays the actual drawing until you call Window.Display(), and at this time the source image doesn't exist anymore.