FBX import

Hello,

Today I am trying to import a free FBX file downloaded from the CGAxis site.

If I import it into Blender or 3DCoat this object is perfect in terms of assembly, textures and spatial orientation.

But on Daz3D, this same object is completely disassembled and all the elements are separated without logical orientation.
Is there a way to import an FBX file with all components correctly oriented?

 

 

Capture d’écran 2022-12-29 060900.png
1157 x 591 - 376K

Comments

  • use their obj option and set the opacity on all the surfaces to 100%

  • Hi, I thank you for this quick answer.

    I import it as an OBJ file, but in this case I need manually import map and I have some artefact results with that.

    Is there a way to automatically import the maps correctly?

    Capture d’écran 2022-12-29 063538.png
    1486 x 926 - 634K
  • possibly not, DAZ fussy about mtl files you may have also applied the wrong map

    I have bought and used lots of CGaxis models myself but saved them as props in Poser (the pp2 props work in D|S too) so cannot really help there

  • omni-moulageomni-moulage Posts: 17
    edited December 2022

    Thank you so much because you gave me the idea to export from 3d Coat as an OBJ file with texture.

    And now Daz3D reads the OBJ file with the correct mapping and positioning of the assembled elements.

    I just have a problem regarding the artifact on the chair, but when I change the value of the "bloor filter radius", this artifact disappears. (ok now the color seems pale...)

     

    Edit:

    I just found a better solution to avoid artefacts by modifying the "Base Mixing" on "Weight instead "PBR"

    bloom filter radius on.png
    757 x 892 - 425K
    Base Mixing.png
    1401 x 816 - 712K
    Post edited by omni-moulage on
  • that's good because if I recall Blender obj export I get the same issue as the mtl file hasn't got paths in quotations so no textures load

  • lilweeplilweep Posts: 2,487
    edited December 2022

    omni-moulage said:

    Thank you so much because you gave me the idea to export from 3d Coat as an OBJ file with texture.

    And now Daz3D reads the OBJ file with the correct mapping and positioning of the assembled elements.

     

    that file on cgaxis comes with a spec map.

    You are really putting a lot of faith in OBJ material definitions to assume it automatically put that Spec map in the right slot for the Daz Iray uber shader, to say nothing of the other values that might have been adjusted by the .mtl file.

    A better workflow is to just export from cgaxis as obj and then import into Daz as Obj (i would uncheck the read material definition option) and then manually drag/drop the Texture maps into the slots on the Surfaces tab and then manually tweak the values to your liking.  

    Post edited by lilweep on
  • when DAZ loads maps it DOES load Specular maps, under glossy reflectivity if I recall

    actually it sometimes loads all the maps including normals depending what I exported it from

    a rare but not unheard of occurance 

Sign In or Register to comment.