import a fbx then export a dae file, blender crashed, (always) #53230

New Issue

xiwen · 2017-11-02T10:27:08+01:00

xiwen commented

2017-11-02 10:27:08 +01:00

System Information
macOS 10.13.1
iMac late 2013

Blender Version
version 2.79

Worked: (optional)

Short description of error
import a fbx then export a dae file, blender crashed, (always)

Exact steps for others to reproduce the error

open blender
remove box
import a fbx
export to dae
crash

crash log:

blender.crash

model sample:

Sapphiart_model.fbx.zip

**System Information** macOS 10.13.1 iMac late 2013 **Blender Version** version 2.79 Worked: (optional) **Short description of error** import a fbx then export a dae file, blender crashed, (always) **Exact steps for others to reproduce the error** 1. open blender 2. remove box 3. import a fbx 4. export to dae 5. crash crash log: [blender.crash](https://archive.blender.org/developer/F1085843/blender.crash) model sample: [Sapphiart_model.fbx.zip](https://archive.blender.org/developer/F1085844/Sapphiart_model.fbx.zip)

xiwen commented

2017-11-02 10:27:08 +01:00

Changed status to: 'Open'

xiwen commented

2017-11-02 10:27:08 +01:00

Added subscriber: @abroter

Peter Boos commented

2017-11-02 18:59:24 +01:00

Added subscriber: @PeterBoos

Peter Boos commented

2017-11-02 18:59:24 +01:00

I couldnt even open the fbx file, i am not a developer but in some cases i give advice that can help you and them

You see its complex to keep up with company formats if those companies dont support open formats (like DocX), basically its all reversed engineering whats in Blender.
I think you better go with the tools provided by those companies to convert those files; checkout this : https://www.autodesk.com/products/fbx/fbx-review
Blender will never be a state of the art converter of autocad formats, simply because they dont put their format under open document contract licenses.
Also they are prone to change some of their formats so that different versions of autocad itself cannot even exchange files, just to drive up their sales...

I'd say yes its a bug, but dont blame the people who try to reverse engineer it, and always in such cases try to find the company and check if they do conversions.
Some developers try to reverse engineer their formats with some degree of succes, but since its not open its always a trouble.
So great if it got fixed but dont count of it, as reverse engineering is a enormous task. But i hope that the link will help you in your process.

I couldnt even open the fbx file, i am not a developer but in some cases i give advice that can help you and them You see its complex to keep up with company formats if those companies dont support open formats (like DocX), basically its all reversed engineering whats in Blender. I think you better go with the tools provided by those companies to convert those files; checkout this : https://www.autodesk.com/products/fbx/fbx-review Blender will never be a state of the art converter of autocad formats, simply because they dont put their format under open document contract licenses. Also they are prone to change some of their formats so that different versions of autocad itself cannot even exchange files, just to drive up their sales... I'd say yes its a bug, but dont blame the people who try to reverse engineer it, and always in such cases try to find the company and check if they do conversions. Some developers try to reverse engineer their formats with some degree of succes, but since its not open its always a trouble. So great if it got fixed but dont count of it, as reverse engineering is a enormous task. But i hope that the link will help you in your process.

xiwen commented

2017-11-03 04:21:08 +01:00

In #53230#469046, @PeterBoos wrote:
I couldnt even open the fbx file, i am not a developer but in some cases i give advice that can help you and them

You see its complex to keep up with company formats if those companies dont support open formats (like DocX), basically its all reversed engineering whats in Blender.
I think you better go with the tools provided by those companies to convert those files; checkout this : https://www.autodesk.com/products/fbx/fbx-review
Blender will never be a state of the art converter of autocad formats, simply because they dont put their format under open document contract licenses.
Also they are prone to change some of their formats so that different versions of autocad itself cannot even exchange files, just to drive up their sales...

I'd say yes its a bug, but dont blame the people who try to reverse engineer it, and always in such cases try to find the company and check if they do conversions.
Some developers try to reverse engineer their formats with some degree of succes, but since its not open its always a trouble.
So great if it got fixed but dont count of it, as reverse engineering is a enormous task. But i hope that the link will help you in your process.

sample fbx file can open with “autodesk fbx review” app

> In #53230#469046, @PeterBoos wrote: > I couldnt even open the fbx file, i am not a developer but in some cases i give advice that can help you and them > > You see its complex to keep up with company formats if those companies dont support open formats (like DocX), basically its all reversed engineering whats in Blender. > I think you better go with the tools provided by those companies to convert those files; checkout this : https://www.autodesk.com/products/fbx/fbx-review > Blender will never be a state of the art converter of autocad formats, simply because they dont put their format under open document contract licenses. > Also they are prone to change some of their formats so that different versions of autocad itself cannot even exchange files, just to drive up their sales... > > I'd say yes its a bug, but dont blame the people who try to reverse engineer it, and always in such cases try to find the company and check if they do conversions. > Some developers try to reverse engineer their formats with some degree of succes, but since its not open its always a trouble. > So great if it got fixed but dont count of it, as reverse engineering is a enormous task. But i hope that the link will help you in your process. sample fbx file can open with “autodesk fbx review” app ![屏幕快照 2017-11-03 上午11.17.21.png](https://archive.blender.org/developer/F1089074/屏幕快照_2017-11-03_上午11.17.21.png)

Joel Godin commented

2017-11-03 11:17:24 +01:00

Added subscribers: @GaiaClary, @FloridaJo

Gaia Clary was assigned by Joel Godin

2017-11-03 11:17:24 +01:00

Joel Godin commented

2017-11-03 11:17:24 +01:00

Happens here on OSX as well. Oct 24 build.
crash log here:

blender.crash.txt

Is this yours @GaiaClary ?

Happens here on OSX as well. Oct 24 build. crash log here: [blender.crash.txt](https://archive.blender.org/developer/F1089900/blender.crash.txt) Is this yours @GaiaClary ?

Gaia Clary commented

2017-11-03 11:53:38 +01:00

Please can you create a blend file that will crash blender when you try to export it to dae ?
Then prepare the blend file such that all i need to do is calling:

  File -> Export -> Collada -> Export Collada

to see blender crashing.
I just want to be sure that i am looking at the right thing.
Then its much easier to figure out what is wrong :)

thanks

Please can you create a blend file that will crash blender when you try to export it to dae ? Then prepare the blend file such that all i need to do is calling: ``` File -> Export -> Collada -> Export Collada ``` to see blender crashing. I just want to be sure that i am looking at the right thing. Then its much easier to figure out what is wrong :) thanks

Gaia Clary commented

2017-11-03 12:13:13 +01:00

Changed status from 'Open' to: 'Archived'

Gaia Clary closed this issue

2017-11-03 12:13:13 +01:00

Gaia Clary commented

2017-11-03 12:14:29 +01:00

Changed status from 'Archived' to: 'Open'

Gaia Clary reopened this issue

2017-11-03 12:14:29 +01:00

Joel Godin commented

2017-11-04 04:52:23 +01:00

If I pack external data, it no longer crashes.
You have to import, then export > crash.
If you import, pack, export, > no crash.

If I pack external data, it no longer crashes. You have to import, then export > crash. If you import, pack, export, > no crash.

Colin Basnett commented

2017-12-12 12:40:25 +01:00

Added subscriber: @cmbasnett

ywaby commented

2018-01-01 10:15:31 +01:00

Added subscriber: @ywaby

ywaby commented

2018-01-01 10:15:31 +01:00

same with me

import fbx and export dae, will crash blender
export to other file type, it is ok
save and reopen blender then export dae, it work ok
daily build blender has same problem

my system is debian testing

with error info

terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_M_construct null not valid

HallwaysCollision.fbx

same with me - import fbx and export dae, will crash blender - export to other file type, it is ok - save and reopen blender then export dae, it work ok - daily build blender has same problem my system is debian testing with error info ``` terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_M_construct null not valid ``` [HallwaysCollision.fbx](https://archive.blender.org/developer/F1641005/HallwaysCollision.fbx)

blender-admin commented

2018-01-01 15:02:26 +01:00

This issue was referenced by e59cf13b8c

This issue was referenced by e59cf13b8c457c69945a9f85e9de61d36d434eea

Gaia Clary commented

2018-01-01 15:03:00 +01:00

Changed status from 'Open' to: 'Resolved'

Gaia Clary closed this issue

2018-01-01 15:03:00 +01:00

Gaia Clary commented

2018-01-01 15:06:19 +01:00

Right after importing the fbx the active UV Layer seems to be not defined for the imported Mesh Object. The active UV Layer is automatically enabled as soon as i open the data properties of the mesh object. From this moment on the Collada exporter works without crashing.

The Blender crash during Collada export happens because the exporter expects an active UV Layer when UV Layers are defined. This seems to be a wrong assumption. I fixed this in the Collada Exporter in master

Right after importing the fbx the active UV Layer seems to be not defined for the imported Mesh Object. The active UV Layer is automatically enabled as soon as i open the data properties of the mesh object. From this moment on the Collada exporter works without crashing. The Blender crash during Collada export happens because the exporter expects an active UV Layer when UV Layers are defined. This seems to be a wrong assumption. I fixed this in the Collada Exporter in master

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

import a fbx then export a dae file, blender crashed, (always) #53230