the parser automatically loads the url, which is after export standard to
"images/"
there is a setter for a custom path: pathToSources
You also can pass init object, and you like for any other model are able to set
othe rmaterials as you wish after its being parsed.
> or should I look at patching the parser myself?
Any improvement is welcome!
the result is exact same as any other format, what is generated comes out same
in flash.
the awd doesn't have dynamic properties. Its for now, holding only what you
need for a static model in Away.
Drop a model in Prefab, export as awd and drop awd back again on Prefab, you
will see.
Fabrice
On Jan 20, 2010, at 10:08 PM, Joshua Granick wrote:
> I'm used to embedding Collada models like this:
>
> var object:Object3D = Collada.parse (ObjectMesh, { material: ObjectMaterial }
> );
>
>
> Simple, easy, but the AWData parser doesn't seem to support a material in the
> init properties. Is there any other way to embed and include a material with
> my model (especially without using an explicit material name), or should I
> look at patching the parser myself?
>
> Also, does the end result of the AWData parser resemble the same as the
> Collada parser, or does it turn out better, or with more available options
> (like primitive objects)?
>
> Thank you!
