OBJ file doesn't import and ends with error message #99660

Closed
opened 2022-07-13 06:03:06 +02:00 by Dahn KIm · 12 comments

System Information
Operating system: Windows 10 21H2
Graphics card: NVIDIA GeForce GTX 1650

Blender Version
Broken: 2.79 (sub 0), branch: master, commit date: 2017-09-11 10:43, hash: 5bd8ac9
Worked: none, only tried 2.79

Short description of error
I was trying to import this one specific obj file I exported from Marvelous Designer but it doesn't import and instead results in an error message in blender. Other obj files have been working but not this one for some reason.
The error message in question (couldn't figure out how to copy the error message directly into here):
image.png
mima4.obj

Exact steps for others to reproduce the error
Exactly as how you would import any obj file: Files, Import, click Waveform (.obj), and then go the location of the downloaded obj file, and try to import it.

**System Information** Operating system: Windows 10 21H2 Graphics card: NVIDIA GeForce GTX 1650 **Blender Version** Broken: 2.79 (sub 0), branch: master, commit date: 2017-09-11 10:43, hash: 5bd8ac9 Worked: none, only tried 2.79 **Short description of error** I was trying to import this one specific obj file I exported from Marvelous Designer but it doesn't import and instead results in an error message in blender. Other obj files have been working but not this one for some reason. The error message in question (couldn't figure out how to copy the error message directly into here): ![image.png](https://archive.blender.org/developer/F13289835/image.png) [mima4.obj](https://archive.blender.org/developer/F13289837/mima4.obj) **Exact steps for others to reproduce the error** Exactly as how you would import any obj file: Files, Import, click Waveform (.obj), and then go the location of the downloaded obj file, and try to import it.
Author

Added subscriber: @udahn

Added subscriber: @udahn

Added subscriber: @scurest

Added subscriber: @scurest

2.79 won't get bugfixes anymore, but this works with the new OBJ importer in current 3.3 alpha. (Make sure you don't use the importer that says "(legacy)" because it's the same as in 2.79.)

The relevant part of the OBJ appears to be

cstype bspline
deg 1
curv 0.000000 0.000000
parm u 0.000000 0.000000
end

This is not valid according the OBJ spec btw. Of curv u0 u1 v1 v2 ... it says "v is the vertex reference number for a control point. [...] A minimum of two control points are required for a curve."

2.79 won't get bugfixes anymore, but this works with the new OBJ importer in current 3.3 alpha. (Make sure you don't use the importer that says "(legacy)" because it's the same as in 2.79.) The relevant part of the OBJ appears to be ``` cstype bspline deg 1 curv 0.000000 0.000000 parm u 0.000000 0.000000 end ``` This is not valid according the OBJ spec btw. Of `curv u0 u1 v1 v2 ...` it says "v is the vertex reference number for a control point. [...] A minimum of two control points are required for a curve."
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

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

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Thanks for the report.
As @scurest said, new importer imports your obj scene without any error. So please try that (get the latest builds from https://builder.blender.org/download/daily)
However problem remains in the old python importer.
@scurest , btw this is what I see in obj file (when I open it in notepad)

deg 1
curv 0.000000 450.733948 20021 20022 20023 20024..... (and more)
parm u 0.000000 0.000000 4.298655 8.704263 13.188544 ..... and more) ```
As far as i understand from [this](http://paulbourke.net/dataformats/obj/)- A minimum of two control points are required for a curve
Aren't control points more than two already? (I might have misinterpreted this)
Thanks for the report. As @scurest said, new importer imports your obj scene without any error. So please try that (get the latest builds from https://builder.blender.org/download/daily) However problem remains in the old python importer. @scurest , btw this is what I see in obj file (when I open it in notepad) ```cstype bspline deg 1 curv 0.000000 450.733948 20021 20022 20023 20024..... (and more) parm u 0.000000 0.000000 4.298655 8.704263 13.188544 ..... and more) ``` As far as i understand from [this](http://paulbourke.net/dataformats/obj/)- A minimum of two control points are required for a curve Aren't control points more than two already? (I might have misinterpreted this)

@PratikPB2123 There are several curves in the file. That one (line 97353) is okay. The one I'm talking about is at line 97160. If you comment out lines 97158-97162 the import succeeds.

@PratikPB2123 There are several curves in the file. That one (line 97353) is okay. The one I'm talking about is at line 97160. If you comment out lines 97158-97162 the import succeeds.

Is the Python addon still going to get bugfixes? How does that work?

Is the Python addon still going to get bugfixes? How does that work?
Member

If you comment out lines 97158-97162 the import succeeds.

yes, that worked.

The one I'm talking about is at line 97160

Thanks for clarifying :)

Is the Python addon still going to get bugfixes? How does that work?

I've asked about this in #blender-triaging channel

> If you comment out lines 97158-97162 the import succeeds. yes, that worked. > The one I'm talking about is at line 97160 Thanks for clarifying :) > Is the Python addon still going to get bugfixes? How does that work? I've asked about this in [#blender-triaging ](https://blender.chat/channel/module-triaging) channel

Added subscriber: @aras_p

Added subscriber: @aras_p

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'

The file imports correctly with the new 3.2+ OBJ importer. The Python based one will be removed soon, and meanwhile is very unlikely to get fixes. The file in question is technically invalid, i.e. the curve definition statement is not following the spec.

The file imports correctly with the new 3.2+ OBJ importer. The Python based one will be removed soon, and meanwhile is very unlikely to get fixes. The file in question is technically invalid, i.e. the curve definition statement is not following the spec.
Sign in to join this conversation.
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#99660
No description provided.