Hi Fabrice,
First of all, a big thanks for replying to quickly. I will test
and reply.
Sushant
On May 10, 7:15 pm, Fabrice3D <[email protected]> wrote:
> I'm no expert at collada format ( I never use them), but this looks
> like a coordinate issue.
> you probably set in papervision a var saying its right or left handed
> system.
> or they have in the Erain export corrected the orientation for PV
> before exporting the dae file.
>
> To fix this issue and see the same in away, you need either to rotate
> the model in your app or in Away: z by 90 degrees. And probably
> inverse your x.
> if you do it in Away, you can do it like this:
>
> myobject.rotationZ -= 90;
> myobject.applyRotations(); --> optional
>
> and for the x, if necessary:
> myobject.scaleX = -1;
> myobject.invertFaces(); --> to flip the faces
>
> of course it would be better to do it in your editor.
>
> Fabrice
>
> On May 10, 2009, at 3:42 PM, flashangel wrote:
>
>
>
> > Hi friends,
> > I must first admit that I am NOT knowledgeable enough about
> > internals of 3D engines. I have just read the 2 books of Keith Peters
> > about 3D and some chapters regarding maths underlying the 3D
> > operations.
>
> > I have been following both Papervision3D and Away3D since a year or
> > so. Now I have got a project to work on some interesting 3D model
> > manipulation. I do not know 3d modelling. I had been using swift3d
> > papervision exporter to export DAe and was using papervision. However
> > for larger models I found that Papervision 3D sucks. I was knowing
> > that Away3D had moved way forward and implemented normal mapping and
> > DOT3BitmapMaterial. From my premitive knowledge of 3D, I am thinking
> > that this is what is going to save me by creating low poly models and
> > high quality normal maps. I have also seen the demo of "2 heads" and
> > "teapot" given by Fabrice. However, he has not shared the source code
> > (or I couldn't find it probably).
>
> > I am giving below the stuff where I am stuck.
>
> > The 3d model is of a female model (Masha):
> >http://www.dnyandeep.com//headTest/assets/head.dae
>
> > the model rendered using swift3d (papervision exporter)
> >http://www.dnyandeep.com/headTest/swift/head.zip
>
> > Same DAE as is used by PV3D is being used in below given Away3D test
> >http://www.dnyandeep.com/headTest/AwayNormalMapTest.html
>
> > You can notice that Away3D had incorrectly rendered the same model.
> > However pv3d does correctly. I really want to use Away3d for this
> > project because of its efficiency and especially what I read about
> > occlusion culling that is available in Away3D.
>
> > I am stuck, any pointers where I am going wrong? Also I wish to know
> > perfect guidelines about what I need to do to directly export the
> > model from 3D tools like Max. Can somebody guide me please? As I will
> > need to tell this to the 3D modeller person I am working with to get
> > the exported 3DS/DAE files from him in perfect format suitable to
> > Away3D. Also why the model is getting rendered is PV3D but not doing
> > correctly in Away? I definitely do not know any internals, so any help
> > is appreciated.
>
> > Sushant
