On Feb 9, 9:43 pm, Fabrice3D <[email protected]> wrote:
> Try replace all code in modelLoaderSuccessHandler with
>
> view.scene.addChild(modelLoader.handle);
> view.render();
> and comment the line where you set your enterframe event listener.
> Just to see if you get these errors because of a faulty construct of the 
> object
> (if you see nothing, make sure the camera looks at the object, using 
> camera.lookAt(); )
>
> If you drop the model in Prefab, no warnings? no missing mtl file or 
> resources?
> Prefab would replace the missing stuff by default maps, Away would not and 
> possibly
> trigger errors.
>
> a detail:> model = new Object3D;
> > model = modelLoader.handle as Object3D;
>
> why do you need a new object3D here?
>
> Fabrice
>

(Just tried installing Prefab, but it returns an error about using an
unsupported version of AIR...)

Anyway, I am pretty confident the Obj file is OK, since it worked in
the previous build of Away3D I was using and it imports cleanly in
Blender.

The error is at the line:

modelLoader = Obj.load("http://"; + serverAddress + "/
officeincreasedaway.obj", { scaling:1, bothsides:true } );


and not in the modelLoaderSuccessHandler and appears to be something
to do with the Mesh creation algorithm.

Thought: Does Away3D have any issues with Unix style line endings (ie
"/r/n" vs "/n")?

Reply via email to