I found out what the problem was. In my code I throw the ObjectContainer back and forth between two views and it seems that Away3D is holding on to the references to the MovieClipSprite.
I solved it by removing the sprite before changing the parent view and then adding it again when added to the new view. On Apr 6, 10:21 am, Johan Larsson <[email protected]> wrote: > Hi, > > I have around 40-50 movieclipsprites that hovers around an object > (like hotspots) as the camera can be navigated around the object. > > I'm seeing massive slowdowns when these movieclipsprites are active. > I'm also seeing the polygon counter (the right yellow counter) go > through the roof with each render. > > I don't think I'm doing anything out of the ordinary here. The > MovieClipSprite is part of an ObjectContainer that also contains a > LineSegment (that points to the object in the center). > > The movieclipsprite itself contains a background (Shape) with opacity > and a textfield. > > var hotSpotSprite:Sprite = new Sprite(); > hotSpotSprite.addChild(bg); > hotSpotSprite.addChild(tfLabel); > > label = new MovieClipSprite(hotSpotSprite); > > The ObjectContainer is initiated and handed over to the MovieClip with > the Away3d-scene and this MovieClip puts all 40-50 of them inside the > away3d-scene at their respective coordinates. > > This MovieClip then displays the ObjectContainer by calling this > method: > > public function show():void > { > if (hidden) > { > hidden = false; > > line.start = _truckPoint; > line.end = endPoint; > > addChild(line); > > addSprite(label) > } > > } > > Is there an issue with movieclipsprite that I'm not aware of or am I > doing something wrong? I'm quite new to the 3D-world and especially to > Away3D. Don't hesitate to tell me that I waltzing around on pink > little clouds and that this is not the proper way to solve my problem.
