Shaders

[PsychoChris]

Hello,

the current shader implementation doesn't provide the coordinates of the pixel beeing processed. I thought about doing shader stuff manually by locking a surface and manipulating its pixels by hand.
Now i'm asking myself if this would have the same performance like using the given shader class or does it use some optimizations?

Greetings and thanks,
Chris

[Kzinti]

[PsychoChris]

[Kzinti]

[PsychoChris]

[Kzinti]

[PsychoChris]

Thank you for your help. After digging deeper into the template stuff for pixel operations i finally managed to get pixel shader lights working.
I found some comments that you intended to change the template stuff and exchange it with new shader code. I'm curious: What exactly did you want to change?

Greetings,
Chris

[Kzinti]

[PsychoChris]

I don't know if i should laugh or cry after reading that...

btw: I send you some days an email through this board but didn't get a reply. Is the email functionality working or perhaps your email here out of date?

Greetings,
Chris

[Kzinti]

I did get an email from you asking about this x,y thing in shaders. I also saw the post here and decided to answer here. This way everyone benefits from the conversation.

If your email was something else, then I am afraid I did miss it.

[PsychoChris]

[jaguard]

[PsychoChris]

It still surprises me that the amount of parameters passed, especially if its just one object of the Point class, influences performance so much. I will try out passing only x and y in different variations to see how much performance changes i can see.

Next problems i'm facing with the light shader are the slow floats and a sqrt for calculating the distance between two points like sqrt(p1.x*p1.x + p2.x*p2.x). Any ideas how this could be improved? Perhaps somehow without the need of floatingpoint calculations.

btw jaguard: Can you give me an idea when your current game will be finished? I'm waiting for it.

Greetings,
Chris

[jaguard]

[Crayfish]