I see a typo in my previous message
>>  just to make sure somehow the container and content do have same shared 
>> name.
I mean NOT
when you parse you might have a container with same name as a mesh inside. make 
sure you apply only to mesh just to be sure.

>>>   if (child is Mesh && child.name.indexOf("bt_artwork") != -1) {


What is the material type? if its a MovieMaterial, and its updated it could 
cause this flickering if the mc source is not stopped.

Fabrice
 

On Sep 2, 2010, at 11:01 PM, giorgioErre wrote:

>> we wrote them :))
> 
> eh eh I think the same
> 
> now I'm in tilt little bit...I try with
> for each (var child:Mesh in model.children)           {
> 
> but nothimg. I try many different combinations with forceupdate and
> with different listeners but nothing...Fabrice heeeellllppppp!!!
> 
> In the enterframe loop I use _view.render(); I think this is the key
> of the question. And, all the meshes have diffent names. The red spot
> is a single mesh, when rollover I apply the transform of the invisible
> button to the red spot.
> 
> On 2 Set, 22:04, Fabrice3D <fabric...@gmail.com> wrote:
>>> What I don't understand is why the other examples donwloadable from
>>> away3d.com don't present this issue...
>> 
> 
>> 
>> bad joke :) seriously, try check on type Mesh instead of Object3D, just to 
>> make sure somehow the container and content do have same shared name.
>> 
>> Fabrice
>> 
>> On Sep 2, 2010, at 9:43 PM, giorgioErre wrote:
>> 
>> 
>> 
>>> well, here some code:
>> 
>>> private function onObjLoad( e:Loader3DEvent ):void {
>>>    model = _loader.handle as ObjectContainer3D;
>>>    for each (var child:Object3D in model.children)         {
>>>        if (child.name.indexOf("bt_artwork") != -1) {
>>>            child.addOnMouseOver(overQuadro);
>>>            child.addOnMouseOut(outQuadro);
>>>                child.mouseEnabled = true;
>>>                child.useHandCursor = true;
>>>        }
>>> }
>>> What I don't understand is why the other examples donwloadable from
>>> away3d.com don't present this issue...

Reply via email to