I have enabled all parsers, but it show me error .

Error: No parser defined. To enable all parsers for auto-detection, use Parsers.enableAllBundled()
at away3d.loaders.misc::AssetLoaderToken/onLoaderEvent()[E:workghostRider2gitsony-ghostrider2gameprototype-v3libaway3dloadersmiscAssetLoaderToken.as:81]
at flash.events::EventDispatcher/dispatchEventFunction()

Can you show us the code when you load the mesh?

Are you embedding the md5 file or loading it from an external source?

I’m having a similar problem.

I’m trying to load a sequence of obj files.
So I’m loading them from an xml.
It doesn’t seem the Embed code like in the Basic_LoadObj example would be practical.

But when i pas the loader the path to the file(s) i get:

Error: No parser defined. To enable all parsers for auto-detection, use Parsers.enableAllBundled()

While the code states, just before it produces this error,

Parsers.enableAllBundled() already.
Anyone who can point me in the right direction?

It’s up to each file-type parser to identify whether they recognize a file or not. If no parser claims it, this error would occur. Does your OBJ file have a file suffix that is “obj”? Is there an MTL file?

It would be great if you could file a bug on GitHub and upload your OBJ/MTL files somewhere and refer to them in the bug report.

ic,

thanks for your quick reply.
It would seem i am coming to similar conclusions.

Now I’m passing my loader object that loaded the obj file url.
(I was thinking i would pass the url to the file as an urlrequest like).
       
Doing AssetLibrary.loadData(”/../somepath/to/the/file/meshFRAME_0.obj”);
Produces this parser error.

Doing AssetLibrary.loadData(contentLoader.getContent(“obj”)); //the completed loader

Produces a new error (but getting closer , related to a linked file

Error: Error #2032: Stream Error. URL: file:///C|/fla/meshFRAME_0.mtl

Problem being I am loading the obj files from an /embed dir not the fla dir.
It seems to link to an mtl from the obj file but cwd to the root dir instead of the same dir the obj came from.
(Where the mtl files also reside)

Not too sure if i really need the mtl file (would be easiest not to have to worry about it though)
I’ll have to do some reconstructing of the material from softimage to away3d anyway.
Plus i would assume uvs are stored in the mesh / obj file?

I think I will need some more research or tips before I file a bugreport.
Just to clarify I’m trying to set up a vertexanimation pipline. A python script in Softimage generates the obj files in a numbered sequence from (shape) animation keyframes. The awayd will load up all the frames and put them in a vertexAnimator (so i can go back and forth on the anims/look).

Nehoe, any pointers welcome, I am still a bit of a n00b.

Sorry for the thread hijack

O

Ok so altering the path in the obj file fixed it.

I guess i will log a bug relating to the error message.
Should be more like cannot read file from url or somminck along those lines.

Then another bug for the reading of a path to the mtl from the obj file. Where really that looks like just the file name of the mtl.

Oddly enough i’ve downloaded and set up all the new flash player 11 stuff, debugger and playerglobal. But my test now just renders black and AWstats says 0 polys. Some checking reveals that also some demos online produce this behaviour. What gives? Or maybe i should rather start a new thread on that.

There isn’t really a bug here (although one could fairly argue that the erro message could be clearer, so feel free to file a request about that.)

An OBJ file often has a reference to an MTL file, and the framework will handle that dependency like it handles all other dependencies. It will resolve the URL using the URL of the main (OBJ) file. However, if you are embedding your OBJ file, it cannot resolve the URL, and will instead try the URL relative to the SWF.

What you need to do if you embed a file is to use the AssetLoaderContext APIs to remap the dependency URL, e.g. to an embedded version of the MTL file or to another URL.

If you are not embedding, this is probably happening because the OBJ file defines an “incorrect” (absolute) path to the MTL file. For local file exchange that’s ok, but for the web there’s no way to solve this but to edit the OBJ file.

Thanks a million for that insight.

As far as bugs go, i agree.

Using an AssetLoaderContext defining the path fixed the problem.

My obj file had a path in it that really only described the filename of the mtl.
So loading the file and using an AssetLoaderContext fixed my problems.

Other problems seemed related to frustrumculling and camera control.

But I’m all set, thanks again and hope this is not too much of a thread hijack

Olivier