Comments on: Testing Unity’s Flash Export on a Large Project – Part 1 http://tech.mindcandy.com/2012/02/testing-unitys-flash-export-on-a-large-project-part-1/ jelly beans and computer screens Thu, 06 Dec 2012 01:31:21 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Ovno http://tech.mindcandy.com/2012/02/testing-unitys-flash-export-on-a-large-project-part-1/#comment-380 Ovno Tue, 24 Apr 2012 14:36:41 +0000 http://tech.mindcandy.com/?p=454#comment-380 Just tried this myself and found the best way to rid yourself of some of the more obscure errors was to package each of your scenes and then drop then into an empty project one by one, reduced mine errors from 40 to 2 and actually provided line number information too :)

]]> By: Lucas Meijer http://tech.mindcandy.com/2012/02/testing-unitys-flash-export-on-a-large-project-part-1/#comment-104 Lucas Meijer Mon, 20 Feb 2012 18:12:09 +0000 http://tech.mindcandy.com/?p=454#comment-104 Nice post!

Yoru experiences are quite in line with what we at Unity expect from the current state of the flash exporter. If you start a project with its limitations in mind, you can create great things. If you try to convert an existing project not designed with its limitations in mind, you’re in for a rougher ride.

I expect many of those 87 errors to be easy. Things like specific overloads of methods missing, that can easily be replaced. Swapping out ReadOnlyCollection with a regular one etc.

Others will be much harder. If your game uses a lot of reflection & raknet, you’ll have to somehow work around that.

We’ll make more and more features work out of the box in the months ahead. Posts like this are great to get a feeling for which missing features we should add first. We didn’t expect reflection to come up so often, but it does, so it’s relatively high on our list. On the top right now are WWW and assetbundle support though. (and to preempt your next question: no we do not have an eta on a build yet :) )

Good luck!

Lucas

]]>