can't export to .fbx with UV map #54684

New Issue

toast · 2018-04-17T07:44:05+02:00

toast commented

2018-04-17 07:44:05 +02:00

System Information
Operating system and graphics card
windows 10, intel integrated hd graphics 530
Blender Version
Broken: 2.79b
Worked: (optional)

Short description of error
can't export to .fbx with UV map
Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps
try to export to .fbx
heck.blend

**System Information** Operating system and graphics card windows 10, intel integrated hd graphics 530 **Blender Version** Broken: 2.79b Worked: (optional) **Short description of error** can't export to .fbx with UV map **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps try to export to .fbx [heck.blend](https://archive.blender.org/developer/F2755768/heck.blend)

toast commented

2018-04-17 07:44:05 +02:00

Added subscriber: @ToastyEngineer

Philipp Oeser commented

2018-04-17 10:16:20 +02:00

Added subscriber: @lichtwerk

Philipp Oeser self-assigned this 2018-04-17 10:16:20 +02:00

Philipp Oeser commented

2018-04-17 10:16:20 +02:00

Confirmed, having a closer look now...

Philipp Oeser commented

2018-04-17 11:06:10 +02:00

You have a couple of UVs with undefined positions (NANs) in "UVMap" ("UV1" doesnt have these and exports fine)
Can be checked with this script:

import bpy
import math

uvlayer = bpy.context.active_object.data.uv_layers['UVMap']

for x in range(len(uvlayer.data)-1):
    if math.isnan(uvlayer.data[x].uv[0]):
        print("index for nan: ", x, uvlayer.data[x].uv)

should give you following output:

index for nan:  73600 <Vector (-nan, -nan)>
index for nan:  73602 <Vector (-nan, -nan)>
index for nan:  73606 <Vector (-nan, -nan)>
index for nan:  73609 <Vector (-nan, -nan)>
index for nan:  73612 <Vector (-nan, -nan)>
index for nan:  73615 <Vector (-nan, -nan)>
index for nan:  73618 <Vector (-nan, -nan)>
index for nan:  73620 <Vector (-nan, -nan)>
index for nan:  73623 <Vector (-nan, -nan)>
index for nan:  73627 <Vector (-nan, -nan)>
index for nan:  73630 <Vector (-nan, -nan)>
index for nan:  73633 <Vector (-nan, -nan)>
index for nan:  73636 <Vector (-nan, -nan)>
index for nan:  73639 <Vector (-nan, -nan)>
index for nan:  73641 <Vector (-nan, -nan)>
index for nan:  73644 <Vector (-nan, -nan)>
index for nan:  73647 <Vector (-nan, -nan)>
index for nan:  73651 <Vector (-nan, -nan)>
index for nan:  73654 <Vector (-nan, -nan)>
index for nan:  73656 <Vector (-nan, -nan)>
index for nan:  73659 <Vector (-nan, -nan)>
index for nan:  73662 <Vector (-nan, -nan)>
index for nan:  73665 <Vector (-nan, -nan)>
index for nan:  73668 <Vector (-nan, -nan)>

Question is where these come from in the first place, because these can cause problems with all kinds of tools.
Was this unwrapped in blender? Or imported with one of the official addons?
(I wasnt able to produce NAN UVs with blenders unwrapping methods, so if you use these, you should be fine and able to export)

Like I said, I dont think it is even desirable to let the FBX exporter check for these NAN (would make it slower) and time is better spent investigating where these NANs come from (to also prevent other tools having trouble with them)
note: I havent spent time investigating if there is a quick method to do a cleanup on these UVs (get rid of the NANs)

Marking as incomplete until we get an answer on how these UVs were generated...

You have a couple of UVs with undefined positions (NANs) in "UVMap" ("UV1" doesnt have these and exports fine) Can be checked with this script: ``` import bpy import math uvlayer = bpy.context.active_object.data.uv_layers['UVMap'] for x in range(len(uvlayer.data)-1): if math.isnan(uvlayer.data[x].uv[0]): print("index for nan: ", x, uvlayer.data[x].uv) ``` should give you following output: ``` index for nan: 73600 <Vector (-nan, -nan)> index for nan: 73602 <Vector (-nan, -nan)> index for nan: 73606 <Vector (-nan, -nan)> index for nan: 73609 <Vector (-nan, -nan)> index for nan: 73612 <Vector (-nan, -nan)> index for nan: 73615 <Vector (-nan, -nan)> index for nan: 73618 <Vector (-nan, -nan)> index for nan: 73620 <Vector (-nan, -nan)> index for nan: 73623 <Vector (-nan, -nan)> index for nan: 73627 <Vector (-nan, -nan)> index for nan: 73630 <Vector (-nan, -nan)> index for nan: 73633 <Vector (-nan, -nan)> index for nan: 73636 <Vector (-nan, -nan)> index for nan: 73639 <Vector (-nan, -nan)> index for nan: 73641 <Vector (-nan, -nan)> index for nan: 73644 <Vector (-nan, -nan)> index for nan: 73647 <Vector (-nan, -nan)> index for nan: 73651 <Vector (-nan, -nan)> index for nan: 73654 <Vector (-nan, -nan)> index for nan: 73656 <Vector (-nan, -nan)> index for nan: 73659 <Vector (-nan, -nan)> index for nan: 73662 <Vector (-nan, -nan)> index for nan: 73665 <Vector (-nan, -nan)> index for nan: 73668 <Vector (-nan, -nan)> ``` Question is where these come from in the first place, because these can cause problems with all kinds of tools. Was this unwrapped in blender? Or imported with one of the official addons? (I wasnt able to produce NAN UVs with blenders unwrapping methods, so if you use these, you should be fine and able to export) Like I said, I dont think it is even desirable to let the FBX exporter check for these NAN (would make it slower) and time is better spent investigating where these NANs come from (to also prevent other tools having trouble with them) note: I havent spent time investigating if there is a quick method to do a cleanup on these UVs (get rid of the NANs) Marking as incomplete until we get an answer on how these UVs were generated...

Philipp Oeser commented

2018-04-29 20:34:34 +02:00

Changed status from 'Open' to: 'Archived'

Philipp Oeser closed this issue

2018-04-29 20:34:34 +02:00

Philipp Oeser commented

2018-04-29 20:34:34 +02:00

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.

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

can't export to .fbx with UV map #54684