diff options
| author | Bastien Montagne <montagne29@wanadoo.fr> | 2013-09-16 17:56:27 +0400 |
|---|---|---|
| committer | Bastien Montagne <montagne29@wanadoo.fr> | 2013-09-16 17:56:27 +0400 |
| commit | 566a38db6d336a0cf2b6d2e1ca92ddb77c133864 (patch) | |
| tree | 8151b2097817ae72c233b11612f3e98ac5f0c1d4 /io_scene_fbx/export_fbx.py | |
| parent | 3ed552b9b825c63ab6ff3caff101d0f0ad25503b (diff) | |
Fix [#36268] FBX exporter precision min is too big
Using a bit more flexible way to handle those values (range now from 10^-18 (20) to 10^2 (0) frames). Not sure we shouldn't rather get rid of such "magic" value and let user set frame threshold directly, though!
Diffstat (limited to 'io_scene_fbx/export_fbx.py')
| -rw-r--r-- | io_scene_fbx/export_fbx.py | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/io_scene_fbx/export_fbx.py b/io_scene_fbx/export_fbx.py index 9513801b..94b40eea 100644 --- a/io_scene_fbx/export_fbx.py +++ b/io_scene_fbx/export_fbx.py @@ -1385,7 +1385,6 @@ def save_single(operator, scene, filepath="", # Write the Real Mesh data here fw('\n\t\tVertices: ') i = -1 - for v in me_vertices: if i == -1: fw('%.6f,%.6f,%.6f' % v.co[:]) @@ -2601,7 +2600,8 @@ Connections: {''') frame_orig = scene.frame_current if use_anim_optimize: - ANIM_OPTIMIZE_PRECISSION_FLOAT = 0.1 ** anim_optimize_precision + # Do we really want to keep such behavior? User could enter real value directly... + ANIM_OPTIMIZE_PRECISSION_FLOAT = 10 ** (-anim_optimize_precision + 2) # default action, when no actions are avaioable tmp_actions = [] |