OBJ Imports related question

Comments

• Bejaymac Posts: 1,962

  February 12 edited February 12

  Wavefront OBJ is set to contain one mesh, all objects are set as mesh groups, and that is how DS imports them, one mesh with lots of mesh groups, as a result you only get one item in the scene tab.

  Studio's handling of the MTL file seems to change with the build, any changes to the Poser Importer (which the OBJ importer is part of) can cause pathing issues, safest way to get around this to make sure the pathways in the MTL are the absolute pathways to where the textures are stored on your system (including the drive letter).

  Post edited by Bejaymac on February 12
• crosswind Posts: 9,669

  February 12 edited February 12

  I've found no issue with both DS 2025 Alpha and 2026 Alpha when importing OBJ + MTL files. Diffuse texture maps are shown correctly in Viewport... There should be no change in OBJ Importer of DS 2026.... not sure why DS 2026 failed you. 

  As for grouping, starting from DS 2025 Alpha, OBJ Importer gives a new option of Read Objects, which can read OBJ file that contains Separate Objects. It now works well with my Blender workflow i.e. I save multiple items as an OBJ file with exporting materials in Blender, then DS 2025/2026 can import the OBJ file as multiple objects with assigned texture maps + correct surface names, so far so good ~

  But I know nothing about SketchUp... not sure if it can save an OBJ file with data of separate objects ...

   

  Post edited by crosswind on February 12
• da_kovacs Posts: 16

  February 12

  Well, I'm completely lost now. I've tried it with a completely new object with a simple texture and the same happens. The model is white... I thought of the MTL file as well, meaning that the pathfiles are either corrupted or something is missing, but creating a new model should've excluded this. I'm not sure what to do..it was working well before the update..

  Regarding grouping, it seems that SketchUp OBJ's don't separate objects, but exporting as 3DS do. I'll go with that instead.

   
• Richard Haseltine Posts: 108,900

  February 12

  Bejaymac said:

  Wavefront OBJ is set to contain one mesh, all objects are set as mesh groups, and that is how DS imports them, one mesh with lots of mesh groups, as a result you only get one item in the scene tab.

  DS can now import separate items.

  Studio's handling of the MTL file seems to change with the build, any changes to the Poser Importer (which the OBJ importer is part of) can cause pathing issues, safest way to get around this to make sure the pathways in the MTL are the absolute pathways to where the textures are stored on your system (including the drive letter).
• da_kovacs Posts: 16

  February 12

  Little update: I've noticed that only OBJ files are having this "white" issue. Exporting as FBX, DAE or 3DS all work perfectly fine and all come with object list as well. So, I'm not sure what's the problem with OBJs
• da_kovacs Posts: 16

  February 12

  Final update: First of all, I'd like to thank you all for your inputs on this. At the end it really made the difference. It was the MTL file all along. I've decided to delete the entire project, reorganize the files in folders and start everything from scratch. That did the trick. It turns out that somewhere along the way I might've removed something from the model I shouldn't have and therefore the pathway was broken. Now everything is back on track, OBJs are displayed correctly in DS so I can spend another week building the same scene :)).

  Cheers!
• Bejaymac Posts: 1,962

  February 14

  Richard Haseltine said:

  DS can now import separate items.

  Well going by the OPs post that's not happening, so I guess it only works on OBJ created with specific programs, which means 99% of the existing OBJ probably wont work with it either.
• Richard Haseltine Posts: 108,900

  February 14

  Read Objects needs to be checked in the import options dialogue, and they do need to be set that way in the OBJ (but if they import separately into other applications they probably are).
• da_kovacs Posts: 16

  February 17

  The thing is that even though it is said that DS can import separate items, for me this is not happening. As shown in the attachment, I have all settings checked. Is this option app specific maybe? I mean, I'm sure it works with Blender just fine, but as advised, I'm using SketchUp and with that, it doesn't work for sure.

  

  

  image_2026-02-17_013940264.png

  2559 x 1386 - 174K
• Richard Haseltine Posts: 108,900

  February 17

  And they are separate objects, not just separate groups, in SketchUp?
• da_kovacs Posts: 16

  February 17 edited February 17

  Most of them are grouped for better handling and organizational purposes. Sometimes, not grouping objects in SketchUp leads to messing up the geometry and whatnot. However, I've tried exploding some groups and leaving the objects as they are, but doesn't seem to be helpful.

  I've saved a version with no groups at all, just objects and oh boy.. not only that the file has no separate items in DS, but texture got lost and the project got white again :)).

  

  

  image_2026-02-17_024013713.png

  2559 x 1391 - 254K

  Post edited by da_kovacs on February 17
• Richard Haseltine Posts: 108,900

  February 17

  Within an object there are surfaces and groups, two differnt ways of dividing it up without splitting it apart. There may also be objects, separate items (thgough DS did not handle them until fairly recently). In addition, for textures you need UVs (which are not related to splitting the mesh up, they just specifity which area of a map gets aplied to a given polygon - however, removing material groupss might also remove the UVs)