Loading...
> >

another obj mtl file question

WendyLuvsCatzWendyLuvsCatz Posts: 41,147
in Daz Studio Discussion

OK

my meshes created by Hunyan 3D AI and converted fron glb to obj with PConPlanner the other day, import into DAZ Studio textured

today's batch don't 

both sets are in runtime textures folder so D|S can refind them after saving duf files

# created with pCon.planner

newmtl mat__473a7d2e
Ka 0.41350016 0.35234278 0.35280597
Kd 1 1 1
map_Kd f60c08f32dbc1722.png
Ks 0 0 0
Ns 0
illum 2

works

 

# created with pCon.planner

newmtl mat__3118bd15
Ka 0.46559992 0.38622758 0.34440079
Kd 1 1 1
map_Kd fa22843a1b20b130.png
Ks 0 0 0
Ns 0
illum 2

doesn't 

can anyone see what I am missing?

Comments

  • WendyLuvsCatzWendyLuvsCatz Posts: 41,147
    edited June 26

    this gets stranger, the first figure I generated today loaded textured

     

    # created with pCon.planner

    newmtl mat__f35b7851
    Ka 0.35568827 0.18462712 0.13991484
    Kd 1 1 1
    map_Kd a9f13ded486d3506.png
    Ks 0 0 0
    Ns 0
    illum 2

    not hard to drag and drop the textures into base colour on iray uber, but still

    Capture2.PNG
    1920 x 1040 - 404K
    Post edited by WendyLuvsCatz on
  • Richard HaseltineRichard Haseltine Posts: 110,751

    Are those the surfacews names? I can't recal the details for MTL files. Do they match the surface names shown in DS, and the original names from creation?

  • WendyLuvsCatzWendyLuvsCatz Posts: 41,147
    edited June 26

    not on my PC right now

    (in bed on iPad)

    but PConPlanner actually generates those png files from loading the glb file

    I did exactly the same thing, (it is my default program for opening glb files)

    just export an obj after it loaded it

     

     oh one difference 

    my first 10 or so files were generated from image prompts

    the rest from descriptions but the first one loaded textured

    just the ones after didn't, very mysterious 

    I am guessing you are right, the surface names or something doesn't match

    would be one of the other programs not D|S

    will check later

    Post edited by WendyLuvsCatz on
  • Richard HaseltineRichard Haseltine Posts: 110,751

    Check for spaces in the group/surface names - strictly OBJ doesn't allow those 9theya re treated as separators) but some applications allow them. I can't see a space in the name in the MTL, though.

  • WendyLuvsCatzWendyLuvsCatz Posts: 41,147
    edited June 27

    the material names match

    I am stumped

    its OK but this doesn't help me one bit in knowing what D|S looks for in the mtl file

     

    I even tried renaming the texture and editing the mtl file 

    sharing 2 zips, one works, one doesnt

     

    zip
    zip
    emperor.zip
    4M
    zip
    zip
    Roman peasant.zip
    4M
    Post edited by WendyLuvsCatz on
  • crosswindcrosswind Posts: 9,896
    edited June 27

    When saving OBJ file with MTL, never leave any space character in between words. Type a dash instead, e.g. Roman peasant.obj, has to be Roman_peasant.obj. Then MTL file will be Roman_peasant.mtl that can be correctly loaded.

    In your case, if you rename Roman peasant.mtl to Roman_peasant.mtl, then open Roman peasant.obj with Notepad++, line 3, replace mtllib Roman peasant.mtl with mtllib Roman_peasant.mtl, it'll also work.

    Post edited by crosswind on
  • WendyLuvsCatzWendyLuvsCatz Posts: 41,147

    crosswind said:

    When saving OBJ file with MTL, never leave any space character in between words. Type a dash instead, e.g. Roman peasant.obj, has to be Roman_peasant.obj. Then MTL file will be Roman_peasant.mtl that can be correctly loaded.

    In your case, if you rename Roman peasant.mtl to Roman_peasant.mtl, then open Roman peasant.obj with Notepad++, line 3, replace mtllib Roman peasant.mtl with mtllib Roman_peasant.mtl, it'll also work.

    oh wow, thats it,

    you solved it yes

    my first lot were all numbers with _because that's how Gimp saves files split from images namely the Colosseum equites billboard texture I used

    my prompt generated meshes were all Roman something except the emperor one that works! 

  • crosswindcrosswind Posts: 9,896

    Great ! yessmiley

  • BejaymacBejaymac Posts: 1,989
    edited June 27

    Just to add that this isn't new behavior by DS, I've been using DS for roughly 20 years at this point and it's always hated spaces, and not just in pathways and file names, spaces in mesh group names and in Surface names have the same effect.

    Some programs give you generic surface names like Material 01, Material 02, Material 03, all DS sees is Material and lumps them all together as one surface at import.

    Post edited by Bejaymac on
  • Richard HaseltineRichard Haseltine Posts: 110,751

    Bejaymac said:

    Just to add that this isn't new behavior by DS, I've been using DS for roughly 20 years at this point and it's always hated spaces, and not just in pathways and file names, spaces in mesh group names and in Surface names have the same effect.

    That is, as I said, part of the OBJ definition - space is a separator. I wasn't aware it affected pathnames too (though they would require quotes even in an OS command line to avoid their being treated as separate entities).

    Some programs give you generic surface names like Material 01, Material 02, Material 03, all DS sees is Material and lumps them all together as one surface at import.

Sign In or Register to comment.