13 Comments

• 
  Theo February 27, 2012 at 04:28

  Awesome!

  I tested it with some models from

  http://telias.free.fr/Models_menu.html

  They came in just fine…

  Reply
• 
  Serg April 14, 2012 at 02:08

  Thanks a lot for this amazing tool!
  Could you please let me know where you get the MD2 models? looking for a place I can get few for free or buy.

  Reply
  • 
    Klas April 14, 2012 at 15:39

    Glad you find it useful! :)

    It´s a really old format so it´s not used much nowadays.

    But there are some models still around.
    The most obvious is Planet Quake: http://planetquake.gamespy.com/View.php?view=Quake2.List&game=5&category_select_id=3
    This one got a few: http://www.md2.sitters-electronics.nl/models.html
    Some fangame that got a few: http://mb.srb2.org/forumdisplay.php?s=6b3f4a9fd6558d6393ef62f56adfc92a&f=72

    I guess you could also use something like Milkshape 3d( http://chumbalum.swissquake.ch/ ) to convert between other formats. I think Md2 models had like a 4k polycount limit or something though.

    Reply
• 
  Saus November 5, 2012 at 11:20

  When i download it with Firefox, it’s saved like “name.part” file. Why i can’t save it like .js? It’s only a .part file

  Reply
  • 
    Klas November 5, 2012 at 14:42

    Not sure why that is, I guess it´s just the way Firefox handles these “blobs” differently. But all the data is there and you can just rename the *.part-file to “whatever.js”.

    Reply
• 
  arcanis November 11, 2012 at 20:00

  I’ve got an issue with a two-materials model (a single texture seems to be used for the whole model), is it possible to convert it from md2 to json using your tool ?

  Reply
  • 
    Klas November 14, 2012 at 09:07

    You mean two textures are used on a single model? Do you have an example of such a model somewhere? Might be better to go with the three.js blender pipeline for such a model though.

    Reply
• 
  joamag December 23, 2012 at 14:33

  This is really awesome work.

  Do you think it’s possible to convert the normal indexes to the json format ?

  Reply
  • 
    Klas December 23, 2012 at 15:41

    I guess what you are after is something like this that is already in three.js by now:
    https://github.com/mrdoob/three.js/blob/master/src/core/Geometry.js#L305

    So you could just load the model and then do geometry.computeMorphNormals();

    This example might be helpful: http://mrdoob.github.com/three.js/examples/webgl_morphnormals.html

    Or did you mean something else?

    Reply
    • 
      joamag December 23, 2012 at 16:16

      Yes, you’re right there’s no need to used the pre-computed values.

      Thanks

      Reply
• 
  joamag December 26, 2012 at 13:25

  I’ve tried to use the converter under different versions of Three.js and since r50 the texture mapping fails as the mapping vertices seem to be wrong.

  Do you have any idea of what has changed in Three.js since r50 that might have caused the problem ?

  Reply
  • 
    Klas December 26, 2012 at 14:19

    Yes, I think something with the texture-flipping changed in Three.js. Between 3.0 and 3.1 of the json-format: https://github.com/mrdoob/three.js/wiki/JSON-Model-format-3.1

    I´ll see if I have time to change the converter to output v 3.1 instead, should be an easy fix.

    In the meantime you could probably set texture.flipY = false;

    Reply
    • 
      joamag December 26, 2012 at 14:51

      You’re right the flipY trick worked just fine.

      Reply