I bought a couple of models on Turbosquid. I chose the obj format and imported them into Poser 10.

The problem is that the textures do not appear, even if the mtl file is in same folder with the obj file.

Any idea as to what I am doing wrong?

I'm not seeing any issues importing .obj files with textures. I'm using Poser Pro 2014, but can't see how it would behave differently than 10.

Are the paths to textures specified in the .mtl file are valid?

If you edit the material on the imported object, is the texture available in the Texture Manager window?

The models in question did not come with separate texture files beyond the mtl.

So does this mean I will have to edit the files manually?

Oh. My bad. I was thinking you had image textures you were expecting to show up. In that case maybe you do need to edit the file manually. Maybe check the .obj and see if the path to the .mtl file for the mtllib keyword is valid and there is a material name in the .mtl file is used for the usemtl keyword?

When I have had this issue in the past I have often solved the problem by loading the object into Bryce or Silo and saving it under another name and then loading that into Poser. I have no idea why this should work I just know it has on occasions in the past.

dardezen posted at 9:58AM Tue, 02 February 2016 - #4252624

Oh. My bad. I was thinking you had image textures you were expecting to show up. In that case maybe you do need to edit the file manually. Maybe check the .obj and see if the path to the .mtl file for the mtllib keyword is valid and there is a material name in the .mtl file is used for the usemtl keyword?

I did. From what I see, it looks OK.

If I sent one of you the files in question, could you see that's going on?

The object file contains the material zones. The mtl files tell what textures to load on what material zones. The textures,

So at minimum, you need at least 3 files. => The obj, the mtl and the texture.

What vilters said. I just trash the .mtl file generated from my modelers and load my textures manually in poser. I also strip the mtllib reference out the the .obj, clean up and/or rename g or usemtl entries if necessary. No need for cluttered up .obj's with external app whatnots, or even the # comments that poser clutters them up with. Take control of your files and you'll have no surprises/mysteries... it's all text.

All good advice here.

Supplying the files would definitely help, but probably not suggested since you purchased them and likely aren't supposed to share them. Or maybe have a free one that shows the same problem.

I like what tonyvilters is pointing out. If you are expecting an image texture and don't have at least 3 files (.obj, .mtl and .jpg|.png), then stop now. It doesn't matter what the .mtl file is pointing to; you're simply missing the image for the texture.

When you mentioned you didn't have texture files outside of the .mtl file, I assumed that was supposed to be the case and that you were using "texture" for what I would probably just call material and then suggested options to figure that out. My bad.

I'd check out hornet3d and EldritchCellar's suggestions as well. The great thing about .obj and .mtl as text file formats is that they are super simple.

Came to this thread very, very late, but a couple of thoughts...

Some modelling apps hard-code MTL's path into OBJ, so it is not accessible without a hunt. Fortunately, Windows' bundled Wordpad will open even huge OBJs. You can watch the % grow as load progresses, then the MTL reference will be visible in first few lines. Carefully edit out extraneous path stuff, save with a smile.

Similar issues with MTL files, whose map-files may have both hard-coded paths and quotes, all unwelcome. Notepad will do for this clean-up...

( One of these days, I'll figure the 'mapping' between MTL and MC5 ...)

None of the referenced texture files included ? Yeah, met such. My kindest take is author suddenly realised those lovely textures were not a 'merchant resource', could not be 'sold on' without getting an extended license. Often, I suspect author completely forgot those files were in a 'library' far, far away from WIP's Runtime...

I've had some luck using eg Google Images to find those named files. Sometimes, folder tree names give a clue to which on-line free texture library contributed. I have resorted to contacting authors, asking what a particular BMP resembled, and what size. Often, I've had a reply with links or attachments...

One wry 'gotcha' is when you import an OBJ and Poser finds its MTL, then prompts for texture files with different, shorter names to those supplied.

This bug, which I've called in, dates all the way back to P3/P4. Just 'left arrow' in the prompt field and the leading characters of name will show up, too. ;-)

Now, why could the forum search engine not find my comment above ?? D'uh...

Belatedly thinking laterally, there's another possible explanation for missing textures: Some MMD PMX artists habitually set their models' texture folders to 'hidden' in Windows' File Explorer. ( They'll also 'mung' the PMX geometry which, IMHO, is a different bucket of stinky 'chum'...)

If an OBJ+MTL artist did this, and original path was 'baked' into OBJ+MTL, you would have to edit those paths and un-hide such covert folder(s)...