If you compile, does FD fires errors? If yes what are these?
You are compiling ok: do you view the swf in html? is your html ready for flash 11.3? having the vmode direct set, right player version?
You view the result in SA flash player: is it the right version? If you try to open flash 11.3 files with SA 10, it gives a nice white screen and no errors.
Now assuming you’re all set, swf compiles just fine and html is ok.
Prefab exports for you a project file (PrefabProject.as), and a set of classes representing the objects that you want to display.
The project file is there to help you. Meaning that if you run it, it will display the exported objects. This class is made just to quick test or show you how you can use Prefab exports. You can do so much in f11 that it would make no sens to attempt to export a fully structured project. Hence the minimalist, tutorial like purpose of the “PrefabProject.as”.
The outputs should run if you use either master or release branch, both available on github page.
If you have applied methods or export a generic ASbase class, and you run them using “master” you will likely get an error that it doesn’t find “EffectMethodBase”. fix: find and replace by “ShadingMethodBase”. If you run release it will be just fine.
if you export vertex animation to as3, it will fail in release.
The problem is that atm, it is impossible for me to release an update that is fully compatible with both. master is beta, and release, evolving dayly, is to become away gold (official 4.0) somewhere around the 17 of july.
I have an update in the making that will be released sync with the away3D 4.0 release. So during 2 weeks (one left to go) Prefab outputs cannot be garantied to work seamlessly. With the update 2.117, all AS3’s will be 4.0 compatible and will no longer reflect beta. You will have by then to update your version to latest in order to run 4.0 with Prefab >=2.117 outputs.