In the latest daz studio I find that materials are not importing correctly to other apps. The material files look the same as older obj's that import materials correctly, however, the obj files are now different sizes for the same exact file export, which results in all gray default textures on import in another app.In 1.2 it worked in new update this is what happens. If I import either obj (new or old) into DAZ Studio maps are missing. Anyone else notice this?

I see others had same problem. I do see that D|S show invalid path so it must be a relative path that is now lost due to some change.

OK...DAZ says this will be updated to be more friendly(I guess more options?). They closed this so I am posting my simple solution here. For anyone who cares. In my case the addition of quotes in the mtllib statement in obj caused disappearance of textures. I would still like to see an option for full paths rather than relative. DAZ says both the mtllib statement in obj needs to be be FULLY supported(in my case, quotes vs non quotes :D apparently some syntax change has occurred)Also the support for proper mtl file reading. MUST HAVE BOTH. DAZ apparently doesn't fully support it's own exported mtl. That's from which all my D|S import errors seem to be originating. I don't know what they were thinking there. (Maybe you would never import and exported D|S obj?)

I don't know what they were thinking, either. The import/export function doesn't do half the stuff you're supposed to be able to do, including maintaining object grouping. I was really looking forward to integrating this into my content development workflow, and I'm back to square one.

This looks interesting it's free...will have to try it. http://scratchcomputing.com/projects/uber-converter/

'I was really looking forward to integrating this into my content development workflow, and I'm back to square one' I'd advise you to wait a while before giving up hope. I'm assured by rob that content creators haven't been forgotten, and there will be tools for us. I imagine that once the SDK is finalised, more options will be available. I had the same problems with obj files, and reported them. A fix has been made for the next release, but I have the distinct feeling that we haven't seen the full picture yet. Rob appears to have several things up his sleeve which he's not showing. mac

Absolutely not giving up, just really disappointed. Having the ability to select how parameters are read and written would have eliminated the extra step of "prepping" the .obj file so that it will export with proper node groupings (e.g. for use in creating morphs with D-formers). I'm SO glad I haven't had other problems that some folks have posted about. The "doubling morphs" bug is also a PITA, especially since I was working on superconformers at the time, and really don't want to have to reinstall an older version to eliminate the problem.

I think it just gets frustrating when it seems they don't see the forest for the trees. We know they use their own sw, but some of this should be blatantly obvious.Altho...they are not the only sw developers to exhibit this. D|S is free so I cannot protest too much.

Message edited on: 02/04/2006 16:34