Animated Picture Object question

[Nobuyuki]

Hello, a quick question about the Animated Picture Object:

Does this object support changing the ink effect or transparency at runtime? So far, I have been unsuccessful in getting it to do so, despite the functionality being exposed in the event editor. Changing it in the Frame Editor is not a problem, however for my game I need to be able to change at least the opacity at runtime...

(This question is for the non-HWA build of MMF2)

[Jacob]

Why not HWA? It is stable enough.

[Nobuyuki]

Mainly because there are other objects which are not made for HWA that I'm using in the project, which would cause graphcal or other issues if building with it. I don't know how or if the effects used by Animated Picture Object are supported in HWA. The ink modes, for example, are completely supported in Background Images Object (which I'm also using), but BGO is not supported in HWA.

However, that's all beside the point, isn't it? I know what isn't supported in HWA, but what purpose would there be to use it unless Animated Picture actually did support opacity at runtime in HWA? I guess my next question would be if it actually does support it under HWA, or if it is similarly limited in either build.

[Nobuyuki]

Hello hello, I have an update to add to this thread, although sadly for anyone else using Animated Picture it probably won't solve your problem if you're having the same one I'm having:

I tested this object with HWA to see if it plays nice with hardware blending and sadly this doesn't seem to be the case. Semi-transparency does not work whatsoever for this object in HWA, and dx9 shaders will crash EDRT if you attempt to use them

I suppose there must be another way to have external animated pictures which can have ink effects applied to them.....

[LB]

Load the images into an active object?

[Nobuyuki]

this will work, of course, but I am envisioning that there are a bit too many images to do this the way that I'd like. I might try and get in touch with the extension developer in case this is a bug and not a deliberate feature omission...