Flash Decompiler Trillix for Mac Known issues, FLA format limitations

Once a FLA file is compiled into SWF, most of the information about its internal structure and objects order is lost. As the result, SWF file size is greatly decreased which is a big advantage for the web usage.

On the other hand, restoring original FLA file from SWF could be a problem. Situation may be worsened by many third-party Flash editing products that do not follow Adobe Flash specifications and introduce their own standards.

We are working to reduce the number of conversion errors to the minimum; however, it is not always possible. We hope you understand that and will help and cooperate with us. You are very welcome to send erroneously converted files to our Support Team for investigation.

Below is the list of known situations that are likely to lead to conversion problems, but are not applicable reasons for refund:

  1. SWF file is compressed, optimized or obfuscated by third-party applications.
  2. SWF file doesn’t satisfy Adobe SWF File Format Specification.
  3. Files, compressed with algorithms other than ZLib compression, may lead to erroneous conversion.
  4. Texts objects contain symbols of a national (localized) alphabet. Learn how to solve problems with text conversion.
  5. SWF file may contain font, which is not installed in your system. In this case Flash will ask for a replacement when you open a converted FLA. Otherwise, please, enable conversion of texts into shapes.
  6. FLA format allows placing as many objects on one layer as you want. However, SWF has a limitation of one object only. So objects will be placed into separate layers when converting SWF into FLA.
  7. If SWF file does not contain a character map, then Texts objects parsing will lead to the following erroneous texts: “??????”.
  8. When decompiling a Motion Tween, you might need to experiment with “Motion tween” settings.
  9. Some Shape objects that have non-standard fills could be parsed incorrectly. The non-standard fill is the one that is present within a non-closed area that has gaps along its contour. Most likely it was created by a third-party application.
  10. Usually Morph shapes have beginning and ending states. When placing a morph shape on a frame its intermediate state is used. It means that morph shape can be rewound/forwarded into any of its states in SWF. However, it is not possible within FLA format. Morph shapes are placed on the timeline and always run from their beginning state to the ending one.
  11. When you compile your FLA file into SWF the first time, the hierarchy of the layers gets deformed. This peculiarity is important only for Morphs. When a morph is placed on a frame its state is remarked and written. It leads to the problem when a series of morphs can be “split” into several layers. Such frames cannot be correctly converted into FLA at this stage.
  12. Action buttons in FLA file are set when you place them on frames. In SWF files actions are stored in buttons themselves, that’s why each button will be represented as a separate instance in FLA, even if they differ in ActionScript only.
  13. We do not decompile captivate projectors (EXE), projectors not created in Adobe Flash.
  14. Sounds with “Nellymoser Asao” codec cannot be extracted properly.
  15. Some problems may occur while converting video with “On2 Truemotion VP6 bistream (with alpha)” to FLA format.
  16. In some cases video which is extracted to AVI format can be played incorrectly.
  17. When the original FLA file is published into SWF format, all the original scenes are joined into one scene. Almost no information is transferred to the output SWF file about the original scenes. This information is almost impossible to retrieve. That is the reason why the output FLA file, decompiled from the SWF file, has only one scene. This fact won’t influence the SWF file functionality after it is published from FLA.
  18. Code (in AS 3.0), written into timeline and movie clips, is placed into separate AS classes by Adobe Flash when published into SWF. In most cases it doesn’t cause any problems. But sometimes the original file developer may give such sprite a name (in Linkage settings, Class field) which will be treated incorrectly by AS (e.g., a name starting from a digit or a name equal to AS keyword). Adobe Flash doesn’t check the name, so there will be no problems during compilation. But during republishing after conversion, AS compiler checks the name and may give error message.Such files need to be corrected manually: one should move the code from functions like “public function frame1()” to the corresponding frame on movie clip timeline, and then delete these AS files.
  19. Flash Decompiler does not support Flex modules, dynamically loadable SWF files.
  20. Text Layout Framework (TLF) texts are not currently supported by Flash Decompiler. Also, Flash files are still converted into FLA binary file format, not into XML-based FLA file (XFL) format.
  21. Adobe AIR applications are currently not supported.
  22. Currently Flash Decompiler Trillix does not support Flex Mobile Projects.