Please allow Blender to convert scientific notation coordinates to decimal in exported files #55041

New Issue

sok0 · 2018-05-12T20:13:55+02:00

sok0 commented

2018-05-12 20:13:55 +02:00

The attached .fbx contains vertices and shapekey offset coordinates stored in scientific notation (file originated from a .CSV file converted to .pmx then imported to Blender with plugin then exported as .FBX). The scientific notation has been passed through each step of the workflow.

The problem that I am having is that the Unity 3D engine cannot import scientific notation and sets all these values to zero. The end result is that vertices are not in the same location in Unity as they are in Blender.

It would be great if there was a way that I could convert directly through blender coordinate data from scientific notation to decimal. This may cause a truncation on some values which there could be a warning message for but it would greatly simplify my life when this problem occurs.

bugreport1.fbx

The attached .fbx contains vertices and shapekey offset coordinates stored in scientific notation (file originated from a .CSV file converted to .pmx then imported to Blender with plugin then exported as .FBX). The scientific notation has been passed through each step of the workflow. The problem that I am having is that the Unity 3D engine cannot import scientific notation and sets all these values to zero. The end result is that vertices are not in the same location in Unity as they are in Blender. It would be great if there was a way that I could convert directly through blender coordinate data from scientific notation to decimal. This may cause a truncation on some values which there could be a warning message for but it would greatly simplify my life when this problem occurs. [bugreport1.fbx](https://archive.blender.org/developer/F3349436/bugreport1.fbx)

sok0 commented

2018-05-12 20:13:55 +02:00

Added subscriber: @sok0

sok0 commented

2018-05-12 23:48:00 +02:00

Update: work around is to scale the mesh such that microscopic floating points (i.e. 1.0e-11 are increased to 1.0e1) so that unity doesn't round them to zero

Philipp Oeser commented

2018-05-13 14:42:18 +02:00

Added subscribers: @mont29, @lichtwerk

Bastien Montagne was assigned by Philipp Oeser

2018-05-13 14:42:18 +02:00

Philipp Oeser commented

2018-05-13 14:42:18 +02:00

Hm, this seems to follow the spec, right?

I believe the better choice would be to open a report with Unity (to fix on their side) rather than adding yet another option on the blender side?

But, as with anything related to FBX, I'll let @mont29 have the final word here.

Hm, this seems to follow the spec, right? - I believe the better choice would be to open a report with Unity (to fix on their side) rather than adding yet another option on the blender side? But, as with anything related to FBX, I'll let @mont29 have the final word here.

Bastien Montagne commented

2018-05-13 14:44:21 +02:00

In any case, we only support binary FBX files now (which do not have that issue of course), old FBX6.1 ASCII code is only kept for historical compat and such, but no more maintained (and doomed to be removed soonish).

Bastien Montagne commented

2018-05-13 15:24:13 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2018-05-13 15:24:13 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Please allow Blender to convert scientific notation coordinates to decimal in exported files #55041