MMF2 HWA - Build #250 (Beta)

[Yves]

Do you mean in the picture editor?

[iamjot]

Yes sorry Yves. Right. But it did not crash since yesterday actually. So maybe it was just a problem of my (yesterday) computer. I think its alright now and it had (90 precent) nothing do to with the new hwa but with my computer.

thx for the new update!

[Atom]

Just wondering is there any way to return a float value from a HLSL effect? So you could use it for a calculations on the gpu etc, i can only find ways to set values so i guess the answer is no for now.

[Pixelthief]

eh, effect->effectparameter("") in the expression editor for just about everything? You could adjust the effect parameter itself in your HLSL script

[Yves]

The answer is no, there is no function to retrieve the value of parameter after the pixel shader has been processed, you can only retrieve its initial value.

Well, we could add this feature, but would this be really interesting?

[Atom]

eh, effect->effectparameter("") in the expression editor for just about everything? You could adjust the effect parameter itself in your HLSL script

I don't mean return the value set on the top level i mean actually returning a value from inside the effect. If i return from the MMF edit box it works ok, if from inside the effect or a float that is not top level (can't set from MMF) it doesn't work.

The answer is no, there is no function to retrieve the value of parameter after the pixel shader has been processed, you can only retrieve its initial value.

Well, we could add this feature, but would this be really interesting?

Thanks for the answer, yes it would be very interesting. People are using this type of thing with AS3 effects to put advanced calculations to the GPU and have even used it for things like audio synthesis so it would be great to be able to do it with HLSL also.

Basically it's a very nice way to optimized cpu usage by using gpu instead, also it is good for debugging and dynamic systems where you need to return from the effect. If it could be added that would be really great

[Pixelthief]

Shouldn't you be able to edit the parameters from inside the HLSL anyway? I gather that you can't and just tested that, but seems a bit logical that it should work both ways. I mean as long as its not hurting efficiency somehow. I'm curious how local those variables are now. Are they set each time the script is called (per frame), or once per pixel callback?