Slow fps with one collada model

using blender 2.42a and exporter collada 1.4.0 from illusoft.

I have a model that I know is good as an .obj so i exported it as .dae, but when I load into jme I get < 30 fps where it should be in the hundreds.

Has anyone else experienced this?

here is my code:

public class TestColladaLoading2 extends SimpleGame {

   public static void main(String[] args) {

      TestColladaLoading2 app = new TestColladaLoading2();




   protected void simpleInitGame() {


      cam.setAxes(new Vector3f(-1, 0, 0), new Vector3f(0, 0, 1),

            new Vector3f(0, 1, 0));

      cam.setLocation(new Vector3f(0, -100, 20));

      input = new FirstPersonHandler(cam, 80, 1);

      URL url = TestColladaLoading2.class.getClassLoader().getResource("");

      InputStream mobboss = TestColladaLoading2.class.getClassLoader()


      ColladaImporter.load(mobboss, url, “model”);

      Node model = ColladaImporter.getModel();


      rootNode.updateGeometricState(0, true);




and a screenshot:

Can you post the collada file?  It doesn't seem likely that is the fault, but I could fire it up in our viewer at work and have a look.

Can you post the collada file?

sure can, here it is:

runs great over here…  Only special thing I notice is that it has no normals.  It also seems to have a huge bounding box, perhaps an odd triangle is off the screen?  Otherwise it seems like an average model.  Sorry I couldn't be of more help.

Only special thing I notice is that it has no normals

good call, i clicked "draw normals" in blender and now im getting 500+ fps. thx renanse

So how come the lack of normals would bork the fps so much (or is that a really stupid question)?

Also, come come it ran great for renanse even without normals (I assume great means proper fps)?

I demand knowledge!  XD

@hal: good point

? at a guess, something to do with determining culling

there aren't that many triangles. the jump from less than 30 to more than 500 is quite big

edit: i mean fps

well here is some weird behaviour that I cant explain, I tried the .dae w/o the normals to see if it would run at < 30 fps, and it ran at 500+ this time. I have no idea why it ran so slow first time but I cant seem to recreate the problem.

It also seems to have a huge bounding box

also I dont see the huge bounding box just a regular bounding box around the pin.

oow eer how odd!  :?

re: the boundings… Could just be an artifact in the tool, no worries.  As for the fps, perhaps something else was going on on your machine at the time?