Fbx import assertion error(unknown location -1) #90627

New Issue

June · 2021-08-12T10:49:31+02:00

June commented

2021-08-12 10:49:31 +02:00

System Information
Operating system: Win10 pro
Graphics card: Nvidia M1200

Blender Version
Broken: 2.80-2.92
(example: 2.79b release)
(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)
Worked: (optional)

Short description of error
.....

  assert(val >= 0 and val < len(enum_items))

Fbx import assertion error(unknown location -1)
Attached test sample 001.fbx

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

Import the test .fbx sample

**System Information** Operating system: Win10 pro Graphics card: Nvidia M1200 **Blender Version** Broken: 2.80-2.92 (example: 2.79b release) (example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen) Worked: (optional) **Short description of error** ..... ``` assert(val >= 0 and val < len(enum_items)) ``` Fbx import assertion error(unknown location -1) Attached test sample [001.fbx](https://archive.blender.org/developer/F10278485/001.fbx) **Exact steps for others to reproduce the error** Based on the default startup or an attached .blend file (as simple as possible). 1. Import the test .fbx sample

June commented

2021-08-12 10:49:31 +02:00

Added subscriber: @tiancaipipi110

Pratik Borhade commented

2021-08-12 10:57:27 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2021-08-12 11:08:18 +02:00

Guess the reported issue is duplicate of #81657 (FBX Import error (enum with -1 value -- e.g. as done by the babylonjs exporter from 3dsmax))

Are you exporting it from 3ds max?

Guess the reported issue is duplicate of #81657 (FBX Import error (enum with -1 value -- e.g. as done by the babylonjs exporter from 3dsmax)) Are you exporting it from 3ds max?

June commented

2021-08-12 11:18:57 +02:00

Yes, exported from 3ds max, I can import it back to 3ds max. It happens to many of them, not sure what's the cause.

Philipp Oeser commented

2021-08-12 11:28:52 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-08-12 11:28:52 +02:00

Problem is a prop called diaphragmBlades.
It is marked as an enum with these possible values: [Circular, Polygonal].
But the value is 5.

Problem is a prop called `diaphragmBlades`. It is marked as an enum with these possible values: [`Circular`, `Polygonal`]. But the value is 5.

Philipp Oeser commented

2021-08-12 11:30:14 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Philipp Oeser commented

2021-08-12 11:30:14 +02:00

Is this the babylonjs exporter? Or the regular max fbx exporter?

June commented

2021-08-12 11:35:24 +02:00

Regular max fbx exporter.

Philipp Oeser commented

2021-08-12 12:24:59 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Philipp Oeser commented

2021-08-12 12:31:35 +02:00

Changed status from 'Needs Triage' to: 'Archived'

Philipp Oeser closed this issue

2021-08-12 12:31:35 +02:00

Philipp Oeser commented

2021-08-12 12:31:35 +02:00

Tbh, I dont think we can do anything here.
I can only assume that number of blades and blades shape is somehow mixed up in their exporter.

I think this needs to be reported to the 3DSMax bugtracker instead.
(feel free to reference this report here).

So thx reporting, but will close.

Tbh, I dont think we can do anything here. I can only assume that number of blades and blades shape is somehow mixed up in their exporter. I think this needs to be reported to the 3DSMax bugtracker instead. (feel free to reference this report here). So thx reporting, but will close.

June commented

2021-08-12 15:02:18 +02:00

Sorry, but how is this a 3dsmax bug if 3ds max imports it fine?

Philipp Oeser commented

2021-08-12 16:13:44 +02:00

What is diaphragmBlades set to when importing that FBX in max?
From the property definition, there only seem to be two choices, but the value is 5?

Max possibly is more forgiving with these properties, but to me this really looks like wrong usage of a property export, no?

What is `diaphragmBlades` set to when importing that FBX in max? From the property definition, there only seem to be two choices, but the value is 5? Max possibly is more forgiving with these properties, but to me this really looks like wrong usage of a property export, no?

Evan Wilson commented

2021-08-12 17:05:34 +02:00

Added subscriber: @EAW

Evan Wilson commented

2021-08-12 17:05:34 +02:00

FYI: Autodesk FBX Converter 2013.3 won't open the file, it says that it is corrupt.

June commented

2021-08-12 17:06:47 +02:00

I'm not sure what this property does, but Meshlab and Win10's 3D Viewer are both able to import this .fbx, so maybe it's not a very important property and could be skipped?

June commented

2021-08-12 17:14:31 +02:00

![fbx.jpg](https://archive.blender.org/developer/F10278728/fbx.jpg)

Philipp Oeser commented

2021-08-12 17:19:12 +02:00

FYI: I've asked in https://blender.chat/channel/data-assets-io-module if we should (maybe) handle borked properties more gracefully, will keep you posted with answers.
(still dont think this is a bug on our side... why not also report this to Autodesk?)

FYI: I've asked in https://blender.chat/channel/data-assets-io-module if we should (maybe) handle borked properties more gracefully, will keep you posted with answers. (still dont think this is a bug on our side... why not also report this to Autodesk?)

June commented

2021-08-13 19:22:22 +02:00

Thank you. I think it'll get a better chance resolved here.

Sign in to join this conversation.