Make two shaders to work with WInUAE

[Leandro Jardim]

Hi,

Anyone with skills to write DirectX shaders, could take a look at these filters, and see if they can be made to work with WinUAE? They are the only ones that not works on my computer, I dont know why...

And at the same time, would be very nice to have these two filters for community use; please?

(They are pure Direct3D filters, of course, but with a .txt extension.)

[Toni Wilen]

"float2 InputDims : INPUTDIMS" needs changing. WinUAE does not set INPUTDIMS (will be in next beta). Workaround: set it to same value as your window size (for example if 800x600, "float2 InputDims : INPUTDIMS = { 800.0, 600.0 };"). Image will be distorted if value does not match display size.

function "float2 bkwtrans(float2 xy)" "point" variable is apparently reserved word, rename all "point" words to some other, for example "pointx" (Only lower case "point", upper case "POINT" must not be changed)

[Leandro Jardim]

Thanks Toni, it is working now, but I think I will wait for the next beta to use them.

[Supamax]

Originally Posted by Leandro Jardim

Thanks Toni, it is working now

Hi Leandro,
would you upload a pair of screenshots showing how these two filters look like in WinUAE?

(And, if you want, the two corrected .txt files)

[turrican3]

Originally Posted by Supamax

(And, if you want, the two corrected .txt files)

+1

Originally Posted by Toni Wilen

(will be in next beta).

thanks toni.

[Leandro Jardim]

Hi,

Well it works but it is too slow for me I was trying to use this filter together with "TysonCRT", another filter, and with Aperture2x4rb, a mask, as a way to get a nice CRT TV display on my LCD, but they not work together too.

Will be too bad for me to snapshot bad pictures with this filter in WinUAE, so I will post only the updated filters for you guys to test on your home, sorry.

[Toni Wilen]

These kinds of shader filters require lots of GPU power. CPU speed is not important. Each pixel requires 10-1000 shader instructions (closer to 100 or even more with this shader), all pixels will be calculated 50 times/second.

Try commenting out oversampling, "#define OVERSAMPLE" -> "//#define OVERSAMPLE"

Another solution is the usual: Buy a better PC. (Or at least GPU)

[Leandro Jardim]

Ah, this means that there is no way for me to get a fast CRT display with my configuration, well, I am happy enough with TysonCRT + Aperture2x4rb, I tweaked both two little a bit, together they look a lot like my old Philips 28' CRT TV...

Thanks Toni, nice that you clarified this issue, it has "bugging" me a bit, since the first time I installed the filter that started the conversation.