Surprisingly, in my case, the texture does show up on the model.
Everything appears to be working absolutely perfectly until I try to
access the material library. It appears to me that the obj loader is
loading and applying the texture properly, but it doesn't place it
into the material library for us to access. Which means, I can't
replace materials dynamically which is exactly what I'm trying to do.
I've been trying to work around this for the better part of a month
with no luck.

On Mar 10, 2:55 pm, Reinorvak <[email protected]> wrote:
> Hello there, I'm have the same problem I believe. The model can appear
> on the view and shows up with the basic color materials on it. The
> modelLibrary is null within the object but otherwise its there.
>
> The accessing of null might be from a different object maybe?
>
> Now I've been banging my head against the wall at this away3D OBJ
> loader, but to no avail can I figure out why model has no materials. I
> believe the OBJ loader doesn't actually set up a  materialLibrary, but
> actually just applies the material to all faces within the mesh.
>
> I've stepped through everything I could on the away3D side and found
> that the image is loading correctly, the mtl is loading correctly, and
> the obj is loading correctly, the texture just fails to make it back
> to the model on screen. Instead, it assigns it to this container
> object in the OBJ loader who doesn't belong to anyone.
>
> Not quite sure whats going on here, help us out mates!
>
> Rein
>
> On Mar 9, 12:49 pm, charglerode <[email protected]> wrote:
>
>
>
> > I load an OBJ file using the Loader3D, object loads and is displayed
> > correctly. However, when I try to access the material data from the
> > loaded Object3D it's null. In fact, any property I try to trace comes
> > back null. Any Ideas?

Reply via email to