Confusing about .obj .mtl .jpg

aleyciafrancis

Hello!Lovely guys in the forum!

Rookie question time again,LOL~~~

The question is How to Import a .obj file into DAZ ,and make its skin(or should I call it "Texture"?)  shows correctly.

For example, I got .obj .mtl and .jpg, 3 files , the .jpg looks like a peeled and spread out skin of this .obj,

In my imagine,this skin should cover the body(main frame?structrue? whatever...), so I put these 3 files into a new folder,then import the .obj file in DAZ,

but I found there is no any skin on the body...

How to make it right? guys! save my ass,please!!! LOL~~~ 

Ascania

Yes, and? DAZ Studio is well-known to have issues with applying the textures on obj import. Just do it by hand.

FenixPhoenix

Yes, like @Ascania mentioned, you can do it manually. Just open up the surface pane (window --> panes --> surfaces). With that open, once you select your object the surfaces will appear. You simply need to set your maps into the correct channels. So the color goes into diffuse, the spec goes into glossy or glossy weight, the normal goes into normal and bump goes into bump.

andya_b341b7c5f5

The .obj file should contain a reference to where the .mtl file is located.  The .mtl file should then have references to the .jpg files.  If there are not present, or incorrect, then the import will never be able to locate the texture files.  The file paths should not contain any spaces.  You can edit the .obj and .mtl files and correct the paths if necessary, they are just text files.

Aside from that, as long as the files are otherwise valid, Das Studio should at least load the texture defined for the base color

aleyciafrancis

FenixPhoenix said:

Yes, like @Ascania mentioned, you can do it manually. Just open up the surface pane (window --> panes --> surfaces). With that open, once you select your object the surfaces will appear. You simply need to set your maps into the correct channels. So the color goes into diffuse, the spec goes into glossy or glossy weight, the normal goes into normal and bump goes into bump.

Thanks for the reply~! phoenix~!

could you teach me more spacific?

Could you write down some steps and I will follow it,please!

aleyciafrancis

Ascania said:

Yes, and? DAZ Studio is well-known to have issues with applying the textures on obj import. Just do it by hand.

Thanks for the reply~Ascania!

The problem is I don't know how to put that skin on the object's body....LOL~~~

Could you write down some spacific steps ? I think I can follow it and make it done~

SpottedKitty

One of the problems is that the .obj file format has been around so long, different 3D programs have developed slight variations in the way they create and read the obj/mtl file pairs. One of the more common is that the .mtl file gives absolute path links to any texture files that exist on the object creator's computer. There's a vanishingly small chance that the same folder paths will exist on your computer for one-click import into DAZ|Studio, so it's important to learn how to fix these glitches when they happen. It's not as difficult as it sounds; almost all of the .obj and .mtl files you'll come across will be plain text, so you can easily spot glitched file paths and alter them to something that will work when you copy the files into your content location.

Ascania

http://docs.daz3d.com/lib/exe/fetch.php/public/software/dazstudio/4/userguide/daz_studio_4_x_user_guide.pdf

Chapter 3 explains it, with pictures,

Ascania

SpottedKitty said:

One of the problems is that the .obj file format has been around so long, different 3D programs have developed slight variations in the way they create and read the obj/mtl file pairs.

Counterargument: The .obj file format has been around for so long and the variations on the obj/mtl reading so established that there is no reason for a program not to support reading all of them.

SpottedKitty

Ascania said:

Counterargument: The .obj file format has been around for so long and the variations on the obj/mtl reading so established that there is no reason for a program not to support reading all of them.

That's the sensible way to do things, but D|S has always been very fussy about the file path formats it'll accept in a .mtl file material definition. Also, it doesn't help much importing an .obj into D|S if it was created in, say, Lightwave or Maya, and the texture file folders are set up for that program. Do this long enough and you'll end up with folders of textures scattered all over your hard drive instead of neatly tucked away in /Runtime/Textures/. I've got into the habit of always checking texture paths whenever I'm about to import anything that isn't a D|S native file format.

Ascania

SpottedKitty said:

Ascania said:

Counterargument: The .obj file format has been around for so long and the variations on the obj/mtl reading so established that there is no reason for a program not to support reading all of them.

That's the sensible way to do things, but D|S has always been very fussy about the file path formats it'll accept in a .mtl file material definition. Also, it doesn't help much importing an .obj into D|S if it was created in, say, Lightwave or Maya, and the texture file folders are set up for that program. Do this long enough and you'll end up with folders of textures scattered all over your hard drive instead of neatly tucked away in /Runtime/Textures/. I've got into the habit of always checking texture paths whenever I'm about to import anything that isn't a D|S native file format.

Frankly, if I intend to re-use an .obj in D|S (yay, someone else still writes it the correct way :D) then I take the time to set it up and save it to my library, including sorting out the texture paths. Just to spare myself the hassle of having to do it again later.