yes, as said multiple times, we'll supply a parser for collada with 1.4 specs.
no eta for now, as more important stuff needs to be solved/done before that.

Even if collada is a very bad format for runtime, it is a widely spreaded 
format that we need to support. And we will.

for now indeed use ac, obj, awd1, 3ds or obj. Md5/md2 if bones/vertex anim is 
required for your tests.

Fabrice
 
On Mar 25, 2011, at 4:41 PM, Dave wrote:

> The collada parser included in the Away3D 4.0 alpha original zip that
> they released included a Collada parser, but it only did polylists,
> and no other kind of geometry.  It also didn't do materials or
> anything.  At some point recently in the SVN repo, they simply
> commented it out - that pretty much says to me that it isn't supported
> at the moment.  This is fine.  I'm actually longer term more
> interested in a compact data format (AWD2 seems to be the goal).
> Supporting Collada at runtime for a shipping product is crazy.
> Supporting Collada for quick prototyping is not.
> 
> Several of us are separately working on collada parsers - I'm putting
> together mine using ASCollada (the newer one from github - the one
> that came with Papervision is a bit old).
> 
> It might be interesting to see if the Away3D team wants to integrate
> one of these when they are "done" (if they ever are - Collada is
> ridiculously overly complex).
> 
> -Dave
> 
> On Mar 25, 5:29 am, Apprentice <[email protected]> wrote:
>> I had the same problem. On inspection I noticed it was the initHandle
>> is called and which should be implemented in the Collada parser but
>> it's currently commented. Hence code executes the initHandle in
>> ParserBase which throws an exception as it's always supposed to be
>> implemented by a derived class. I tried uncommenting the code in the
>> Collada parser, but this leads to other types of errors. I guess
>> they've temporarily disabled it... Would have been nice if they threw
>> another error like "Collada parser (temporarily?) disabled" though.
>> 
>> On 25 mrt, 12:58, Jahiro <[email protected]> wrote:
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>> Hi Guys,
>> 
>>> I'd like to reference the names of my models, and since OBJ srtips out
>>> names, I need to export Collada from Maya - however, the Broomstick
>>> Collada parser is throwing errors - I noticed there's no Collada Demo
>>> - is the Parser still under contruction?
>> 
>>> I'm calling this to
>> 
>>> container =
>>> ObjectContainer3D(ResourceManager.instance.getResource("myCollada.dae"));
>> 
>>> It results in a RTE:
>> 
>>> Error: An abstract method was called! Either an instance of an
>>> abstract class was created, or an abstract method was not overridden
>>> by the subclass.
>>>         at away3d.loading.parsers::ParserBase/initHandle()[C:\Users\jahiro
>>> \Projects\myProject\myProject-dependencies\flash\Away3D\branches
>>> \molehill\src\away3d\loading\parsers\ParserBase.as:242]
>>>         at away3d.loading.parsers::ParserBase()[C:\Users\jahiro\Projects
>>> \myProject\myProject-dependencies\flash\Away3D\branches\molehill\src
>>> \away3d\loading\parsers\ParserBase.as:84]
>>>         at away3d.loading.parsers::ColladaParser()[C:\Users\jahiro\Projects
>>> \myProject\myProject-dependencies\flash\Away3D\branches\molehill\src
>>> \away3d\loading\parsers\ColladaParser.as:37]
>> 
>>> Happy to create a ticket if you'd like - just thought I'd check first.
>> 
>>> Cheers
>>> -Jahiro

Reply via email to