A Bug in MMF2 killed my widget
For this active object I have set three float alterable values between 0 & 1.
In an object behaviour's I have set it to change RGB coeffeciency to GetRGB(Alterable Value A*255,Alterable Value B*255,Alterable Value C*255)
But when I run my app no matter what I change these three alterable values to, the RGB Coeffenciency will remain at the colour "FFFFFF".
One thing that is interesting is that it works correctly for my Alpha Coeffenciency and that is done the same way.
Help Please
Re: A Bug in MMF2 killed my widget
well since HWA's still beta there's probably a few non-working things in it
EffectParam() doesn't work either so
Re: A Bug in MMF2 killed my widget
Works fine here... Are you sure you are setting the values correctly? Starting values cannot be floats for example.
Re: A Bug in MMF2 killed my widget
If I change it to run with my own math instead of the built-in GetRGB I still get the same bug but this bug appears to be completely limited to none Direct 3D rendered applications.
Re: A Bug in MMF2 killed my widget
RGB coefficients are new for the HWA builds, so it's probably just not fully implemented yet.
Re: A Bug in MMF2 killed my widget
RGB Coefficient is a Direct 3D feature. Naturally it won't work for the standard display modes.
Re: A Bug in MMF2 killed my widget
True that is a feature of Direct 3D but it can easily be implemented in Software Rendered, can't it?
Re: A Bug in MMF2 killed my widget
DragonGuy you are officially my favorite person to quote.
Re: A Bug in MMF2 killed my widget
Yes it could be implemented in software, but it hasn't yet. It's a feature introduced with HWA, and HWA isn't finished yet.
Re: A Bug in MMF2 killed my widget
I hope that a software version of the effect will be implemented, if not just to make MMF less "this feature only works with HWA, that with Java, and another one only in Standard".
Of course, HWA is in beta stage, so as I said it's logical that it doesn't work now.