Page MenuHome

add-on to import and export MilkShape3D (*.ms3d) files
Closed, ArchivedPublic

Description

Project: Blender Extensions
Tracker: Py Scripts Release
Blender: 2.66
Python: 3.2
Script name: io_scene_ms3d
Wiki page: http://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Import-Export/MilkShape3D_MS3D
Author(s): Alexander Nussbaumer
Category: Import Export
SVN Download: https://svn.blender.org/svnroot/bf-extensions/trunk/py/scripts/addons/io_scene_ms3d/
Status: Open

this add-on allows you to import ms3d files to Blender and export ms3d from Blender (conform with MilkShape3D v1.8.4 file format).

at import time, all properties of the ms3d model will be stored to separate MS3D-panels in blender to have nearly 100% control of all the available raw data. same for export. the exporter will respect the data, that are stored in these MS3D-panels, to have full control, what will be stored in output file. that gives you the chance to tweak the output to your purpose and have all the features of ms3d, that blender does not has or handle in an other way.

for the full list of implemented features, please visit the wiki page

Event Timeline

(i closed the previously bug tracker http://projects.blender.org/tracker/index.php?func=detail&aid=29404 for this add-on)

please report bugs and issued here, which are related to this add-on...

For some reason when I import models it looks like the following is happening (possibly in every triangle, but I am not 100% sure)

The triangle vertex 0 gets the texture coordinates of vertex 1
the vertex 1 gets the texture coordinates of vertex 2
the vertex 2 gets the coordinates of vertex 0
(the "rotation" may actually be to the opposite direction, I am not sure)

This happens both in real models I have purchased, and in a simple single triangle model I created in milkshape3d my self.

When testing with the single triangle it seems to export OK to ms3d format, but if I import the exported file a gain the vertices are "rotated again". If I repeat the import/export three times I actually get the correct model (as the vertex texture coordinates now are bound to correct vertices).

I have tried to read the python code, but I am un experienced with python and especially with Blender, and I have not yet noticed any cause for this.

Eero

thank you for reporting this issue. i am currently not sure if somthing changed from 2.67b to 2.68a related to this in blender API...
i opened a bug report to the bug tracker [#36443] "Vertex to UV index doesn't match with 2.68a". with blender 2.67b everything works, but with blender 2.68a the same script is broken. please stay tuned.
at the moment, i your suggest you to use blender 2.67a to import ms3d objects until i know the reason and prepared a solution.

a modifier version is available on svn. i made a workaround that will invert the "scrambled" vertex-to-UV order.
tomorrow, the changed add-on should be included to the buildBot version on
http://builder.blender.org/download/

Hi Alexander,

As I tried to extend the length of the MS3D-Groups list view by clicking on those two strokes blender freezes. This is only the case when the list is inactive while in object mode.

This task was automatically closed as archived as part of migration, because it was determined to be no longer active.

The authoritative list of addons is on the wiki, we no longer have a report for each addon to track bugs and updates. Bugs can be reported individually and assigned to the addon developers. See the Addons project page for more information on the workflow.

Nobody (None) closed this task as Archived.Feb 2 2013, 7:44 AM