[svn:fx-trunk] 10960: Fixed performance of Wipe effect.

Revision: 10960
Author:   [email protected]
Date:     2009-10-09 13:55:47 -0700 (Fri, 09 Oct 2009)
Log Message:
Fixed performance of Wipe effect. It turns out that micro-tuning the shader code is very important, since that same inner loop runs on every pixel of the bitmap being affected. This change splits the single Wipe shader (with a direction parameter) into four separate Wipe shaders (WipeLeft, etc.), to avoid a switch on the direction parameter. Also, it avoids some setup of pixel values, only bothering to sample the pixel values after it determines which image to sample from. Little stuff, but gained about 20-25% performance on some sample wipe effects.
QE notes: This broke 3 Wipe effects tests because the old WipeEffectInstance class went away. These tests have supposedly been updated by the time this checkin is happening.
Doc notes: No
Bugs: sdk-23279
Reviewer: Corey
Tests run: checkintests, mustella spark/effects
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-23279
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Wipe.as
Added Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeDown.pbj
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeDown.pbk
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeLeft.pbj
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeLeft.pbk
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeRight.pbj
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeRight.pbk
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeUp.pbj
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeUp.pbk
Removed Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Wipe.pbj
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Wipe.pbk
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/WipeInstance.as

Similar Messages

  • [svn:fx-trunk] 12034: Fixes issues in Wipe/CrossFade shaders.

    Revision: 12034
    Revision: 12034
    Author:   [email protected]
    Date:     2009-11-20 02:03:45 -0800 (Fri, 20 Nov 2009)
    Log Message:
    Fixes issues in Wipe/CrossFade shaders. Mostly minor text fixes, like making the kernel names match the file names. Also fixes a syntax error in WipeUp that prevented compilation.
    QE notes: None
    Doc notes: None
    Bugs: sdk-24108
    Reviewer: Corey
    Tests run: checkintests, Mustella spark/effects/Wipe|CrossFade|AnimateShaderTransition
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-24108
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/CrossFade.pbj
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/CrossFade.pbk
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeDown.pbj
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeDown.pbk
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeLeft.pbj
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeLeft.pbk
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeRight.pbj
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeRight.pbk
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeUp.pbj
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeUp.pbk

  • [svn:fx-trunk] 9145: Fixed leak in AnimateTransitionShader effect.

    Revision: 9145
    Author:   [email protected]
    Date:     2009-08-06 11:54:04 -0700 (Thu, 06 Aug 2009)
    Log Message:
    Fixed leak in AnimateTransitionShader effect. We now dispose any BitmapData objects that we create on the fly as part of setting up and playing the effect.
    QE notes: None
    Doc notes: None
    Bugs: SDK-20273
    Reviewer: Corey
    Tests run: checkintests, Mustella (spark/effects/[AnimateShaderTransition|Wipe|CrossFade])
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-20273
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransiti onShaderInstance.as

  • [svn:fx-trunk] 10229: Fixes for some transform effects problems.

    Revision: 10229
    Author:   [email protected]
    Date:     2009-09-14 08:43:43 -0700 (Mon, 14 Sep 2009)
    Log Message:
    Fixes for some transform effects problems.
    - We were not animating the postLayout properties in some cases where we should have, effectively pinning the object in place. We now animate those properties whenever applyChangesPostLayout is true.
    - A copy/paste error meant that we did not animate the scaleZ property in cases where we should have.
    - A problem in the transform code means that using a null transform center is not the same as a transform center which uses the transformX/Y/Z properties of the target object. We now force the creation/use of a transform center in all cases to avoid that problem.
    QE notes: This breaks about a dozen tests in the transform effects area, but I believe the new results are correct and the tests/bitmaps should be changed.
    Doc notes: None
    Bugs: sdk-23177
    Reviewer: Hans
    Tests run: checkintests, Mustella transform effects
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-23177
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransform.as

  • [svn:fx-trunk] 9287: Fixes bug with shader-transition effects ( AnimateTransitionShader, Wipe, and CrossFade) when acting on targets that either have filters or are inside a hierarchy with filters .

    Revision: 9287
    Author:   [email protected]
    Date:     2009-08-13 15:53:43 -0700 (Thu, 13 Aug 2009)
    Log Message:
    Fixes bug with shader-transition effects (AnimateTransitionShader, Wipe, and CrossFade) when acting on targets that either have filters or are inside a hierarchy with filters. Fix was to capture the bitmap snapshot of the target without any of its own filters applied and to then use the ShaderFilter in conjunction with the target's filters during the animation.
    QE notes: Probably need more tests in this area, now that we handle it
    Doc notes: none
    Bugs: sdk-20250
    Reviewer: Jason
    Tests run: Checkintests, Mustella (spark/effects/[AnimateTransitionShader|Wipe|CrossFade])
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-20250
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransitionShader.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransiti onShaderInstance.as

    Lots to be excited about. BUT...Just updated to 8.1 on one of my computers to test it out...
    Sadly, the following issue is NOT fixed for me. Is it with new projects only?  I haven't started a new project on 8.1 I've only opened an old project but the issue that I'm referring to which involves also a delay/freeze of anywhere from a few seconds to a MINUTE while the render bar goes from yellow to red and then back to yellow is still there. Boo.
    On the list above...
    Switching between sequences can turn the render bar red.
    This issue is incredibly easy to replicate. I really do hope it gets fixed. Here are the steps:
    1) Create two sequences with multiple short clips (the more clips the better)
    2) Make sure GPU acceleration is enabled.
    3) Add warp stabilizer to the clips in both sequences. Again, the more clips the longer the delay/freeze will be as the render bar goes from YELLOW to RED and then eventually back to YELLOW again.
    4) Hit SAVE.
    5) Now, toggle between sequences. You'll hit a short delay with a few clips stabilized and a LONG delay with lots stabilized. In my case this delay is around a full minute. The render bar will go from YELLOW to RED and then back to yellow...eventually.
    6) Toggle back to the original sequence and the delay occurs again.
    7) Once you've toggled between sequences and have gone through this delay, that's it, there is no longer a delay...UNTIL...(and here's the big kicker)...until the project is SAVED again. After that the issue returns when you toggle between sequences. Both saving manually and AUTOSAVING cause this issue. No way around it except not editing with GPU acceleration.
    Not sure what the issue is...caching issue when saving maybe? Either way, it stinks and it's still there in 8.1. Big bummer.
    Again, lots to be excited about with this release but I really was hopefully this specific issue was resolved.
    Sigh.

  • [svn:fx-trunk] 11447: Fix to 3 unrelated bugs.

    Revision: 11447
    Author:   [email protected]
    Date:     2009-11-04 16:12:40 -0800 (Wed, 04 Nov 2009)
    Log Message:
    Fix to 3 unrelated bugs.
    - Auto-fading logic was clobbering the state-specified value of alpha in some situations (and the logic was way complex and fragile, so a refactoring was needed).
    - Animation now handles sorting of Resize animations to be processed first in each frame, to improve some of the Resize/transform-effect interaction.
    - Post-layout translation animations were being automatically created in some situations, ignoring any startDelays set on the real translation animations. The fix was to pick up the real translation animation info to pre-populate the post-layout animations.
    QE notes: None
    Doc notes:  None
    Bugs:  sdk-23399, sdk-22563, sdk-24010, sdk-23252
    Reviewer: Kevin
    Tests run: checkintests, Mustella spark/effects
    Is noteworthy for integration: Yes - some fixes requested by Tools
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-23399
        http://bugs.adobe.com/jira/browse/sdk-22563
        http://bugs.adobe.com/jira/browse/sdk-24010
        http://bugs.adobe.com/jira/browse/sdk-23252
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/animation/Animation.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransfor mInstance.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/FadeInstance.as

  • [svn:fx-trunk] 5812: Fixed a bug where direct use of Animation failed because AnimationProperty was not setting up its internal keyframes with correct duration information , so the animation would skip immediately to the end.

    Revision: 5812
    Author: [email protected]
    Date: 2009-03-31 11:34:56 -0700 (Tue, 31 Mar 2009)
    Log Message:
    Fixed a bug where direct use of Animation failed because AnimationProperty was not setting up its internal keyframes with correct duration information, so the animation would skip immediately to the end.
    Bugs: SDK-20356
    QE Notes: spark/effects Mustella tests currently hosed, couldn't run test suite
    Doc Notes: None
    Reviewer: Jason
    Testing: checkintests, Mustella effects tests could not be run (post-rename issues)
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-20356
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/AnimationProperty.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/animation/Animation.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/AnimateColorIns tance.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/AnimateShaderTr ansitionInstance.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/FadeInstance.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/MoveInstance.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/ResizeInstance. as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/Rotate3DInstanc e.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/RotateInstance. as

    Hi
    Can you please try setting up full persmission in the security properties for everyone on the wsconfig folder C:\ColdFusion10\config\wsconfig  and restart ColdFusion Server.
    Swaraj

  • [svn:fx-trunk] 13133: Fix to transform effects to ignore projection on 2D effects.

    Revision: 13133
    Revision: 13133
    Author:   [email protected]
    Date:     2009-12-21 16:02:54 -0800 (Mon, 21 Dec 2009)
    Log Message:
    Fix to transform effects to ignore projection on 2D effects. The prior implementation meant that even 2D effects, like Move, would cause us to set the projection information on a target object's container, even though we were not changing 3D values.
    The fix is to set the default values of the projection properties to false in AnimateTransformInstance. That way, any 3D effect (AnimateTransform3D or its subclasses) would cuase the properties to be set according to the 3D defaults (or values that the developer set them to), whereas any 2D effect would leave the values false, which would result in our ignoring the projection matrix for that effect.
    QE notes: Breaks several AnimateTransform tests in Mustella, but new behavior is correct and tests should be updated (they have been excluded for now)
    Doc notes: None
    Bugs: SDK-24396
    Reviewer: Ely
    Tests run: Checkintests, Mustella sparrk transform effects (AnimateTransform, Move, AnimateTransform3D, etc.)
    Is noteworthy for integration: no
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24396
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransfor mInstance.as

    I had downloaded it for test, and requested for evaluation license...
    But I haven't got license, and also I am not able to find Flash Builder Plugins from HFCD site....
    I think those plugins are removed from site....
    Please help me, if anyone have those plugins...

  • [svn:fx-trunk] 5473: Fix for bug around handling of constraints during and after effects were run , both for old and new effects.

    Revision: 5473
    Author: [email protected]
    Date: 2009-03-20 16:02:58 -0700 (Fri, 20 Mar 2009)
    Log Message:
    Fix for bug around handling of constraints during and after effects were run, both for old and new effects. Fix was to correctly record and handle styles that were set or not set in either state and to temporarily set width/height values for the duration of an effect if we disabled the relevant styles that affect width/height.
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-17809
    Reviewer: Jason
    Testing: checkintests, Mustella Effects, ListDataEffects
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17809
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateInstance.a s
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.as

    Revision: 5473
    Author: [email protected]
    Date: 2009-03-20 16:02:58 -0700 (Fri, 20 Mar 2009)
    Log Message:
    Fix for bug around handling of constraints during and after effects were run, both for old and new effects. Fix was to correctly record and handle styles that were set or not set in either state and to temporarily set width/height values for the duration of an effect if we disabled the relevant styles that affect width/height.
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-17809
    Reviewer: Jason
    Testing: checkintests, Mustella Effects, ListDataEffects
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-17809
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateInstance.a s
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.as

  • [svn:fx-trunk] 13317: Fix to allow Animate to automatically handle changes in styles during transitions .

    Revision: 13317
    Revision: 13317
    Author:   [email protected]
    Date:     2010-01-06 16:19:04 -0800 (Wed, 06 Jan 2010)
    Log Message:
    Fix to allow Animate to automatically handle changes in styles during transitions. This same logic already works for properties (e.g., if you specify different values for x in states and run Animate with a SimpleMotionPath with property="x" then it will automatically determine the from/to values to animate for x). But we needed to add an override for getRelevantStyles() for Animate to advertise the possible styles to pick up changes for so that the transitions array would be populated accordingly.
    QE notes: None
    Doc notes: This is a fix that should allow the second animated skin example in the docs (spark_skinning, p46) to work as detailed in my edits
    Bugs: sdk-24932
    Reviewer: Jason
    Tests run: checkintests, Mustella spark/effects
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-24932
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Animate.as

    FYI - This regression has been filed here: http://bugs.adobe.com/jira/browse/SDK-31989

  • [svn:fx-trunk] 8883: Fixes RTE seeking into Sequences.

    Revision: 8883
    Author:   [email protected]
    Date:     2009-07-28 16:05:56 -0700 (Tue, 28 Jul 2009)
    Log Message:
    Fixes RTE seeking into Sequences. Seeking (setting playheadTime) to or past the end of the Sequence would not properly end the effect and would set it up for failure on future playing.
    QE notes: None
    Doc notes: None
    Bugs: sdk-22367
    Reviewer: Jason     
    Tests run: checkintests, Mustella (spark/effects, mx/effects/Sequence)
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-22367
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/effectClasses/SequenceInstanc e.as

  • [svn:fx-trunk] 10131: Fixes to several effects bugs and one styles-related bug.

    Revision: 10131
    Author:   [email protected]
    Date:     2009-09-10 14:25:42 -0700 (Thu, 10 Sep 2009)
    Log Message:
    Fixes to several effects bugs and one styles-related bug.
    QE notes: Fixes to all filed auto-center feature bugs.
    Doc notes: None
    Bugs: sdk-22994, sdk-22992, sdk-22990, sdk-21850, sdk-22973
    Reviewer: Jason (+Glenn for RadioButton/CheckBox changes, 21850)
    Tests run: checkintests, Mustella (transform effects, Slider, DataGrid - all passed last week, prior to skin/test changes)
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-22994
        http://bugs.adobe.com/jira/browse/sdk-22992
        http://bugs.adobe.com/jira/browse/sdk-22990
        http://bugs.adobe.com/jira/browse/sdk-21850
        http://bugs.adobe.com/jira/browse/sdk-22973
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/CheckBox.as
        flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/RadioButton.as
        flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
        flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/effectClasses/SoundEffectInst ance.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransform.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Move.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Move3D.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Rotate.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Rotate3D.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Scale.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Scale3D.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransfor mInstance.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/GraphicEleme nt.as
        flex/sdk/trunk/tools/dependencychecker/frameworkSwcExceptionsList.txt

  • [svn:fx-trunk] 10135: Fix to effects' transform center functionality.

    Revision: 10135
    Author:   [email protected]
    Date:     2009-09-10 15:38:22 -0700 (Thu, 10 Sep 2009)
    Log Message:
    Fix to effects' transform center functionality. When autoCenterTransform=false, should default to the transformX/Y/Z specified in the target object. We were instead defaulting to a default Vector3D(), which is like having transfomrXYZ at (0,0,0). one-liner fix to initialize the default transform center with the target's transformXYZ values.
    Also fixed unrelated typo in UIComponent asdocs.
    QE notes: None
    Doc notes: None
    Bugs: sdk-21766
    Reviewer: Jason
    Tests run: checkintests, Mustella transform effects
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-21766
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransfor mInstance.as

    I had downloaded it for test, and requested for evaluation license...
    But I haven't got license, and also I am not able to find Flash Builder Plugins from HFCD site....
    I think those plugins are removed from site....
    Please help me, if anyone have those plugins...

  • [svn:fx-trunk] 12978: Fix for possible null deref in Effect. captureMoreStartValues().

    Revision: 12978
    Revision: 12978
    Author:   [email protected]
    Date:     2009-12-15 17:12:29 -0800 (Tue, 15 Dec 2009)
    Log Message:
    Fix for possible null deref in Effect.captureMoreStartValues(). Seems unlikely to ever occur since the function is not really there for random calling outside of data effects, but the fix was simple.
    QE notes: none
    Doc notes: none
    Bugs: sdk-16451
    Reviewer: Jason
    Tests run: checkintests, Mustella mx/effects, mx/ListDataEffects
    Is noteworthy for integration: no
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-16451
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.as

  • [svn:fx-trunk] 7891: Fixed bug in effects  that was fallout from renaming offsets property to postLayoutTransformOffsets .

    Revision: 7891
    Author:   [email protected]
    Date:     2009-06-16 13:38:37 -0700 (Tue, 16 Jun 2009)
    Log Message:
    Fixed bug in effects  that was fallout from renaming offsets property to postLayoutTransformOffsets.
    QE Notes: none
    Doc Notes: None
    Bugs: SDK-21839
    Reviewer: Evtim
    Tests: checkintests
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21839
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/AnimateTransfor mInstance.as

    Lots to be excited about. BUT...Just updated to 8.1 on one of my computers to test it out...
    Sadly, the following issue is NOT fixed for me. Is it with new projects only?  I haven't started a new project on 8.1 I've only opened an old project but the issue that I'm referring to which involves also a delay/freeze of anywhere from a few seconds to a MINUTE while the render bar goes from yellow to red and then back to yellow is still there. Boo.
    On the list above...
    Switching between sequences can turn the render bar red.
    This issue is incredibly easy to replicate. I really do hope it gets fixed. Here are the steps:
    1) Create two sequences with multiple short clips (the more clips the better)
    2) Make sure GPU acceleration is enabled.
    3) Add warp stabilizer to the clips in both sequences. Again, the more clips the longer the delay/freeze will be as the render bar goes from YELLOW to RED and then eventually back to YELLOW again.
    4) Hit SAVE.
    5) Now, toggle between sequences. You'll hit a short delay with a few clips stabilized and a LONG delay with lots stabilized. In my case this delay is around a full minute. The render bar will go from YELLOW to RED and then back to yellow...eventually.
    6) Toggle back to the original sequence and the delay occurs again.
    7) Once you've toggled between sequences and have gone through this delay, that's it, there is no longer a delay...UNTIL...(and here's the big kicker)...until the project is SAVED again. After that the issue returns when you toggle between sequences. Both saving manually and AUTOSAVING cause this issue. No way around it except not editing with GPU acceleration.
    Not sure what the issue is...caching issue when saving maybe? Either way, it stinks and it's still there in 8.1. Big bummer.
    Again, lots to be excited about with this release but I really was hopefully this specific issue was resolved.
    Sigh.

Maybe you are looking for