Accurate Skin textures possible?

Is it possible to get accurate skin textures for G3F? Until now I have just skin texures that are not accurate and I have a lot for G3F bought here at DAZ. On some you can see the body/arm borders on others you can see the the body/leg borders on some ýou can see all borders body/arms body/legs. I do not get it why that is so but most skin textures I have for V4 are more accurate than what I have for G3F and it begins with the skin texture of V7, also this is not accurate.

«1

Comments

  • I haven't noticed this - is this in Iray or 3Delight (I guess the latter)? Are you using the correct materials for that render engine, if both are included? Are you using the default SubD algorithm or one of the others, and if one of the others does switching back to Catmark help?

  • cosmo71cosmo71 Posts: 3,609

    I haven't noticed this - is this in Iray or 3Delight (I guess the latter)? Are you using the correct materials for that render engine, if both are included? Are you using the default SubD algorithm or one of the others, and if one of the others does switching back to Catmark help?

    I render in 3Delight and use the 3Delight textures (shader) but without SSS but that should not matter, the borders you have, it is the diffuse map (Jpeg Image) issue, the textures themself I have not edited, just the diffuse color and strength but for all I have the same values, arms, legs, body and also with original values you have these borders, most of the time you can you have them on the backsite of the character.

  • cosmo71cosmo71 Posts: 3,609

    As written it is a core issue of the Jpeg images and has nothing to do with values or colors of the surface tab.

  • jestmartjestmart Posts: 4,449

    I haven't seen this either.  Do you have Gamma Correction switched on in the Render Settings?

  • cosmo71cosmo71 Posts: 3,609
    edited February 2016
    jestmart said:

    I haven't seen this either.  Do you have Gamma Correction switched on in the Render Settings?

    folks, a visible border is a visible border and it comes from the diffuse jpeg image and from nothing else because the values of gamma corrections or what ever else is for all surfaces in the scene the same. If the body surface and the arm surface for exmaple have the same values in the surface tab there should be no border if the the texture itself (the jpeg images) are accurate.

    borders.jpg
    1680 x 1050 - 251K
    Post edited by cosmo71 on
  • frogimusfrogimus Posts: 200

    Is this possibly from torso and limbs having different resolutions? IIRC, there was a similar thread about noticable seams/surface changes between head and neck.

  • cosmo71cosmo71 Posts: 3,609
    frogimus said:

    Is this possibly from torso and limbs having different resolutions? IIRC, there was a similar thread about noticable seams/surface changes between head and neck.

    yeap on some skin textures you have also a noticable seam between neck and head

  • SzarkSzark Posts: 10,634

    what is your Render Settings > Shading Rate set to?

  • cosmo71cosmo71 Posts: 3,609

    loaded from scratch

    borders 2.jpg
    1680 x 1050 - 283K
  • cosmo71cosmo71 Posts: 3,609
    Szark said:

    what is your Render Settings > Shading Rate set to?

    Sark, loaded from scratch without rendering and you have seams so what has the shading rate to do with it? Answer: Nothing.

  • cosmo71cosmo71 Posts: 3,609

    It is just bad texturing

  • SzarkSzark Posts: 10,634

    ok just trying to help..

  • Cosmo, your attachments are showing screen captures of the viewport.  A texture in the viewport often gives a false impression of how it will eventually look when rendered.  It is just an approximation.

  • HavosHavos Posts: 5,609

    I think the point Szark was making was that it does not really matter if you see differences in the viewport if the final render is seam free.

    Having said that I have been through the 10 G3F skins I have and I am not seeing any seamlines between the arm and the shoulder in my viewport view. However I do not have Rahele, so I can not comment on that skin.

  • cosmo71cosmo71 Posts: 3,609
    Szark said:

    ok just trying to help..

    well thank you for that but I think without rendering the shading rate has no influence and if you have seams during pre render work and after rendering I guess it is not a shading rate issue

  • cosmo71cosmo71 Posts: 3,609
    edited February 2016
    Cayman said:

    Cosmo, your attachments are showing screen captures of the viewport.  A texture in the viewport often gives a false impression of how it will eventually look when rendered.  It is just an approximation.

    it looks equal (the seam) pre render and render you have the seam. Believe me, If I would just have the seam in the pre render scene I would not write any comment on this issue but the seam is also in the rendered scene visible. And Rahele was just an example, there are other textures of other G3F characters having the same issues with seams on arm/body or leg/body or neck/body or all. It is not a critical comment to just one vendor. It is a general statement on texturing.

    Post edited by cosmo71 on
  • cosmo71cosmo71 Posts: 3,609
    cosmo71 said:
    Cayman said:

    Cosmo, your attachments are showing screen captures of the viewport.  A texture in the viewport often gives a false impression of how it will eventually look when rendered.  It is just an approximation.

    it looks equal (the seam) pre render and render you have the seam. If you have a seam in the  pre render you also have a seam in the renderd scene.

     

  • I have this character and the seam is visibile for me in the view port with the default loading of the character and it is also visible in the render I did with Iray.  Probably best to open a ticket for it.

  • Are you sure you are using the current version of Rahele? I was not seeing any issues in the viewport with the Iray or 3Delight materials, I do think there was a fairly  recent update however (which I have installed).

  • mjc1016mjc1016 Posts: 15,001

     

    cosmo71 said:
    Cayman said:

    Cosmo, your attachments are showing screen captures of the viewport.  A texture in the viewport often gives a false impression of how it will eventually look when rendered.  It is just an approximation.

    it looks equal (the seam) pre render and render you have the seam. Believe me, If I would just have the seam in the pre render scene I would not write any comment on this issue but the seam is also in the rendered scene visible. And Rahele was just an example, there are other textures of other G3F characters having the same issues with seams on arm/body or leg/body or neck/body or all. It is not a critical comment to just one vendor. It is a general statement on texturing.

     

    I have this character and the seam is visibile for me in the view port with the default loading of the character and it is also visible in the render I did with Iray.  Probably best to open a ticket for it.

    Being more specific tends to get quicker results...

    Cosmo, be specific with which skins are having problems, that way if someone else has the same set, it can be confirmed if it is a configuration issue or an actual problem with texture.

  • OK, I do see an issue in the rendered version under Iray at least, so yes open a support ticket please.

  • Clearly a problem with the texture; in the excerpt below where i overlayed neighboring arm- and torso-islands of the texture, it can be seen that the arm is a few ticks brighter than the torso. In the image it reads "Master Skin Resource by 3Dream" which seems to be a product at renderosity. Perhaps all textures derived from that product have the same problem. 

     

    rahele-overlap.png
    936 x 762 - 410K
  • cosmo71cosmo71 Posts: 3,609
    edited February 2016
    mjc1016 said:

     

    cosmo71 said:
    Cayman said:

    Cosmo, your attachments are showing screen captures of the viewport.  A texture in the viewport often gives a false impression of how it will eventually look when rendered.  It is just an approximation.

    it looks equal (the seam) pre render and render you have the seam. Believe me, If I would just have the seam in the pre render scene I would not write any comment on this issue but the seam is also in the rendered scene visible. And Rahele was just an example, there are other textures of other G3F characters having the same issues with seams on arm/body or leg/body or neck/body or all. It is not a critical comment to just one vendor. It is a general statement on texturing.

     

    I have this character and the seam is visibile for me in the view port with the default loading of the character and it is also visible in the render I did with Iray.  Probably best to open a ticket for it.

    Being more specific tends to get quicker results...

    Cosmo, be specific with which skins are having problems, that way if someone else has the same set, it can be confirmed if it is a configuration issue or an actual problem with texture.

    how can it be a config issue when loading the figure from scratch, have the seam without rendering and with rendering?????? Think about it.

    Post edited by cosmo71 on
  • cosmo71cosmo71 Posts: 3,609
    edited February 2016

    Other thing. If you see a seam between body and arm in the pre render scene for example you will see the same seam also in the rendered scene no matter what your configs and values are because it is a core texture issue (Jpeg files). So more accuracy on texturing is requeired.

    Post edited by cosmo71 on
  • cosmo71cosmo71 Posts: 3,609
    edited February 2016

    OK, I do see an issue in the rendered version under Iray at least, so yes open a support ticket please.

    Well I guess I have the latest version because I have bought the character two days ago and have no updates for this character in the dim

    Post edited by cosmo71 on
  • mjc1016mjc1016 Posts: 15,001
    cosmo71 said:
    mjc1016 said:
     

    how can it be a config issue when loading the figure from scratch, have the seam without rendering and with rendering?????? Think about it.

    Because there could be a simple fault in the surface settings...

    Something like the 'base' color for the torso being 248 248 248 and the limbs being 255 255 255.

    THAT is a config issue.

  • mjc1016 said:
    cosmo71 said:
    mjc1016 said:
     

    how can it be a config issue when loading the figure from scratch, have the seam without rendering and with rendering?????? Think about it.

    Because there could be a simple fault in the surface settings...

    Something like the 'base' color for the torso being 248 248 248 and the limbs being 255 255 255.

    THAT is a config issue.

    I seelct both arm and torso surfaces in Rahele and looked through the Surface pane settings - there were no <?> entries indicatind different numeric values. I then went through the images checking the settings in Image Editor for each pair of maps - again there were no mismatches. So in this case I think it as Cosmo says, a difference in one or more of the textures themselves.

  • HavosHavos Posts: 5,609

    cosmos71 seems to imply at the start of the thread that this was an issue for many G3F skins, if this is the case are there any other issues you can see with other G3F skins other than just Rahele? Between us all we probably have the same skins, so we can look to see if we can see the same things.

  • nicsttnicstt Posts: 11,715

    I've had the same happen. I raised a ticket, but closed it as can't always repear; sometimes they only show up if I alter a texture and re-save; when that occurs it's to do with the specular texture.

  • cosmo71cosmo71 Posts: 3,609
    edited February 2016
    mjc1016 said:
    cosmo71 said:
    mjc1016 said:
     

    how can it be a config issue when loading the figure from scratch, have the seam without rendering and with rendering?????? Think about it.

    Because there could be a simple fault in the surface settings...

    Something like the 'base' color for the torso being 248 248 248 and the limbs being 255 255 255.

    THAT is a config issue.

    I may not the smartest guy in the world but I am also not stupid and as written, it is on the backside more visible than on the front, so it can`t be a config issue.

    Post edited by cosmo71 on
Sign In or Register to comment.