OBJ import - same named .obj entries are appended to one mesh / not extra objects #54362

Closed
opened 2018-03-19 16:06:26 +01:00 by blender user #1436282 · 6 comments

System Information
any sys, any card

Blender Version
Broken: blender-2.79.0-git.0301df4 also official 2.79a
Worked: I don't think so

Importing example file problem.obj does not result in different objectsobj_problem.zip

Exact steps for others to reproduce the error

  • open default scene, remove all
  • import probem.obj with options:
    • split: checked "Objects", checked "Keep Vert Order"
  • result: one object in blender with 4 screw meshes
    • should be individual objects, like

this is just to show/clarify the problem:

  • import problem_edit.obj (which was edited in text editor to unique named "g ......" lines
  • result: invdidual objects (as there are invdividual names)

same named .obj objects should not be inside one mesh

**System Information** any sys, any card **Blender Version** Broken: blender-2.79.0-git.0301df4 also official 2.79a Worked: I don't think so **Importing example file problem.obj does not result in different objects**[obj_problem.zip](https://archive.blender.org/developer/F2464834/obj_problem.zip) **Exact steps for others to reproduce the error** * open default scene, remove all * import probem.obj with options: * split: checked "Objects", checked "Keep Vert Order" * result: one object in blender with 4 screw meshes - > should be individual objects, like this is just to show/clarify the problem: * import problem_edit.obj (which was edited in text editor to unique named "g ......" lines * result: invdidual objects (as there are invdividual names) same named .obj objects should not be inside one mesh

Added subscriber: @Linuz

Added subscriber: @Linuz
Member

Added subscriber: @LazyDodo

Added subscriber: @LazyDodo
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Ray molenkamp self-assigned this 2018-03-19 16:35:29 +01:00
Member
  1. the .obj specifications are rather vague and do not mention what is supposed to happen with duplicate names.
  2. ue4 does the same thing with these files.

So this i'd have to classify this as a feature request and not a bug. while we love to hear feature requests, this is not the right place for them. This website is mainly used to track bug reports and not feature requests. But there are some other nice solutions you can take, so please use one of the other forms of communication listed below:

https://rightclickselect.com/
Fun board mailing list: https://lists.blender.org/mailman/listinfo/bf-funboard

1) the .obj specifications are rather vague and do not mention what is supposed to happen with duplicate names. 2) ue4 does the same thing with these files. So this i'd have to classify this as a feature request and not a bug. while we love to hear feature requests, this is not the right place for them. This website is mainly used to track bug reports and not feature requests. But there are some other nice solutions you can take, so please use one of the other forms of communication listed below: https://rightclickselect.com/ Fun board mailing list: https://lists.blender.org/mailman/listinfo/bf-funboard

Added subscriber: @Foaly

Added subscriber: @Foaly

I'd say this is not a bug.
The same group name can apparently be reused, and refers to the same group.

At least that's what this spec seems to imply: http://www.martinreddy.net/gfx/3d/OBJ.spec
See the example "Cube with group names", it states that "all elements belong to the group cube". And the g statement is used multiple times.

However it might be worth considering to split even with the same name as a work around. But I guess this is rather a bug in the exporter.

I'd say this is not a bug. The same group name can apparently be reused, and refers to the same group. At least that's what this spec seems to imply: [[ http://www.martinreddy.net/gfx/3d/OBJ.spec ]] See the example "Cube with group names", it states that "all elements belong to the group cube". And the g statement is used multiple times. However it might be worth considering to split even with the same name as a work around. But I guess this is rather a bug in the exporter.
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 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#54362
No description provided.