the old flogged to death obj and FBX export subject

WendyLuvsCatz

once again I am finding extremely annoying export issues with UV mapping and textures to other apps on some sets.

and have no easy answers just more questions

the latest PITA is Powerage's Old Town Bordeaux.

I finally got it as all one obj into Carrara and unticked UV wrap in the vertex room and it mapped correctly but a damned big obj with many maps.

duf and other options failed badly

In Poser and iClone no luck.

Increasingly DAZ products are not only D|S only but it seems you cannot even export a useable obj to other applications.

I am not blaming the PA's as they make them to work in D|S as required and they do fine, its a D|S export issue.

The plugins need more options to cover stuff like UV wrap on x and z axis etc and D|S badly needs a texture bake option for procedural iray and 3Delight shaders that will use either renderer to render a texture baked to the model's UV for use in other apps.

 

 

my video in Carrara after a hellava lot of fluffing around!

below how it loads in Poser, iClone the same

wolf359

Hi this is not a daz studio problem. If your recieving application has a rubbish .obj importer you will always have these difficulties. Daz has an excellent obj exporter with many presets for proper scaling in other applications. The problem is that these recieving applications dont have well developed obj import options and frankly do not even seem to care. Even the $3600 dollar Maxon Cinema4D that I use to render all of my exported Daz content has a rubbish obj importer which is why I use a powerful third party plugin for C4D that has many options including a requestor for the file path of the textures of the obj file referenced in the. Mtl file. Programs like poser and Iclone are purpose built to use their internal native content and will likely never have complete import options

hphoenix

wolf359 said:

Hi this is not a daz studio problem. If your recieving application has a rubbish .obj importer you will always have these difficulties. Daz has an excellent obj exporter with many presets for proper scaling in other applications. The problem is that these recieving applications dont have well developed obj import options and frankly do not even seem to care. Even the $3600 dollar Maxon Cinema4D that I use to render all of my exported Daz content has a rubbish obj importer which is why I use a powerful third party plugin for C4D that has many options including a requestor for the file path of the textures of the obj file referenced in the. Mtl file. Programs like poser and Iclone are purpose built to use their internal native content and will likely never have complete import options

Actually, the Wavefront|Alias OBJ format is very straightforward, simple, and pretty easy to implement an importer or exporter for.

The problem is various OTHER entities keep trying to extend it to add in additional data/parts/etc. to bring it forward into the 21st century.  The Wavefront OBJ format is quite old.

Everytime one place extends it, another importer breaks.  Their export no longer matches the standard.  While it should technically just ignore anything it doesn't support, that doesn't always work.

 

WendyLuvsCatz

I feel as though its a duf format issue as the uv unwrap issue occurs with duf files from Studio in Carrara too, Poser used obj or pp2 or obz I only have this issue with some duf only files, a reimport of the obj into D|S has the same issues I might add.

WendyLuvsCatz

I must add an important note here

99% of exports are fine!!!

its mainly Stonemason and a few other PA's products such as this Powerage set that do it.

What is worrying is its becoming more frequent with new content.

Mattymanx

As someone who use to convert a lot of models from one format to another, (MAX, LWO & 3DS to OBJ) I can tell you from experiance that its not always the mesh but how the parent program allows shaders and textures to be used on any given surface.  Because we build our models for use in Daz Studio, Iray and 3Delight become governing factors in what we do.  There are things that can be done in those two engines that work great for those engines but dont work for any other render engine.  The same is true for Poser's Material Room.  Presets saved out from it that can do wonders in Poser do not work at all in Daz Studio.

 

So what you are experiancing is nothing new or unique.  Its the bane of all those who wish to convert from one format to another or take a model from its "native" application to a different one.  Think of it like languages.  Your native language works great in your home country but not so much, or at all, in another.