Wavefronts do not load or save
rhye_7b205b2b74
Posts: 89
What has happened to Daz3d since W10, every wavefront I create as a wavefront from it becomes unusable and anything I now bring into it is invisible, I have tried using the basic settings with no materials, which work so I can load gf3 into Marvelous Designer, but when I create a wavefront person with clothes/no clothes with mtl etc it loads it back in either invisible or grey?
Win 7 works but making a Daz Win7 object still has the same problems when loading into the latest Daz3d ?
Just to point out the Win7 version is Daz 4.10 btw
Post edited by rhye_7b205b2b74 on
Comments
Wavefront OBJ is usually abbreviated to OBJ - it's shorter, and the actual extension that appears in the fiel name, so I assume that is what you mean. Are you exporting from or importing to DS? I haven't done a lot of OBJ-handling but can't say I have seen this, using WIndows 10 and the then current version of DS (4.12.1.117 now).
Yes wavefront is abreviated to .OBJ, the latest daz3d does not create anything usable any more, a grey basic obj is all it can do. Win10 has a 3D Object veiwer and I get a good idea from that if it has created a .OBJ properly, as I said if I create a figure with clothes hair etc and export it with daz3d info attached, the new daz makes it invisible???
DS to MD9 is working, and bringing over textures, for me in 4.12.1.117 - I used the Daz Studio preset which made the model too small though.
Thanks Richard I have GF3 successfully exported and importing the clothing back into Daz is fine, it is that I like to create background people by turning them into OBJ and then import them back into daz, this is the problem daz does not recognise its own exporting code, they are invisible and previous ones I created that worked in daz 4.10 come in grey ??
Very frustrating problem, all the posts on this forum never actually answer the problem, they just say you have to import into blender or some other 3d app to get it to read the mtl files?
Someone somewhere must have the answer ?
The export loads for me, with base maps applied - the materials wll need reworking (the opacity on the eye surface needs to go back to 0, anything but the basic settings gets lost in the OBJ export) but the basic maps have reapplied. What settings are you uisng for Export and Import?
I've had a lot of experience with all the ways an .obj import into DAZ|Studio can go wrong. When this happens, it usually means there's some kind of mismatch in the import/export settings. D|S is very fussy about the exact file format for .obj materials — it will quite happily export a .mtl file that it can't read properly.
Have you tried loading the exported model into a converter such as PoseRay? Or opening the .obj and .mtl in a text editor to make sure the file/folder paths are actually correct?
Thanks Spotted that helped big time, opening the mtl files in notepad showed me the problem!
I went through all the options and found the export to use is *Carrera* with scale 100% and Collect Maps enabled.
Daz places all the materials in the mtl file into the attached Map folder alongside the wavefront created, the actual Daz export does not create a Map folder ito reference it just points it all back to the MyDaz texture files it found them, when Daz imports it, it obviously only looks for the Maps files in the Wavefront figure's Map file, hence Grey figure.
The Clothes and Eyes are the next obstacle, but you can go to the original textures in Surfaces and load them.
It is strange how 4.10 and 4.8 never had this problem though?
Thanks Richard :)
Cutting the opacity of the Cornea in the imported works too!