Adobe Creative Cloud

Digital Video & Audio

After Effects CC 2015 (13.6.1) bug-fix update available: fixes stale image cache and more

The After Effects CC 2015 (13.6.1) bug-fix update is now available. This update fixes multiple bugs, including a bug that caused After Effects to not update the preview image in the Composition panel, which happened most commonly after using Undo.

You can install the update through the Creative Cloud desktop application, or you can check for new updates from within any Adobe application by choosing Help > Updates.

For details of what was added, changed, and fixed in After Effects CC 2015 (13.6), see this page. For details of all of the other updates for Adobe professional video and audio applications, see this page.

Please, if you want to ask questions about this update, come on over to the After Effects user-to-user forum, rather than leaving comments on this blog post. (It’s much harder to have conversations in the comments of a blog post.) If you’d like to submit feature requests or bug reports, you can do so here.

The After Effects team is continuing to investigate other bugs for future updates. Please refer to this article for current information about known issues.


tell us what we should work on next


The After Effects team is currently planning our releases for the upcoming year, which will focus on quality and performance. We would like to hear from you about what specific areas we should work on next.

Please fill out a short survey, which will help us learn what you consider most important to the development of After Effects. We appreciate you taking the time to do this.


bug fixes in After Effects CC 2015 (13.6.1)


The After Effects CC 2015 (13.6.1) bug-fix update addresses these significant bugs:

  • The preview image in the Composition panel no longer fails to update in certain cases after you make a change to the composition. This fix prevents After Effects from putting the image cache into a bad state, which most commonly occurred on Windows after using Undo, but could also occur after other changes once the project had entered the bad state.
  • Previewing a composition with audio will no longer fail to start when a layer has an audio effect with an expression, and display an error: Effect cannot use “abort” callback when called with “unrecognized plug-in effect command” command. ( 25 :: 19 )
  • Viewer panels (Composition, Layer, Footage) no longer show downsampling artifacts when the viewer zoom is set to 50% zoom, the viewer resolution is set to Full, and the Hardware Accelerate Composition, Layer, and Footage Panels option is enabled in Preferences > Display.
  • After Effects no longer fails to start on computers with older processors lacking a specific instruction set (e.g., AMD Phenom II and Athlon processors). The error message given for this specific issue was “The application was unable to start correctly (0xc000001d)” or “The application was unable to start correctly (0xc0000142)”. Note: A similar issue affects Premiere Pro CC 2015 (9.1), for which the fix is somewhat more involved. An upcoming Premiere Pro update is intended to address this issue. Thank you for your patience.
  • After Effects no longer generates the wrong image for layers using some plug-ins in 16-bpc or 32-bpc (bits per channel) color mode. Affected plug-ins included Digital Film Tools Film Stocks and Digital Anarchy plug-ins.
  • Creative Cloud account names that use non-ASCII characters (e.g., Japanese and Chinese characters) no longer cause an error “could not convert Unicode characters” when you start After Effects.
After Effects, General, Region of Interest

Join the discussion

  • By ProDesignTools - 8:16 PM on December 17, 2015  

    Thanks, appreciate the fixes. As an aside, would it be possible to clarify the After Effects versioning scheme?

    Wondering why this AE 13.6.1 update is called the “CC 2015.1 Release” (under the app’s “About” screen), rather than CC 2015.1.1 – and why the November 30th update (AE 13.6) wasn’t called the CC 2015.1 release instead?

    The AE naming convention got a little confusing with the use of app version 13.5 instead of 14.0 for the original CC 2015.0 release – and now this muddies it up a bit more…

    (It seems odd that Premiere will change its file format for a dot release, while the version numbering for After Effects goes to great lengths in the opposite direction!)

    Thanks again.

    • By Tim Kurkoski - 10:04 AM on December 18, 2015  

      There are multiple questions here. Let’s take them one by one:

      > Wondering why this AE 13.6.1 update is called the “CC 2015.1 Release” (under the app’s “About” screen), rather than CC 2015.1.1 – and why the November 30th update (AE 13.6) wasn’t called the CC 2015.1 release instead?

      That After Effects 13.6 was not labeled “CC 2015.1” was actually a bug; we missed incremented that label.

      We generally don’t increment the year-based branding for bug-fix updates like this one, so “2015.1.1” wouldn’t be relevant.

      > The AE naming convention got a little confusing with the use of app version 13.5 instead of 14.0 for the original CC 2015.0 release

      We recognize the incongruity, but there’s logic behind it.

      The After Effects team prefers to coincide project file format changes with major version numbers (X.0’s). We chose explicitly to not increment the project file format version in After Effects 13.5, so we did not increment the application version. This keeps After Effects 13.5 projects compatible with After Effects 13.2.

      > (It seems odd that Premiere will change its file format for a dot release, while the version numbering for After Effects goes to great lengths in the opposite direction!)

      Incrementing the file format gives the Premiere Pro team a bit more freedom in how they store project data when adding features or fixing bugs. For the After Effects team, more work is required to protect the project data and to test that it maintains compatibility. Two approaches to the problem.

  • By ProDesignTools - 3:10 PM on December 18, 2015  

    Hey Tim, thanks so much for the clarifications and explanations – really appreciate it!

    So bottom line on the year-based release numbering in this case: It sounds like the November AE update *should* have been called “CC 2015.1” – but also this latest one as well?

    In other words, both the Nov. 30th update and the Dec. 17th update have the same CC 2015.1 release number, and are distinguished only by their particular AE app version 13.6 vs. 13.6.1 – is that right?

    Thanks again.