[Sandy] movie material and timer based updates

Andy bowljoman at hotmail.com
Sat Dec 15 17:19:32 PST 2007


No , I propose 'no timers' and use the render event.

The divider idea provides a mechanism to reduce the material updates.


If I understand you correctly Andy, you propose to have a common Timer  
for all animated materials?


Le 16 déc. 07 à 00:27, Andy a écrit :

>
>>> On Dec 15, 2007 9:24 PM, Andy <bowljoman at hotmail.com> wrote:
>>> would it be less overhead to not have a timer for these types of
> dynamic
>>> materials ?
>>>
>>> what about the material updates for every render()
>
>>> yes, this can be done using SandyEvent.SCENE_RENDER_DISPLAYLIST
>
>>> and provide a divider
>>> value instead of a timer object.
>>>
>>> new VideoMaterial(vid,(1 out of 4 render calls),null);
>>>
>>> or  actually
>>>
>>> new VideoMaterial(vid, 4,null);
>>>
>>> then create some micro counter in the  material class that makes an
>>> update on value 1, so if you pass a large number to the material, it
>>> counts render calls, resets the counter to 1 at the constructor
> value,
>>> then updates the texture.
>
>
>> you mean, to skip every 3 of 4 render()-s ? surely possible, but why?
>
> Yes.
>
> To provide the same functionality as the timer update interval and  
> still
> drop the need for the timer.
>
> If nobody uses the timer variable and the event is present, then why
> have the timer at all?
>
>
>
>
> _______________________________________________
> Sandy mailing list
> Sandy at osflash.org
> http://osflash.org/mailman/listinfo/sandy_osflash.org


_______________________________________________
Sandy mailing list
Sandy at osflash.org
http://osflash.org/mailman/listinfo/sandy_osflash.org




More information about the Sandy mailing list