PP_GarthJones is correct and PrashantGupta is incorrect. Having an import method for a finished Animate project is one thing, but this update seems to destroy everything else as a trade off. For instance, any possibility of an iterations and updates workflow. Also destroyed is the possibility to import a multiple-level Animate animation as a single .swf asset. I don't necessarily want to import my multi-layer Animate project as anything other than a single compiled asset. Which would be fine if it were an option but presently it is not. Presently, if I publish via the traditional publish method, the animation frames are not included and the .swf imports as a still of the first frame. It is still registering the presence of the frames, because where frames are present, the .swf is truncated to the duration of the frames animation (as apart from single-frame timelines which still import as infinite) but it is not including the motion. So I consider this a bug. This means that, even if I import the whole multilayered .fla project (which I don't want to do because it means creating surplus precomps where that layering is surplus) that I still can't find/replace specific layers, since only the 'import .fla' option retains the actual animation (a buggy inconsistency). So I have to re-import everything to change one thing. Previously, one person could simply update and publish an .swf file, and it would update in AE without the compositor even having to refresh. This was ideal. Entire TV series are produced using the (previous) Animate to AE workflow and they've all been ground to a halt! This update is a disaster, and Adobe have shown once again they have no idea how people are using their product. Until such time as it co-exists with the previous publishing method, we're all going to have to revert to older versions again, for like the 5th time in the history of Animate/Flash usage. Publish to AE worked fine in like 2005 and it also worked fine in previous version, stop breaking it!
... View more