TronicVolta

Have you been able to get other custom classes to work? Try the zip I attached, it's just a sample fla with a moveiclip that tweens across the stage.

The reason it's appearing jittery is because flv video uses an interframe codec in which frames are described based on the differences from keyframes. This make the CPU work extra hard to play in reverse which is making it jitter, and doesn't have anything to do with TweenMax. My advise would be try using a sequence of images instead, or increasing the amount of keyframes in the video. Hope that Helps.

Your code looks fine, so it should work. Are all the movie clips you're tweening using the ColorMatrixFilter the same color? Maybe you're confusing the ColorMatrixFilter with Tint. According to the documentation it says: Colorizing a DisplayObject makes it look as though you're seeing it through a colored piece of glass whereas tinting it makes every pixel exactly that color.

I would define the timeline instance outside the playAgain function, and set it paused. Then in the playAgain function I would just restart the timeline. Try this out: import com.greensock.*; import com.greensock.easing.*; var timeline:TimelineLite = new TimelineLite({onComplete:playAgain, paused:true}); timeline.append(new TweenLite(box1, 1, {_x:100, ease:Expo.easeOut})); timeline.append(new TweenLite(box2, 1, {_x:200, ease:Expo.easeOut})); timeline.append(new TweenLite(box3, 1, {_x:300, ease:Expo.easeOut})); timeline.append(new TweenLite(box4, 1, {_x:400, ease:Expo.easeOut})); var cycles:Number = 0; function playAgain():Void { if (cycles <= 2) { timeline.restart(); cycles += 1; } } playAgain();

One way would be use the yoyo functionality with the repeat parameter set to 1. import com.greensock.TweenMax; TweenMax.to(mc, 1, { scaleX:2, scaleY:2, yoyo:true, repeat:1});

This functionality lives within TweenMax now. So you would just use: TweenMax.allTo(mcArray, 0.25, { alpha:1 }, .1);

Have you tried using TweenMax.from ?

The updateParams are stored at the start of the tween. Try passing the sprite instead like this: function tweenSprite(e:MouseEvent):void { TweenLite.to(mySprite, 1, {width:400, height:400, onUpdate:myUpdateFunction, onUpdateParams:[mySprite]}); } function myUpdateFunction(target:Sprite):void { trace("width = " + target.width + " height = " + target.height); }

Setting the blendMode property to LAYER fixes the alpha issue. mc.blendMode = BlendMode.LAYER;

Try this: import com.greensock.easing.Expo; TweenMax.fromTo(mc, 1, {x:0, y:0}, {x:300, y:200, ease:Expo.easeOut});

Are you using the most recent tween classes, because it works for me? package { import org.papervision3d.view.BasicView; import org.papervision3d.objects.primitives.Plane; import org.papervision3d.materials.ColorMaterial; import com.greensock.easing.Linear; import com.greensock.TweenMax; public class Main extends BasicView { public function Main() { super(0, 0, true, false, "FreeCamera"); scene.addChild(new Plane(new ColorMaterial(0x990000))); startRendering(); TweenMax.to(camera, 10, { rotationY:360, repeat:-1, ease:Linear.easeNone} ); } } }

That's because you're making slide a local variable. When you call reverse it has no way of knowing slide exists, so it throws an error. It will work if you define slide outside the move function.

I just created two plugins to achieve the popular typewriter and decoder text effects. They follow the same architecture as the other plugins, and behave just like a tween. Pass a Textfield instance as the target, and a String for the property. Thanks Jack! TextEffect Plugins So for the TypewriterPlugin you would use. import com.greensock.TweenLite; import com.greensock.plugins.TweenPlugin; import com.greensock.plugins.TypewriterPlugin; TweenPlugin.activate([TypewriterPlugin]); TweenLite.to(textField, 0.5, {typewriter:"Lorem Ipsum"}); DecoderTextPlugin: import com.greensock.TweenLite; import com.greensock.plugins.TweenPlugin; import com.greensock.plugins.DecoderTextPlugin; TweenPlugin.activate([DecoderTextPlugin]); TweenLite.to(textField, 0.5, {decoder:"Lorem Ipsum"});

That behavior was changed once TweenCore was introduced in v11. If you want to see the 1009 error , try removing this from the TweenLite constructor: if ($target == null) { return }

The onCompleteAll and onCompleteAllParams are now defined outside the vars object. So you would use them like this: TweenMax.allTo(btnArray, 1, {y:"50", ease:Expo.easeOut}, .1, test, [testParams]);

You can tween relative values by passing a String for the amount. TweenLite.to(mc, 1, {frame:String(-10)});

Remove the () from function name so it doesn't fire right away. Good TweenLite.to(peopleContainer.peopleHdr, .5, {y: (peopleContainer.peopleHdr.y+75), alpha:1, overwrite:3, onComplete: toggleVisibility}); Bad TweenLite.to(peopleContainer.peopleHdr, .5, {y: (peopleContainer.peopleHdr.y+75), alpha:1, overwrite:3, onComplete: toggleVisibility()});

Have you tried using the EaseLookUp.as class? This might work: import com.greensock.easing.EaseLookup; TweenLite.to(mc, 1, {x:100, ease:EaseLookup.find("Expo.easeOut")});

I would just use: TweenLite.delayedCall(1, this.gotoAndPlay, ["myFrame"])

Is the text being anti-aliased, because that requires a decent amount of cpu to process?

Have you tried using the onReverseComplete callback?

You just need to pass the function parameters in an array using the onCompleteParams variable. So it would look like this: TweenMax.to(img01img, 5, {x:0, y:0, onComplete:gotoAndPlay, onCompleteParams:["next"]});

I vote to keep it gs, seems Tweener has managed just fine using caurina.