Loading...
> >

Look at my Hair (LAMH) Official Thread: update 1.6.0.2 released

1…4142444647…80

Comments

  • lokanbulllokanbull Posts: 24
    edited April 2016

    Bah, double post on my part :(

    Post edited by lokanbull on
  • Kendall SearsKendall Sears Posts: 2,995
    the button is on the lamh pane where the color and hair quantity entries are. I am on the road ATM otherwise I'd include an image.
    lokanbull said:
    Alessandro_AM said:

    Hello, this is an issue that we are still trying to sort out for what's possible, on our end. It is caused by the way certain UV sets are made and so far we know for sure it affects G3 based characters. Your should be a Genesis(1) based model, am I right? If so I'd be slightly suprised if the texture output is wrong because never experimented this issue on it.

    @Alessandro_AM Correct, those two figures I mentioned were for Genesis(1).  I'm in the process of uninstalling and reinstalling everything right now. It was something I needed to do anyhow, so this was as a good time as any.

     

    Kendall Sears said:
    @lokanbull make sure that the "mapped" button is checked on the pane for the figure. Kendall

    Where is this button exactly? Inside LAMH or somewhere in DS?

    I couldn't figure out how to do an @ with your username Kendall.

  • Alessandro MastronardiAlessandro Mastronardi Posts: 2,629

    @lokanbull, see attached image...

     

    Screen Shot 2016-04-07 at 23.49.31.jpg
    453 x 775 - 98K
  • Alessandro MastronardiAlessandro Mastronardi Posts: 2,629
    timmins.william said:

    I suppose a woolly render is in order?

    (Rhinoceros 1 + Iray Skydome Superpak)

     

    @timmins.william nice, that is with the LAMH free player right?

  • lokanbulllokanbull Posts: 24
    Alessandro_AM said:

    @lokanbull, see attached image...

    Ah, I'm currently using the full version, and not the player.

  • Alessandro MastronardiAlessandro Mastronardi Posts: 2,629
    lokanbull said:
    Alessandro_AM said:

    @lokanbull, see attached image...

    Ah, I'm currently using the full version, and not the player.

    @lokanbull , actually that is from the full version. The full version has also a pane that you can use (Window->Panes->LAMH); that 'mapped' option is available through the pane also for the full version.

  • Oso3DOso3D Posts: 15,041

    AM: Oh no, I've owned LAMH full for quite a while. ;)

    Thank goodness, too, because without Fiberhair option I would have given up on using it for Iray.

    I ended up combining the mapped texture with Mec4d's Unshaven shaders.

     

    Come to think about it, I should see how well I can do it in 3DL. I've had good luck with Iray Worlds being converted.

     

  • Alessandro MastronardiAlessandro Mastronardi Posts: 2,629

    Ok, check that you have latest version, because using the full and Fiberhair the fur mesh generated should account for density maps, while it seems that on your, if my eyes don't betray me, the fur is covering all the body parts. I did a quickie right now with Iray too...

     

     

     

    timmins.william said:

     

    AM: Oh no, I've owned LAMH full for quite a while. ;)

    Thank goodness, too, because without Fiberhair option I would have given up on using it for Iray.

    I ended up combining the mapped texture with Mec4d's Unshaven shaders.

     

    Come to think about it, I should see how well I can do it in 3DL. I've had good luck with Iray Worlds being converted.

     

     

    rino.jpg
    1234 x 722 - 184K
  • Oso3DOso3D Posts: 15,041

    v 1.5.15.0

    It might be the hair. I'm still working on getting an iray shader I'm really happy with for LAMH. hmm.

  • Oso3DOso3D Posts: 15,041

    It looks more obviously how it's supposed to look from a different camera angle. I was going to redo the hair but it keeps locking up my machine so I'll just leave it for now. Heh.

     

     

  • lokanbulllokanbull Posts: 24
    Alessandro_AM said:
    @lokanbull , actually that is from the full version. The full version has also a pane that you can use (Window->Panes->LAMH); that 'mapped' option is available through the pane also for the full version.

    Ah OK. I do see it. I will try that setting later today and let you know how it goes.

    In the meantime though, I wonder why I'm having this issue when using the full editor. I assume it should be working, or is it a known issue? If it should work, then maybe it's something to do with my setup.

  • DisparateDreamerDisparateDreamer Posts: 2,511

    I did not have this issue occur in 4.8, only in 4.9, I am not sure what happened.... :(

  • lokanbulllokanbull Posts: 24
    lokanbull said:
    Alessandro_AM said:
    @lokanbull , actually that is from the full version. The full version has also a pane that you can use (Window->Panes->LAMH); that 'mapped' option is available through the pane also for the full version.

    Ah OK. I do see it. I will try that setting later today and let you know how it goes.

    In the meantime though, I wonder why I'm having this issue when using the full editor. I assume it should be working, or is it a known issue? If it should work, then maybe it's something to do with my setup.

    I gave the pane a shot, and I got the exact same result.

    I even re-installed from scratch all Daz content from my system (Daz Studio included) and I'm still getting the same issue when exporting to OBJ or FibreHair. However, if I'm using Renderman, then everything works fine, it's just the exporter doesn't seem to want to create a proper texture file based on the mapped textures.

    I've experimented with Daz Studio 4.9 only as I no longer have access to 4.8.

    I'm at a loss. 

  • Alessandro MastronardiAlessandro Mastronardi Posts: 2,629
    lokanbull said:
    lokanbull said:
    Alessandro_AM said:
    okanbull , actually that is from the full version. The full version has also a pane that you can use (Window->Panes->LAMH); that 'mapped' option is available through the pane also for the full version.

    Ah OK. I do see it. I will try that setting later today and let you know how it goes.

    In the meantime though, I wonder why I'm having this issue when using the full editor. I assume it should be working, or is it a known issue? If it should work, then maybe it's something to do with my setup.

    I gave the pane a shot, and I got the exact same result.

    I even re-installed from scratch all Daz content from my system (Daz Studio included) and I'm still getting the same issue when exporting to OBJ or FibreHair. However, if I'm using Renderman, then everything works fine, it's just the exporter doesn't seem to want to create a proper texture file based on the mapped textures.

    I've experimented with Daz Studio 4.9 only as I no longer have access to 4.8.

    I'm at a loss. 

    I'm pretty much sure it's a LAMH issue in conjunction with the way some UV's are designed for some models. I still have DS 4.8 and my tests shows that it happens also there. With Kendall we're working on a solution but it's not an easy fix at all.

  • lokanbulllokanbull Posts: 24
    Alessandro_AM said:
    lokanbull said:
    lokanbull said:
    Alessandro_AM said:
    okanbull , actually that is from the full version. The full version has also a pane that you can use (Window->Panes->LAMH); that 'mapped' option is available through the pane also for the full version.

    Ah OK. I do see it. I will try that setting later today and let you know how it goes.

    In the meantime though, I wonder why I'm having this issue when using the full editor. I assume it should be working, or is it a known issue? If it should work, then maybe it's something to do with my setup.

    I gave the pane a shot, and I got the exact same result.

    I even re-installed from scratch all Daz content from my system (Daz Studio included) and I'm still getting the same issue when exporting to OBJ or FibreHair. However, if I'm using Renderman, then everything works fine, it's just the exporter doesn't seem to want to create a proper texture file based on the mapped textures.

    I've experimented with Daz Studio 4.9 only as I no longer have access to 4.8.

    I'm at a loss. 

    I'm pretty much sure it's a LAMH issue in conjunction with the way some UV's are designed for some models. I still have DS 4.8 and my tests shows that it happens also there. With Kendall we're working on a solution but it's not an easy fix at all.

    Thanks for your all your help Alessandro and Kendall. I appreciate how quickly you got back to me :)

    I'll use Renderman for those models, and I'll keep experimenting with other models in my collection and see which ones will work as an OBJ.

  • Alessandro MastronardiAlessandro Mastronardi Posts: 2,629
    lokanbull said:
    Alessandro_AM said:
    lokanbull said:
    lokanbull said:
    Alessandro_AM said:
    okanbull , actually that is from the full version. The full version has also a pane that you can use (Window->Panes->LAMH); that 'mapped' option is available through the pane also for the full version.

    Ah OK. I do see it. I will try that setting later today and let you know how it goes.

    In the meantime though, I wonder why I'm having this issue when using the full editor. I assume it should be working, or is it a known issue? If it should work, then maybe it's something to do with my setup.

    I gave the pane a shot, and I got the exact same result.

    I even re-installed from scratch all Daz content from my system (Daz Studio included) and I'm still getting the same issue when exporting to OBJ or FibreHair. However, if I'm using Renderman, then everything works fine, it's just the exporter doesn't seem to want to create a proper texture file based on the mapped textures.

    I've experimented with Daz Studio 4.9 only as I no longer have access to 4.8.

    I'm at a loss. 

    I'm pretty much sure it's a LAMH issue in conjunction with the way some UV's are designed for some models. I still have DS 4.8 and my tests shows that it happens also there. With Kendall we're working on a solution but it's not an easy fix at all.

    Thanks for your all your help Alessandro and Kendall. I appreciate how quickly you got back to me :)

    I'll use Renderman for those models, and I'll keep experimenting with other models in my collection and see which ones will work as an OBJ.

    You're welcome and sorry about this issue. We're after it, hopefully we'll have a fix soon that allows all models to be compliant with the export procedure. I'm going to try with the same figure you have because, as I wrote earlier, I'm quite surprised to see a G1 based model having troubles (while the G3's we know for sure they do).

  • lokanbulllokanbull Posts: 24
    Alessandro_AM said:
    lokanbull said:
    Alessandro_AM said:
    lokanbull said:
    lokanbull said:
    Alessandro_AM said:
    okanbull , actually that is from the full version. The full version has also a pane that you can use (Window->Panes->LAMH); that 'mapped' option is available through the pane also for the full version.

    Ah OK. I do see it. I will try that setting later today and let you know how it goes.

    In the meantime though, I wonder why I'm having this issue when using the full editor. I assume it should be working, or is it a known issue? If it should work, then maybe it's something to do with my setup.

    I gave the pane a shot, and I got the exact same result.

    I even re-installed from scratch all Daz content from my system (Daz Studio included) and I'm still getting the same issue when exporting to OBJ or FibreHair. However, if I'm using Renderman, then everything works fine, it's just the exporter doesn't seem to want to create a proper texture file based on the mapped textures.

    I've experimented with Daz Studio 4.9 only as I no longer have access to 4.8.

    I'm at a loss. 

    I'm pretty much sure it's a LAMH issue in conjunction with the way some UV's are designed for some models. I still have DS 4.8 and my tests shows that it happens also there. With Kendall we're working on a solution but it's not an easy fix at all.

    Thanks for your all your help Alessandro and Kendall. I appreciate how quickly you got back to me :)

    I'll use Renderman for those models, and I'll keep experimenting with other models in my collection and see which ones will work as an OBJ.

    You're welcome and sorry about this issue. We're after it, hopefully we'll have a fix soon that allows all models to be compliant with the export procedure. I'm going to try with the same figure you have because, as I wrote earlier, I'm quite surprised to see a G1 based model having troubles (while the G3's we know for sure they do).

    I've also tried the "Tauran III - The Big Bull HD" and "Ape World 2" which uses G2 base model and also comes with LAMH presets and they are also giving the same issue. Leave it to me to find the genesis models that gives issues *chuckles*

    And no worries about the issue, I know how that goes (25+ year software developer here). I do love your product and looking forward to the fix. I'm just glad I was able to help you find these issues. Hopefully they'll help you pinpoint the cause faster.

  • Alessandro MastronardiAlessandro Mastronardi Posts: 2,629
    edited April 2016
    lokanbull said:
    Alessandro_AM said:
    lokanbull said:
    Alessandro_AM said:
    lokanbull said:
    lokanbull said:
    Alessandro_AM said:
    okanbull , actually that is from the full version. The full version has also a pane that you can use (Window->Panes->LAMH); that 'mapped' option is available through the pane also for the full version.

    Ah OK. I do see it. I will try that setting later today and let you know how it goes.

    In the meantime though, I wonder why I'm having this issue when using the full editor. I assume it should be working, or is it a known issue? If it should work, then maybe it's something to do with my setup.

    I gave the pane a shot, and I got the exact same result.

    I even re-installed from scratch all Daz content from my system (Daz Studio included) and I'm still getting the same issue when exporting to OBJ or FibreHair. However, if I'm using Renderman, then everything works fine, it's just the exporter doesn't seem to want to create a proper texture file based on the mapped textures.

    I've experimented with Daz Studio 4.9 only as I no longer have access to 4.8.

    I'm at a loss. 

    I'm pretty much sure it's a LAMH issue in conjunction with the way some UV's are designed for some models. I still have DS 4.8 and my tests shows that it happens also there. With Kendall we're working on a solution but it's not an easy fix at all.

    Thanks for your all your help Alessandro and Kendall. I appreciate how quickly you got back to me :)

    I'll use Renderman for those models, and I'll keep experimenting with other models in my collection and see which ones will work as an OBJ.

    You're welcome and sorry about this issue. We're after it, hopefully we'll have a fix soon that allows all models to be compliant with the export procedure. I'm going to try with the same figure you have because, as I wrote earlier, I'm quite surprised to see a G1 based model having troubles (while the G3's we know for sure they do).

    I've also tried the "Tauran III - The Big Bull HD" and "Ape World 2" which uses G2 base model and also comes with LAMH presets and they are also giving the same issue. Leave it to me to find the genesis models that gives issues *chuckles*

    And no worries about the issue, I know how that goes (25+ year software developer here). I do love your product and looking forward to the fix. I'm just glad I was able to help you find these issues. Hopefully they'll help you pinpoint the cause faster.

    Ok, thanks for the information, it's really helpful. May I ask, if it's not too much trouble, if you can fur a Genesis1 (just the plain one) and try to export the hair? Possibly also a G2M. Does the texture gets generated correctly (as it happens for me)? Attached what I get with the G2M...

    Edit: re-attached image...

    Screen Shot 2016-04-08 at 23.02.59.jpg
    2529 x 1169 - 523K
    Post edited by Alessandro Mastronardi on
  • lokanbulllokanbull Posts: 24
    Alessandro_AM said:
    lokanbull said:
    Alessandro_AM said:
    lokanbull said:
    Alessandro_AM said:
    lokanbull said:
    lokanbull said:
    Alessandro_AM said:
    okanbull , actually that is from the full version. The full version has also a pane that you can use (Window->Panes->LAMH); that 'mapped' option is available through the pane also for the full version.

    Ah OK. I do see it. I will try that setting later today and let you know how it goes.

    In the meantime though, I wonder why I'm having this issue when using the full editor. I assume it should be working, or is it a known issue? If it should work, then maybe it's something to do with my setup.

    I gave the pane a shot, and I got the exact same result.

    I even re-installed from scratch all Daz content from my system (Daz Studio included) and I'm still getting the same issue when exporting to OBJ or FibreHair. However, if I'm using Renderman, then everything works fine, it's just the exporter doesn't seem to want to create a proper texture file based on the mapped textures.

    I've experimented with Daz Studio 4.9 only as I no longer have access to 4.8.

    I'm at a loss. 

    I'm pretty much sure it's a LAMH issue in conjunction with the way some UV's are designed for some models. I still have DS 4.8 and my tests shows that it happens also there. With Kendall we're working on a solution but it's not an easy fix at all.

    Thanks for your all your help Alessandro and Kendall. I appreciate how quickly you got back to me :)

    I'll use Renderman for those models, and I'll keep experimenting with other models in my collection and see which ones will work as an OBJ.

    You're welcome and sorry about this issue. We're after it, hopefully we'll have a fix soon that allows all models to be compliant with the export procedure. I'm going to try with the same figure you have because, as I wrote earlier, I'm quite surprised to see a G1 based model having troubles (while the G3's we know for sure they do).

    I've also tried the "Tauran III - The Big Bull HD" and "Ape World 2" which uses G2 base model and also comes with LAMH presets and they are also giving the same issue. Leave it to me to find the genesis models that gives issues *chuckles*

    And no worries about the issue, I know how that goes (25+ year software developer here). I do love your product and looking forward to the fix. I'm just glad I was able to help you find these issues. Hopefully they'll help you pinpoint the cause faster.

    Ok, thanks for the information, it's really helpful. May I ask, if it's not too much trouble, if you can fur a Genesis1 (just the plain one) and try to export the hair? Possibly also a G2M. Does the texture gets generated correctly (as it happens for me)? Attached what I get with the G2M...

    Edit: re-attached image...

    Sure thing. I'll give it a shot in a a couple of hours and get back to you on it.

  • Oso3DOso3D Posts: 15,041

    I keep forgetting how much better LAMH looks in 3DL. ;) And now that I know more about what I'm doing for lighting and whatnot...

    Here's roughly similar setting (different camera angle), with Iray Superpak converted to 3DL.

    http://willbear.deviantart.com/art/Woolly-Rhino2-601834327

     

  • RAMWolffRAMWolff Posts: 10,228

    Looks great Will! 

  • JimbowJimbow Posts: 557
    timmins.william said:

    I keep forgetting how much better LAMH looks in 3DL. ;) And now that I know more about what I'm doing for lighting and whatnot...

    Here's roughly similar setting (different camera angle), with Iray Superpak converted to 3DL.

    http://willbear.deviantart.com/art/Woolly-Rhino2-601834327

     

    If you were really brave, you could create a geoshell and use your procedural tricks to add scaly highlights to the hair in iray devil

  • Oso3DOso3D Posts: 15,041

    Maybe after the new version is released. Until then, it's just like trying to steer a barge using any amount of hairs in Iray. I originally tried to convert 2 million hairs of the woolly rhino and it locked my machine up hard.

    2 million hairs in 3DL, no problem! And I hope it works like that when new version is out. ;)

     

  • JimbowJimbow Posts: 557

    Can you not export the hair in separate chunks? Depends on your setup, of course, but might make things more manageable. Do you even need hairs on the far side of the beast? I have to say, though, it's surprising that iray doesn't have a native hair shader, being related to Mental Ray which has one.

  • lokanbulllokanbull Posts: 24
    Alessandro_AM said:
    lokanbull said:

    I've also tried the "Tauran III - The Big Bull HD" and "Ape World 2" which uses G2 base model and also comes with LAMH presets and they are also giving the same issue. Leave it to me to find the genesis models that gives issues *chuckles*

    And no worries about the issue, I know how that goes (25+ year software developer here). I do love your product and looking forward to the fix. I'm just glad I was able to help you find these issues. Hopefully they'll help you pinpoint the cause faster.

    Ok, thanks for the information, it's really helpful. May I ask, if it's not too much trouble, if you can fur a Genesis1 (just the plain one) and try to export the hair? Possibly also a G2M. Does the texture gets generated correctly (as it happens for me)? Attached what I get with the G2M...

    Edit: re-attached image...

    So, I gave that a shot with the G1 and G2 base model and yes, that worked. So, I went further and tried it with the Bear and Tauran III models, and doing it that way also works. So, it appears the issue is with loading their packaged presets.

    I tried loading the original preset and saving it in a new location, then using that new save file, but that did not work. I've then tried to delete all texture maps from the shave group and re-add them, but the app kept crashing when I apply the changes. I was hoping that I could somehow duplicate or just update something from the original file so I could use the already styled hair, but no go.

    I think I may have round a workaround for now. I'm thinking of saving the texutre map created by making a new LAMH, then apply it to it to the preset LAHM. Maybe that will work if I use the same hair density and all. It's not perfect, but should work until a fix is found to load those presets properly.

    I'll give it a shot after I fix a few things on my main rig.

     

  • Mustakettu85Mustakettu85 Posts: 2,933

     

    xmasrose (aka tulipe) said:

    Thank you Mustakettu85 I would love to play with your skull cap even if I am not that good with LAMH I really would like to get better.

     

    Ice Dragon Art said:

    This would be awesome

     

    Hello again, and thank you both for taking an interest... here is the link; hope you find it fun to play with:

    http://www.sharecg.com/v/84596/view/21/DAZ-Studio/Mk85-CapForHair-plus-LAMH-presets

  • Alessandro MastronardiAlessandro Mastronardi Posts: 2,629
    Mustakettu85 said:

     

    xmasrose (aka tulipe) said:

    Thank you Mustakettu85 I would love to play with your skull cap even if I am not that good with LAMH I really would like to get better.

     

    Ice Dragon Art said:

    This would be awesome

     

    Hello again, and thank you both for taking an interest... here is the link; hope you find it fun to play with:

    http://www.sharecg.com/v/84596/view/21/DAZ-Studio/Mk85-CapForHair-plus-LAMH-presets

    Thanks for this, really appreciated!

     

  • Mustakettu85Mustakettu85 Posts: 2,933
    Alessandro_AM said:

    Thanks for this, really appreciated!

     

    blush And thank you for making it all happen =)

  • Kendall SearsKendall Sears Posts: 2,995

    A bit of information for everyone.  If you're using LAMH and your textures are not showing in the hairs, make sure that the "mapped" button is selected in the pane for the shavegroup(s) *AND* the hair root color is set to maximum white (255,255,255).  This should make the hair pick up the underlying texture.

    Also, in a bit of news, we've located the issue with Genesis 3.  We have a fix that we are testing that should be out in a maintenance release in a couple of weeks.  There is a maintenance release coming out imminently, but this was published before the issue with G3 was discovered.

    Kendall

  • Alessandro MastronardiAlessandro Mastronardi Posts: 2,629

    To complete Kendall's information, here are two images that show where to set the root color, and an Iray test render. Cheers

     

    Screen Shot 2016-04-10 at 11.31.36.jpg
    1281 x 1038 - 407K
    Screen Shot 2016-04-10 at 11.39.59.jpg
    2436 x 1218 - 484K
Sign In or Register to comment.