Publishing

1. Install the Unity Developer Preview and activate if you are using Unity for the first time.
2. Put something in your scene (GameObject->Create->Box)
3. Open the Build Settings window (File->Build Settings...)
4. Select Flash Player as target platform.
5. Click the Build And Run button.

If you start with an empty project, you’ll have a great time.

If you want to take an existing unity project and “bring it to flash”, you should expect to make changes to your script code. As we improve the exporter, the required modifications will become smaller and smaller. That said, the Angrybots project that you get when you install the Developer Preview runs out of the box, just like for other supported platforms.

Supported

• Lightmapping
• Occlusion culling
• Basic scripting
• Editor scripting (JavaScript / C# / Boo). Note: for JavaScript, use #pragma strict.
• Custom shaders
• Animation / skinning
• Basic audio features, such as AudioSource / AudioListener
• Physics
• Navigation meshes
• Baked substance textures
• PlayerPrefs
• UnityGUI, except for text input
• Realtime shadows

Limited support - features with potential issues

• Image Effects. Some work, some don’t.
• Not all parts of .NET scripting work (lambda expressions and LINQ aren’t supported, for example)
• GUIText will have a dramatic impact on performance
• The new Particle System (Shuriken) works, but scripts that use the Shuriken API will fail to convert to flash

Not supported

• Unity profiler
• Asset bundles
• Text input in UnityGUI
• WWW classes. Note that you can write your own ActionScript that uses Adobe networking APIs.
• Raknet networking (if you need networking, you can write it in Action Script 3 directly, using flash API)
• Terrain
• Cloth
• Using VertexLit shaders in combination with:
  - Specular highlights
  - Spot lights
  - Emissive material color
• Advanced audio features, such as audio effects. Also pitch manipulation is not supported.
• Deferred rendering
• AnimationEvents that carry arguments

You can use Debug.Log() to print messages to the logfile. The logfile is also a good source of information about potential errors if you’re using features that don’t work yet. You can get a logfile like this:

• Install "content debugger" version of the Adobe Flash Player plugin from: http://www.adobe.com/support/flashplayer/downloads.html
• Go to http://flashplayerversion.com/, and make sure that it says 'Debugger: Yes'
• Do not use Chrome. (It ships with its own flashplayer)
• Create a file called mm.cfg which will instruct the Flash Player to create a logfile. mm.cfg file needs to be placed here:

OSX	/Library/Application Support/Macromedia/mm.cfg
XP	C:\Documents and Settings\username\mm.cfg
Windows Vista	C:\Users\username\mm.cfg
Win7	C:\Users\username\mm.cfg
Linux	/home/username/mm.cfg

• Write this text in the mm.cfg file:
  ErrorReportingEnable=1
  TraceOutputFileEnable=1
• Find and open your flashlog.txt here:

Macintosh OS X	/Users/username/Library/Preferences/Macromedia/Flash Player/Logs/
XP	C:\Documents and Settings\username\Application Data\Macromedia\Flash Player\Logs
Windows Vista/Win7	C:\Users\username\AppData\Roaming\Macromedia\Flash Player\Logs
Linux	/home/username/.macromedia/Flash_Player/Logs

Note that whilst your content is running, this flashlog.txt will constantly be updated as new debug messages are generated by your script code. You may need to reload the file or use an editor that can reload as the file grows in size.

More details about enabling debug logs when using SWFs is available at: http://livedocs.adobe.com/flex/3/html/help.html?content=logging_04.html

• Mouse input in can be laggy on Chrome in MacOS X 10.6.8

"Failed assemblies stripper ... Unhandled Exception: Mono.Linker.ResolutionException: Can not resolve reference: System.String UnityEngine.WWW::get_text()"

This means that you have a precompiled dll in your project that was not built with flash support in mind and references classes that Unity Flash does not support (such as the WWW class).

'TerrainCollider' is not supported when building for FlashPlayer. 'TerrainData' is not supported when building for FlashPlayer. Asset: 'Assets/New Terrain.asset'

The terrain feature is not supported when building for the Flash Player target. All un-supported features will generate a similar warning. Note that the build will continue, however, the unsupported feature will be missing from the final SWF.

Error building Player: UnauthorizedAccessException: Access to the path "Temp/StagingArea/Data/ConvertedDotNetCode/global" is denied.

This means your generated ActionScript file is open in an editor, and Unity cannot overwrite it. To fix this, close the ActionScript file.