Reminder To Myself: Never again SBH Hair


Please, find a working replacement for dforce! It's slow and its results are more than often unwanted. Like explosions and weird forces towards the x-axis.
When it comes to simulation speed, SBH hair is the worst.
I've just purchased a SBH hair product, that finally fits my workflow, only to find out, that it might take about half an hour of simulation time.
Other software have cloth and hair simulation in real time.
Dforce is obviously outdated.

Comments

  • WendyLuvsCatzWendyLuvsCatz Posts: 41,505
    edited September 5

    meh, mine can take several hours and 5GB save files devil

    yeah, stopped buying it too

    Dforce cloth hair better

    Post edited by WendyLuvsCatz on
  • jmucchiellojmucchiello Posts: 2,065

    Masterstroke said:

    Please, find a working replacement for dforce! It's slow and its results are more than often unwanted. Like explosions and weird forces towards the x-axis.
    When it comes to simulation speed, SBH hair is the worst.

    Well, yeah. It's strand based hair (SBH). It is simulating individual strands of hair. Other hair is faster because the hair is approximated with polygons. This has nothing to do with dForce and all to do with individual hairs. I've never had a hair sim last more than 10 minutes. But maybe my hardware is better. Also never seen a 5 GB save file. Not sure what's up with that.

  • backgroundbackground Posts: 929

    SBH is only good for portraits. I don't do portraits... end of.

  • WendyLuvsCatzWendyLuvsCatz Posts: 41,505
    edited September 5

    I do animations hence the times and save sizes

    Carrara dynamic hair not that ridiculous 

    and not locked to PAs

    Post edited by WendyLuvsCatz on
  • PadonePadone Posts: 4,314

    Probably it helps disabling collisions among strands.

  • Animating in daz with SBH, quite the masochist arent you ?

  • Can I ask what I need to update to allow my machine to do anything with tessalation 0 SBH. At the moment I only get a grey splodge, and I think it requires an update to one of the resource files. I just don't know which & it's not done automatically on my offline machine. Regards, Richard.
  • HavosHavos Posts: 5,703

    richardandtracy said:

    Can I ask what I need to update to allow my machine to do anything with tessalation 0 SBH. At the moment I only get a grey splodge, and I think it requires an update to one of the resource files. I just don't know which & it's not done automatically on my offline machine. Regards, Richard.

    Which DS version are you using? Tesslation 0 was added at least a couple of years ago, but you have to be using at least the latest version at that time. You will also need the latest version of the resources and shaders file.

  • MasterstrokeMasterstroke Posts: 2,492

    Padone said:

    Probably it helps disabling collisions among strands.

    This is usually the first thing I do with simulated hair. It might work in some cases, but often it results in totally flat collapsed hair, without really signifficant simulation time saving. 

  • HavosHavos Posts: 5,703

    I found SBH hair largely unusable before Iray supported curves natively (ie hair could be dropped to tessation 0 and still look good).

    On my machine dForce tends to simulate in 5-15 seconds, and render times are at least as fast as polygon hair. There are a few items I own with longer simulation times, but never more than 2-3 mins, I don't have the patience for anything longer than that.

  • I'm using 4.21. I have 4.23 and 4.24 but am not using them regularly. Only use 4.24 for MeasureMetrics really. Rendering seems slower with it. If need be, I can go to 4.11, 4.14 & 4.16. Regards, Richard
  • Looks like 4.22 is the oldest that can use the Omni shader. Will update my default resources and try 4.24. Regards, Richard.
  • frank0314frank0314 Posts: 15,100

    Masterstroke said:


    Please, find a working replacement for dforce! It's slow and its results are more than often unwanted. Like explosions and weird forces towards the x-axis.
    When it comes to simulation speed, SBH hair is the worst.
    I've just purchased a SBH hair product, that finally fits my workflow, only to find out, that it might take about half an hour of simulation time.
    Other software have cloth and hair simulation in real time.
    Dforce is obviously outdated.

    What are your system specs and which ver of DS are you using?

  • MasterstrokeMasterstroke Posts: 2,492

    frank0314 said:

    Masterstroke said:


    Please, find a working replacement for dforce! It's slow and its results are more than often unwanted. Like explosions and weird forces towards the x-axis.
    When it comes to simulation speed, SBH hair is the worst.
    I've just purchased a SBH hair product, that finally fits my workflow, only to find out, that it might take about half an hour of simulation time.
    Other software have cloth and hair simulation in real time.
    Dforce is obviously outdated.

    What are your system specs and which ver of DS are you using?

    I am using a PC with 64 GB Ram and an RTX 3060 12 GB gpu. 

  • lilweeplilweep Posts: 2,867

    Masterstroke said:


    Please, find a working replacement for dforce! It's slow and its results are more than often unwanted. Like explosions and weird forces towards the x-axis.
    When it comes to simulation speed, SBH hair is the worst.
    I've just purchased a SBH hair product, that finally fits my workflow, only to find out, that it might take about half an hour of simulation time.
    Other software have cloth and hair simulation in real time.
    Dforce is obviously outdated.

    Just because something is SBH or "dForce SBH" doesnt mean it was intended for simulation.
    "dforce SBH" is just the name of of the system used to make SBH hair. The "dforce" aspect of the name in some cases is a misnomer and does not always mean it will simulate.

  • TorquinoxTorquinox Posts: 4,859

    lilweep said:

    Just because something is SBH or "dForce SBH" doesnt mean it was intended for simulation.
    "dforce SBH" is just the name of of the system used to make SBH hair. The "dforce" aspect of the name in some cases is a misnomer and does not always mean it will simulate.

    Can you share with us the documentation for that so we can better understand how all this works? 

  • jmucchiellojmucchiello Posts: 2,065

    Torquinox said:

    lilweep said:

    Just because something is SBH or "dForce SBH" doesnt mean it was intended for simulation.
    "dforce SBH" is just the name of of the system used to make SBH hair. The "dforce" aspect of the name in some cases is a misnomer and does not always mean it will simulate.

    Can you share with us the documentation for that so we can better understand how all this works? 

    Documentation? This is intended as humor?

  • 3DSaga3DSaga Posts: 902
    edited September 5

    I asked DAZ AI (Victoria) a similar question a few days ago; "Why do some of my dForce hair products not simulate?" I don't remember the answer verbatim so I just asked again, and this is how it was explained:

    "Some hair products are built using the dForce hair system, but the creator never intended the final product to actually run a simulation. They use the dForce tools mainly to help design or generate the hair strands, then leave the hair as a static asset in the final product.

    So even though the name includes “dForce,” the hair may:

    • Have no simulation setup
    • Not respond to dForce simulation at all
    • Be meant to stay fixed in the scene

    This naming can definitely be confusing, because “dForce hair” doesn’t always mean it will simulate."

    Granted, DAZ AI isn't always completely accurate so I'm reluctant to say this is "official" DAZ documentation. 

    Post edited by 3DSaga on
  • 3DSaga said:

    I asked DAZ AI (Victoria) a similar question a few days ago; "Why do some of my dForce hair products not simulate?" I don't remember the answer verbatim so I just asked again, and this is how it was explained:

    "Some hair products are built using the dForce hair system, but the creator never intended the final product to actually run a simulation. They use the dForce tools mainly to help design or generate the hair strands, then leave the hair as a static asset in the final product.

    So even though the name includes “dForce,” the hair may:

    • Have no simulation setup
    • Not respond to dForce simulation at all
    • Be meant to stay fixed in the scene

    This naming can definitely be confusing, because “dForce hair” doesn’t always mean it will simulate."

    Granted, DAZ AI isn't always completely accurate so I'm reluctant to say this is "official" DAZ documentation. 

    dForce Hair just means it is using the dForce hair system, which is distinct from Strand-Based Hair (dForce Hair can be made from imported mesh from another application, it doesn't have to be built with SBH). Whether, and to what extent, it allows simulation is up to the PA. So Victoria is pretty much correct here.

  • lilweeplilweep Posts: 2,867

    3DSaga said:

    I asked DAZ AI (Victoria) a similar question a few days ago; "Why do some of my dForce hair products not simulate?" I don't remember the answer verbatim so I just asked again, and this is how it was explained:

    "Some hair products are built using the dForce hair system, but the creator never intended the final product to actually run a simulation. They use the dForce tools mainly to help design or generate the hair strands, then leave the hair as a static asset in the final product.

    So even though the name includes “dForce,” the hair may:

    • Have no simulation setup
    • Not respond to dForce simulation at all
    • Be meant to stay fixed in the scene

    This naming can definitely be confusing, because “dForce hair” doesn’t always mean it will simulate."

    Granted, DAZ AI isn't always completely accurate so I'm reluctant to say this is "official" DAZ documentation. 

    I dont think there is any documentation, but that agrees with what has been said in threads on this forum over the years.

    Hair physics systems in most software are not actually simulating every single strand of hair, that would be a pretty computationally expensive/stupid way to do it. Obviously aglorithms have come a long way, and it's no longer fantasy to have a sim do such things. But certainly in blender today and daz today, simulation is done on proxy strands, not every single strand. 

    In Daz dforce hair, my understanding is that the guide strands (and the PS strands) are the proxies that get simulated and then the children hairs just follow.  Not every hair strand simulates.

    So that means for a dforce hair to actually be simulatable, the PA/Vendor should set the hair up with guide strands/ps strands and then children hairs get generated inside daz.  But some Daz PAs clearly do not want to generate the children hairs within Daz studio because the hairs look better in the the software where they author them.  Those PAs bring in every single strand of hair instead of just a minimal number of guide strands. They still convert the hair to dforce hair to get access to other properties, but the hair is not going to be simulatable with so many guide strands.  They will probably have changed the dforce sim settings to stop it from simulating.

    Anyways, the confusing nomenclature probably leads to many returns and sales queries, so it's strange that Daz has not changed the naming conventions yet.  

  • 3DSaga3DSaga Posts: 902

    Thanks for confirming that, Richard!  While SBH is a bit of a challenge for my PC (actually, it has more to do with my impatience), I've learned that some dForce hair works really well for me. Initially I made the mistake of  avoiding dForce hair altogether. 

  • We should remember that a lot of hair styles in the physical world don't move much - they have gel or laquer holding them in place, they have been given curls or waves that are heat or chemically set in place etc. 

    Any DS strand-based hair is likely to use guide hairs and then interpolate additional hairs between them at render time - that is not inherently linked to the hair being set up for simulation.

  • lilweeplilweep Posts: 2,867

    Richard Haseltine said:

    3DSaga said:

    I asked DAZ AI (Victoria) a similar question a few days ago; "Why do some of my dForce hair products not simulate?" I don't remember the answer verbatim so I just asked again, and this is how it was explained:

    "Some hair products are built using the dForce hair system, but the creator never intended the final product to actually run a simulation. They use the dForce tools mainly to help design or generate the hair strands, then leave the hair as a static asset in the final product.

    So even though the name includes “dForce,” the hair may:

    • Have no simulation setup
    • Not respond to dForce simulation at all
    • Be meant to stay fixed in the scene

    This naming can definitely be confusing, because “dForce hair” doesn’t always mean it will simulate."

    Granted, DAZ AI isn't always completely accurate so I'm reluctant to say this is "official" DAZ documentation. 

    dForce Hair just means it is using the dForce hair system, which is distinct from Strand-Based Hair (dForce Hair can be made from imported mesh from another application, it doesn't have to be built with SBH). Whether, and to what extent, it allows simulation is up to the PA. So Victoria is pretty much correct here.

    SBH can also mean different things to different people.  "Strand-based" hair is a general term used outside of Daz Studio to refer to hair grooms that are strands as opposed to cards etc.  You seem to be using "SBH"  to refer to the type of object that is generated in Daz Studio by the "SBH Editor".  

    It doesnt really help matters that there are effectively two definitions "SBH" which has a weak definition and "dforce" which is just a confusing definition.

    Daz Studio could perhaps put "simulation ready" or "not simulation ready" somewhere on the product to add clarity/distinctions between both cases.  But most people see dforce and assume it is simulation ready, so it can lead to frustration if it isnt.

  • mattlight07mattlight07 Posts: 7
    lilweep said:

    3DSaga said:

    I asked DAZ AI (Victoria) a similar question a few days ago; "Why do some of my dForce hair products not simulate?" I don't remember the answer verbatim so I just asked again, and this is how it was explained:

    "Some hair products are built using the dForce hair system, but the creator never intended the final product to actually run a simulation. They use the dForce tools mainly to help design or generate the hair strands, then leave the hair as a static asset in the final product.

    So even though the name includes “dForce,” the hair may:

    • Have no simulation setup
    • Not respond to dForce simulation at all
    • Be meant to stay fixed in the scene

    This naming can definitely be confusing, because “dForce hair” doesn’t always mean it will simulate."

    Granted, DAZ AI isn't always completely accurate so I'm reluctant to say this is "official" DAZ documentation. 

    I dont think there is any documentation, but that agrees with what has been said in threads on this forum over the years.

    Hair physics systems in most software are not actually simulating every single strand of hair, that would be a pretty computationally expensive/stupid way to do it. Obviously aglorithms have come a long way, and it's no longer fantasy to have a sim do such things. But certainly in blender today and daz today, simulation is done on proxy strands, not every single strand. 

    In Daz dforce hair, my understanding is that the guide strands (and the PS strands) are the proxies that get simulated and then the children hairs just follow.  Not every hair strand simulates.

    So that means for a dforce hair to actually be simulatable, the PA/Vendor should set the hair up with guide strands/ps strands and then children hairs get generated inside daz.  But some Daz PAs clearly do not want to generate the children hairs within Daz studio because the hairs look better in the the software where they author them.  Those PAs bring in every single strand of hair instead of just a minimal number of guide strands. They still convert the hair to dforce hair to get access to other properties, but the hair is not going to be simulatable with so many guide strands.  They will probably have changed the dforce sim settings to stop it from simulating.

    Anyways, the confusing nomenclature probably leads to many returns and sales queries, so it's strange that Daz has not changed the naming conventions yet.  

    Can I get a source about the blender part? Is it enforced that it could only simulate guides and not individual hairs? What if you place the modifier after the hair hair duplication? I seem to recall videos of it producing different movements per strand on a single guide curve.
  • Richard HaseltineRichard Haseltine Posts: 111,363

    mattlight07 said:

    lilweep said:

    3DSaga said:

    I asked DAZ AI (Victoria) a similar question a few days ago; "Why do some of my dForce hair products not simulate?" I don't remember the answer verbatim so I just asked again, and this is how it was explained:

    "Some hair products are built using the dForce hair system, but the creator never intended the final product to actually run a simulation. They use the dForce tools mainly to help design or generate the hair strands, then leave the hair as a static asset in the final product.

    So even though the name includes “dForce,” the hair may:

    • Have no simulation setup
    • Not respond to dForce simulation at all
    • Be meant to stay fixed in the scene

    This naming can definitely be confusing, because “dForce hair” doesn’t always mean it will simulate."

    Granted, DAZ AI isn't always completely accurate so I'm reluctant to say this is "official" DAZ documentation. 

    I dont think there is any documentation, but that agrees with what has been said in threads on this forum over the years.

    Hair physics systems in most software are not actually simulating every single strand of hair, that would be a pretty computationally expensive/stupid way to do it. Obviously aglorithms have come a long way, and it's no longer fantasy to have a sim do such things. But certainly in blender today and daz today, simulation is done on proxy strands, not every single strand. 

    In Daz dforce hair, my understanding is that the guide strands (and the PS strands) are the proxies that get simulated and then the children hairs just follow.  Not every hair strand simulates.

    So that means for a dforce hair to actually be simulatable, the PA/Vendor should set the hair up with guide strands/ps strands and then children hairs get generated inside daz.  But some Daz PAs clearly do not want to generate the children hairs within Daz studio because the hairs look better in the the software where they author them.  Those PAs bring in every single strand of hair instead of just a minimal number of guide strands. They still convert the hair to dforce hair to get access to other properties, but the hair is not going to be simulatable with so many guide strands.  They will probably have changed the dforce sim settings to stop it from simulating.

    Anyways, the confusing nomenclature probably leads to many returns and sales queries, so it's strange that Daz has not changed the naming conventions yet.  

    Can I get a source about the blender part? Is it enforced that it could only simulate guides and not individual hairs? What if you place the modifier after the hair hair duplication? I seem to recall videos of it producing different movements per strand on a single guide curve.

    The guide hairs ar what can be edited, interpolated hairs are generated from the guides (the relative proportions of one to the other being set in the SBH Editor or in dForce setup). None of us have access to the dForce hair set-up tools, however, so we can go only by results or what is mentioned in the change logs. 

  • donniekeidicdonniekeidic Posts: 135

    I don't like it for human hair but its really good for fur. No need to simulate and it renders really fast. There is nothing better for fur.

Sign In or Register to comment.