Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
doesn't match with 2.68a", because that issue is fixed in blender 2.68a r59343 now.
- deleted not needed workaround for issue [#36443], because it is fixed in blender 2.68a r59343,
- added BMEdge generation to the importer (only for nice doing),
- added undo to operators,
- deleted some unused strings,
|
|
- until the <BMesh>.faces.new(..) is scrambling the vertices order (input -> output), i use the workaround, that build a de-scramble dictionary.
i still thing it is a bug in blender 2.68.
- got rid of unneeded option 'io_scene_ms3d.set_sence_to_metric', Ms3dSetSceneToMetricOperator, set_sence_to_metric
|
|
|
|
|
|
changed: position of update scene;
|
|
shown in:
http://www.blender.org/documentation/blender_python_api_2_65_10/bpy.types.UIList.html
|
|
and tiny other things e.g.
fix: sum of weights sometimes reaches only 99% instead of 100%
mod: come # comments - year to 2013
mod: ui of importer - joint size bit closer to other item
|
|
during export for applying transform.
that will calculate parented object correctly.
related to issue reported by Shadoh.
http://www.blender.org/forum/viewtopic.php?t=26251
|
|
cannot support.
indirect part of the reported issue:
http://www.blender.org/forum/viewtopic.php?t=26251
now, vertex weights will sorted according the weight. in case of more than 3 weights, less important ones will be skipped on export.
|
|
hopefully the permission by Campbell Barton)
|