diff options
| author | Alexander N <alpha-beta-release@gmx.net> | 2013-09-16 17:50:20 +0400 |
|---|---|---|
| committer | Alexander N <alpha-beta-release@gmx.net> | 2013-09-16 17:50:20 +0400 |
| commit | 3ed552b9b825c63ab6ff3caff101d0f0ad25503b (patch) | |
| tree | f547e1ad32600818243e909a63d01d9e40be01a0 /io_scene_ms3d/__init__.py | |
| parent | cf6493491297a05e0e4bcfd7b9e6c7b6b7b2ef86 (diff) | |
added: exporter takes armature parent in account of animation handling.
only one armature source will can be taken at the moment, and will taken in the following "priority" order:
1. armature parent will be taken if exist.
2. first available armature modifier will be taken if exist.
open question: what is best practice, in case of existence of multiple armature sources?
(armature parent and one or more armature modifier)
can that case happen (very often) in real world mesh modeling?
Diffstat (limited to 'io_scene_ms3d/__init__.py')
| -rw-r--r-- | io_scene_ms3d/__init__.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/io_scene_ms3d/__init__.py b/io_scene_ms3d/__init__.py index fc228245..7173a1aa 100644 --- a/io_scene_ms3d/__init__.py +++ b/io_scene_ms3d/__init__.py @@ -23,7 +23,7 @@ bl_info = { 'description': "Import / Export MilkShape3D MS3D files"\ " (conform with MilkShape3D v1.8.4)", 'author': "Alexander Nussbaumer", - 'version': (0, 99, 2), + 'version': (0, 99, 3), 'blender': (2, 66, 0), 'location': "File > Import & File > Export", 'warning': "", |