OT: Flash Professional CC is now live!

Hi Nipun, Any chance of getting the bandwidth profiler back?

Alexanderflash: try Anime Studio Pro instead for your animation. It exports to swf if needed. I've switched ages ago to AS Pro from Flash for my animation needs.

The timeline offers a proper motion graph curve editor, and is many, many times more powerful and convenient to use than the motion editor in Flash ever was.

The inverse kinematics and bones system is comparable to 3d applications like Maya, but geared towards quick 2d character setups. Smart bones are available for quick secondary animation like tails. Controller bone systems can be setup for easy facial expression controls, poses and actions can be set, and much, much more. There is just no comparison to the old Flash bones system.

Quick layer switching is also implemented.

A real 2.5d camera is supported which allows you to fly through your scene in true 3d easily.

It's brilliant for 2d/2.5d animation, and you owe it to yourself to check it out!

You may want to wait for Christmas time - Smith Micro usually does special deals around that time, and it can save you some money.

Some examples made with Anime Studio Pro:

https://www.youtube.com/watch?v=Dg9FG4MubQY&hq_e=el&hq_m=1253325&hq_l=14&hq_v=36e2f0ebb1  (also Poser used in this production)

http://anime.smithmicro.com/videos/murklorpurklor.html

The only caveat is their trial policy - you must enter a credit card to download the trial, I believe. Not so good - the software is brilliant, though.

I wonder how Adobe makes these choices to just "throw out stuff" which a lot of users (paying clients!) seem to use...

The good thing is that they can put things back in now since the cloud stuff.

For animation just stay with Flash CS6 instead. I don´t see any reason to switch to CC for that. Dragon Bones as an extensipn to CC does have some kind of bones but is not really a replacement for bone tool.

BUG - in flash pro CC, 'bold' and 'italic' properties of TextFormat have no effect on the rendered text

Concise problem statement:

If you compile with flash pro CC, and use the 'setTextFormat' method of a TextField, the 'bold' and 'italic' properties of the TextFormat argument have no effect on the rendered text. If you compile with flash pro CS6, the 'bold' and 'italic' properties work as expected.

Apparently, with flash pro CC, the only way to make the text render correctly is to change the font name (add the suffix ' Bold', ' Italic', or ' Bold Italic'.) This means code which dynamically changes font styles only works in CS6 or CC, but not both. For example, if you use the 'bold' property the text renders bold in CS6 and regular in CC, whereas if you change the font name to add the suffix ' Bold', the text renders bold in CC and DOES NOT RENDER at all in CS6. This makes it difficult to transition a team from CS6 to CC.

Steps to reproduce bug:

1. Create an xfl with 2 TextFields on the stage, both with font "Trebuchet MS" and style "regular", one named boldTrueText containing the String "bold = true", one named fontNameText containing the String "fontName = Trebuchet MS Bold". Create 2 more TextFields on the stage for visual reference, both with font "Trebuchet MS", one with style "regular", one with style "bold".

2. Add the following code to the Actions panel on frame 1:

import flash.text.TextFormat;

import flash.text.Font;

var format:TextFormat = boldTrueText.getTextFormat();

format.bold = true;

boldTrueText.setTextFormat(format);

format = fontNameText.getTextFormat();

format.font = "Trebuchet MS Bold";

fontNameText.setTextFormat(format);

var fonts:Array = Font.enumerateFonts(), count:int = fonts.length;

for (var i:int = 0; i < count; i++) {

    var font:Font = fonts;

    trace("fontName: " + font.fontName + ", fontStyle: " + font.fontStyle);

}

3. Save, and compile with flash pro CS6 and flash pro CC.

Results:

With flash pro CS6, "bold = true" renders bold, and "fontName = Trebuchet MS Bold" DOES NOT RENDER.

With flash pro CS6, the following is traced:

fontName: Trebuchet MS, fontStyle: bold

fontName: Trebuchet MS, fontStyle: regular

With flash pro CC, "bold = true" renders regular, and "fontName = Trebuchet MS Bold" renders bold.

With flash pro CC, the following is traced:

fontName: Trebuchet MS, fontStyle: regular

fontName: Trebuchet MS Bold, fontStyle: bold

Expected results:

The same text is rendered in both flash pro CS6 and CC. I don't know why this behavior was changed in flash pro CC - it causes silent failures in code which dynamically changes font styles. I expected the flash pro CS6 behavior to remain the same in CC, like so:

With flash pro CC, "bold = true" renders bold, and "fontName = Trebuchet MS Bold" DOES NOT RENDER.

With flash pro CC, the following is traced:

fontName: Trebuchet MS, fontStyle: bold

fontName: Trebuchet MS, fontStyle: regular

If you don't want to break backward compatibility (any further), you could make both the behaviors work in flash pro CC, like so:

With flash pro CC, "bold = true" renders bold (font is still "Trebuchet MS"), and "fontName = Trebuchet MS Bold" renders bold also.

With flash pro CC, the following is traced:

fontName: Trebuchet MS, fontStyle: bold

fontName: Trebuchet MS, fontStyle: regular

fontName: Trebuchet MS Bold, fontStyle: bold

I submitted this bug with the bug form, and also with adobe bugbase (in case it isn't obsolete) - I'm just trying to maximize my chances of getting a fix.  Has anyone else encountered this bug?

feature request - authortime sharing

I notice authortime sharing was removed from flash pro CC. This is the only missing feature holding back my company from upgrading to the newest version of flash pro. I understand adobe bases decisions on the aggregate, but I figured I'd get my request in and hope there are enough similar requests. I started a new thread, and a response pointed me to the feature request form (which I submitted), but another response left me doubtful of the form's relevance.

http://forums.adobe.com/message/5520896

Authortime sharing is the glue that holds our asset pipeline together, and we're very disappointed to see the Authortime Sharing section has been removed from the Symbol Properties dialog box. To be clear, we do NOT use flash pro projects. We only use the ability to share a symbol from a source file (and the "Update automatically" checkbox.)

Any of the artists can make changes in one of the "shared assets" xfls, and those changes will automatically propagate to the production xfls which use those assets before they are compiled (in fact, as soon as they are opened - we use the "Update automatically" checkbox.) It's a huge waste of time (and error-prone) to manually copy over assets from one of the "shared assets" xfls to each production xfl that uses the assets, every time an artist makes a small change.

We thought about using runtime shared libraries for the shared assets, but concluded authortime sharing is better, for 2 main reasons.  First, the artists find it indispensable to be able to preview and work with the shared assets within the production xfls. Second, since the shared assets are compiled into the production swfs, only the 1 swf file needs to be loaded by visitors to our site; we've found that each additional asset load has some small chance of failure. It's quite odd runtime shared libraries were included in flash pro CC, but not authortime sharing.

I hope adobe adds this crucial feature back, or we'll be stuck with CS6, and we really do like the much faster, more responsive experience of CC. I'm curious what gave them the impression authortime sharing is not an important feature. It seems like they're serious about the future of flash pro, and authortime sharing is necessary to use it in our production pipeline. Does anyone else use this feature? Does anyone else know how to get through to adobe with this kind of feedback?

Hi Adam and others! I just saw that Ajar made this free extension for Flash CChttp://ajarproductions.com/blog/2013/07/03/transferring-tween-eases-to-flash-pro-cc/

"EaseCaddy lets you save, apply, export, and import custom eases (which make animations beautiful and believable)."

It may help some! And hopefully more extensions will come for the missing CC features.

I miss the main tools panel with a one-click icon to save, since autosave is removed too. Quite cumbersome while drawing to either click file-> save or to use keyboard shortcuts for me. I seem to use CS6 90% of the time still allthough I quite like CC too much to change there, but hopefully solutions will turn up.

for our "focus", can´t we decide our focus ourselfes?

Totally agree We should be able to activate or no these features ourselves. It is regrettable to remove major features without consulting customers who use them every day, especially when these features were presented as important developments in last 2 or 3 versions of Flash and are now in the most recent projects.

Please everyone, ask Adobe to put these old features in Flash on this page. If they don't listen to us, many of us will stop our subscription and stay on CS6.

For me, object-level undo, support for AS2 (for old projects), TLF text and SWC imports are very important features that I miss.