Free 3D
3D Print Models
3D Scans
Animation & MoCap
Textures
Materials
Skin Reference
2D Game Assets
Sound Effects
Brushes & Tools
Reference Photos
Stock Images
HDR Images
3ds Max
Maya
Blender
Unreal Engine
Unity
ZBrush
Cinema 4D
LightWave
Marmoset
SketchUp
FBX
DAE
DXF
GLBIs D-Force some sort of prank?
436Thread Activity
Tourmaline72Fri, Jun 19
Pushee-RiWed, Jun 17
Tourmaline72Wed, Jun 17
Pushee-RiWed, Jun 17
Tourmaline72Wed, Jun 17
Luxe MuseWed, Jun 17
Personally, I loathe D Force simply because I can't use it.
I don't understand it. I don't get it. I got on Daz Studio right before G9 figures started to appear.
That's how long I've been trying to figure it out.
Not one single tutorial I have found works. Not a single one.
Every single time I try it - EVERY SINGLE TIME - one of four things ALWAYS happens:
1 - Daz locks up and stays locked up until I close it. Literally for days if I don't.
2 - Daz locks up and crashes instantly.
3 - The object, prop, figure, background, or all of them distort into a groovy acid trip. Then Daz crashes.
4 - Nothing, it just says : "error in preparing objects to simulate and collide" and does nothing.
I know I swore it off a while back but I recently saw another tutorial which I had not seen before
and I spent the last month trying it out, over and over and over again with the same results.
I don't understand it. I don't get it. I got on Daz Studio right before G9 figures started to appear.
That's how long I've been trying to figure it out.
Not one single tutorial I have found works. Not a single one.
Every single time I try it - EVERY SINGLE TIME - one of four things ALWAYS happens:
1 - Daz locks up and stays locked up until I close it. Literally for days if I don't.
2 - Daz locks up and crashes instantly.
3 - The object, prop, figure, background, or all of them distort into a groovy acid trip. Then Daz crashes.
4 - Nothing, it just says : "error in preparing objects to simulate and collide" and does nothing.
I know I swore it off a while back but I recently saw another tutorial which I had not seen before
and I spent the last month trying it out, over and over and over again with the same results.
! REPORT
I already replied to you in the other thread. Let's go into a bit more detail here.
I assume you want to build a dForce object (clothing or something like that) yourself. My basic rule is: no fiddle-faddle, just a clear and simply structured mesh. Anything else can cause dForce explosions and system freezes. I posted links to my dForce freebies in the other thread. Take a look (if you feel like it) at the meshes for the objects. Saying it's 'easy-peasy' would be an understatement
I assume you want to build a dForce object (clothing or something like that) yourself. My basic rule is: no fiddle-faddle, just a clear and simply structured mesh. Anything else can cause dForce explosions and system freezes. I posted links to my dForce freebies in the other thread. Take a look (if you feel like it) at the meshes for the objects. Saying it's 'easy-peasy' would be an understatement
REPLY
! REPORT
Quote:
"Every single time I try it - EVERY SINGLE TIME - one of four things ALWAYS happens:
1 - Daz locks up and stays locked up until I close it. Literally for days if I don't.
2 - Daz locks up and crashes instantly.
3 - The object, prop, figure, background, or all of them distort into a groovy acid trip. Then Daz crashes.
4 - Nothing, it just says : "error in preparing objects to simulate and collide" and does nothing."
No doubt, that dforce is simply cr@p, but it usually works.
There must be something missing in your system, like some driver or something, because your dforce symtomes should not happen.
"Every single time I try it - EVERY SINGLE TIME - one of four things ALWAYS happens:
1 - Daz locks up and stays locked up until I close it. Literally for days if I don't.
2 - Daz locks up and crashes instantly.
3 - The object, prop, figure, background, or all of them distort into a groovy acid trip. Then Daz crashes.
4 - Nothing, it just says : "error in preparing objects to simulate and collide" and does nothing."
No doubt, that dforce is simply cr@p, but it usually works.
There must be something missing in your system, like some driver or something, because your dforce symtomes should not happen.
REPLY
! REPORT
Pushee-Ri
Karma: 52,482
Sun, Jun 14@Masterstroke
Yep, I thought of that too... I just didn't want to say it out loud
I had already sent Tourmaline the links to my two dForce freebies, which simulate without any ifs or buts. But I haven't gotten a response yet. Let's wait and see...
Yep, I thought of that too... I just didn't want to say it out loud
I had already sent Tourmaline the links to my two dForce freebies, which simulate without any ifs or buts. But I haven't gotten a response yet. Let's wait and see...
I used Poser dynamics for years. Loved it. dforce kind of scared me at first. I was using dforce the same way I used Poser dynamics. Say 50 frames in my timelines, pose at frame 25. That did not always work the way I wanted. So, I've been posing in the very last frame and dforce runs so much nicer. And it's the same as it was with Poser dynamics: you run one item at a time, then freeze that simulation.
But there are some products that won't actually work with the timeline, you have to use the current frame. So far, just hair for those. I have, on occasion, had things explode. But those instances are almost always something I did wrong.
But there are some products that won't actually work with the timeline, you have to use the current frame. So far, just hair for those. I have, on occasion, had things explode. But those instances are almost always something I did wrong.
REPLY
! REPORT
Masterstroke
Karma: 5,702
Sun, Jun 14I think, that is not exactly the point here.
The problems are freezes and crashes with dforce.
This sounds more fundamental, than the usual dforce hickups.
The problems are freezes and crashes with dforce.
This sounds more fundamental, than the usual dforce hickups.
ArtbyMel
Karma: 17,649
Sun, Jun 14My point is that I forgot to add was that Daz would freeze up when I was doing things incorrectly. Sorry, not enough caffeine this morning.
Pushee-Ri
Karma: 52,482
Sun, Jun 14@ArtbyMel
Sometimes (as a CC) I feel like there are more ways to mess up with DAZ than to get it right
I've already had a looooooot of coffee (but then again, it's already afternoon here
Sometimes (as a CC) I feel like there are more ways to mess up with DAZ than to get it right
I've already had a looooooot of coffee (but then again, it's already afternoon here
dforce works.
is it a good cloth simulator?
no it is bare bones. basic.
but it works just adequately for most users..
you have to look at your system specs. that's probably what is causing the failures. calculation overload.
is it a good cloth simulator?
no it is bare bones. basic.
but it works just adequately for most users..
you have to look at your system specs. that's probably what is causing the failures. calculation overload.
REPLY
! REPORT
I had thought initially when I started out that it was my old computer, which was S L O W.
But now I have a computer which I had built by a custom shop specifically for using DAZ.
That changed nothing. D Force just does weird things faster now.
I wasn't looking to build anything, just use it for posing hair and clothing.
But now I have a computer which I had built by a custom shop specifically for using DAZ.
That changed nothing. D Force just does weird things faster now.
I wasn't looking to build anything, just use it for posing hair and clothing.
REPLY
! REPORT
It really does need pretty heavy hardware to "work", as in not always crash. Once you get good hardware, like say a 4090 paired with a 16 core ryzen beast with 128gb RAM like I have, it doesn't do the crash thing often, just the explode thing. If you ever use something like marvelous designer, you can see how poorly made and or poorly implemented dforce really is. Like even on weaker systems, MD just works, maybe it works slow, but you don't get all these constant explosions and implosions like dforce. But it is expensive software, made to do that one thing, work with clothes.
But that really is daz studio in a nutshell TBH. It cannot render as well as things like blender for example. Geometry that renders perfectly fine in blender, can end up a mangled mess with holes in it in daz studio for no explicable reason, forcing you back into blender to try and figure out how to fix it. Same with instancing, daz studio will choke a lot sooner than blender will, it took me like a week to get the grass I made looking OK as I could, without locking up daz studio.
But that really is daz studio in a nutshell TBH. It cannot render as well as things like blender for example. Geometry that renders perfectly fine in blender, can end up a mangled mess with holes in it in daz studio for no explicable reason, forcing you back into blender to try and figure out how to fix it. Same with instancing, daz studio will choke a lot sooner than blender will, it took me like a week to get the grass I made looking OK as I could, without locking up daz studio.
REPLY
! REPORT
Is there any chance you're trying to run dForce while you're in Iray preview mode? Also, are any of those tutorials you've found so far by Rauko on YT?
REPLY
! REPORT
Tourmaline72
Karma: 955
Sun, Jun 14I've tried it in ALL modes. Iray preview, Texture, Smooth, Filament, all of them. Doesn't change anything.
It's possible some were by Rauko. I haven't kept track of who made them.
It's possible some were by Rauko. I haven't kept track of who made them.
Everwild
Karma: 10,484
Sun, Jun 14There's almost nothing intuitive about Daz; I feel your frustration. I've experienced every problem you mentioned above, but of course, with different systems, what fixed things for me might not fix anything for you. If you want to try to troubleshoot it here, though, I'm happy to try to help and I'm sure others will be willing to chime in and steer you towards some level of success.
If you want to go this route, I think diogenese's comment above is a good place to start. That, and maybe post the stats on your system, esp. the video card. The first hurdle is getting you past the freezes and crashes. I don't know if you can drop the whole error log here, but copying a block including some fail states might help someone interpret what's going on.
Avoid running any simulation in Iray Preview, though. It's a resource hog. I stick to Texture Shaded.
Lemme know, cuz if all you wanna do is come to throw virtual bricks at Daz and scream into the void, I'm down for that, too. I can certainly relate and commiserate.
If you want to go this route, I think diogenese's comment above is a good place to start. That, and maybe post the stats on your system, esp. the video card. The first hurdle is getting you past the freezes and crashes. I don't know if you can drop the whole error log here, but copying a block including some fail states might help someone interpret what's going on.
Avoid running any simulation in Iray Preview, though. It's a resource hog. I stick to Texture Shaded.
Lemme know, cuz if all you wanna do is come to throw virtual bricks at Daz and scream into the void, I'm down for that, too. I can certainly relate and commiserate.
Pushee-Ri
Karma: 52,482
Mon, Jun 15@Everwild
For testing purposes, I would also suggest the following:
Create a new scene that contains only the model. You don't need to assign a pose.
Load the dForce object. You should select clothing, as hair takes longer to simulate. If there are multiple clothing items, limit the selection to a single one.
Go to the render settings and turn off 'Start Bones From Memorized Pose.' This also speeds up the simulation.
This would be a setup for a quick test. If a dForce object that works for everyone else still crashes on your computer, the problem lies with your PC
For testing purposes, I would also suggest the following:
Create a new scene that contains only the model. You don't need to assign a pose.
Load the dForce object. You should select clothing, as hair takes longer to simulate. If there are multiple clothing items, limit the selection to a single one.
Go to the render settings and turn off 'Start Bones From Memorized Pose.' This also speeds up the simulation.
This would be a setup for a quick test. If a dForce object that works for everyone else still crashes on your computer, the problem lies with your PC
A year ago I had a similar problem. I got a "new" computer and suddenly dForce caused problems. Then I found out that you can change the way dForce is computed.
I described it in my Post:
https://www.renderhub.com/gallery/70965/help-please-a-problem-with-simulations
"It seems, I found the solution: let the CPU do the dForce-Simulation.
At least on my iMac with i7-Processor:
> go to the Simulation Pane > Advanced Tab > under OpenCL Device choose:
Apple Intel Core i7-4771 CPU @ 3.5 GHz"
In my case it's an Apple with an NViDIa-Graphics Card, but I think, one can doe the same on a PC
Another thing: choose "Better" instead of "Best" in the simulation settings. If I accidentally had chosen "Best" or the Simulation settings of a product are set to "best" by default
the simulation starts - but nothing is happening. I guess that is a sort of setting for very strong computers (mine is from 2013)
And of course the simulation should be well prepared. I watch frame by frame if there is a body part cutting through the body at any time. Usually this happens with crossed Legs or when the arms are on the way to the final position of the movement (i.e. hands in the hips). Try to change the arms rotation some frames before the end position so the hands come from the side, not from the front where they will inevitably cut through the hips. (If that doesn't help, you can make the thump-parts invisible during the simulation and make those parts visible after the simulation (which is a "dirty trick", but the thumb isn't visible in a lot of situations when you do the rendering : )
One last thing: I posted my way of preparing the figure and a chair here:
https://www.renderhub.com/gallery/51080/simulation-of-a-dress-on-a-3d-lady
It's not another tutorial, it is just a description of how I try to avoid exploding dresses (and it does NOT help with all clothes. Some just tend to explode and after I tried several times I just choose another outfit).
I do hope, that something of this may be useful!?
I described it in my Post:
https://www.renderhub.com/gallery/70965/help-please-a-problem-with-simulations
"It seems, I found the solution: let the CPU do the dForce-Simulation.
At least on my iMac with i7-Processor:
> go to the Simulation Pane > Advanced Tab > under OpenCL Device choose:
Apple Intel Core i7-4771 CPU @ 3.5 GHz"
In my case it's an Apple with an NViDIa-Graphics Card, but I think, one can doe the same on a PC
Another thing: choose "Better" instead of "Best" in the simulation settings. If I accidentally had chosen "Best" or the Simulation settings of a product are set to "best" by default
the simulation starts - but nothing is happening. I guess that is a sort of setting for very strong computers (mine is from 2013)
And of course the simulation should be well prepared. I watch frame by frame if there is a body part cutting through the body at any time. Usually this happens with crossed Legs or when the arms are on the way to the final position of the movement (i.e. hands in the hips). Try to change the arms rotation some frames before the end position so the hands come from the side, not from the front where they will inevitably cut through the hips. (If that doesn't help, you can make the thump-parts invisible during the simulation and make those parts visible after the simulation (which is a "dirty trick", but the thumb isn't visible in a lot of situations when you do the rendering : )
One last thing: I posted my way of preparing the figure and a chair here:
https://www.renderhub.com/gallery/51080/simulation-of-a-dress-on-a-3d-lady
It's not another tutorial, it is just a description of how I try to avoid exploding dresses (and it does NOT help with all clothes. Some just tend to explode and after I tried several times I just choose another outfit).
I do hope, that something of this may be useful!?
REPLY
! REPORT
1 - Daz locks up and stays locked up until I close it. Literally for days if I don't.
2 - Daz locks up and crashes instantly.
3 - The object, prop, figure, background, or all of them distort into a groovy acid trip. Then Daz crashes.
4 - Nothing, it just says : "error in preparing objects to simulate and collide" and does nothing.
A lot of these sound like they could be related to graphics driver issues, mainly the nVidia phyix engine (or whatever it's called). Maybe try running DDU (display driver uninstaller). Usually best to run this in safemode on your system. Then reinstall the -studio drivers- for your video card. The Game Ready drivers can get a little flaky from time to time, so stick with studio since those are stable.
Collision errors are also a thing. If you do something like do a pose with the hand behind the back, or head, or something and start from memorized pose, the hand (or object) will pass THROUGH the dforce object and cause an explosion in dForce. Sometimes that can manifest as just a complete program lock and you need to end task on Daz.
One thing I miss from Daz 6 is ManFriday's dForce companion...that was the best. You could run calculations on just individual pieces (I usually worked form bottom-up...eg calculate skirt, then shirt, then hair). And you could keep them visible in the viewport, but invisible in dForce so they didn't collide.
But alas...it's no longer available in the Daz store and paywall locked behind the $20/month premium access fee in version 6.
2 - Daz locks up and crashes instantly.
3 - The object, prop, figure, background, or all of them distort into a groovy acid trip. Then Daz crashes.
4 - Nothing, it just says : "error in preparing objects to simulate and collide" and does nothing.
A lot of these sound like they could be related to graphics driver issues, mainly the nVidia phyix engine (or whatever it's called). Maybe try running DDU (display driver uninstaller). Usually best to run this in safemode on your system. Then reinstall the -studio drivers- for your video card. The Game Ready drivers can get a little flaky from time to time, so stick with studio since those are stable.
Collision errors are also a thing. If you do something like do a pose with the hand behind the back, or head, or something and start from memorized pose, the hand (or object) will pass THROUGH the dforce object and cause an explosion in dForce. Sometimes that can manifest as just a complete program lock and you need to end task on Daz.
One thing I miss from Daz 6 is ManFriday's dForce companion...that was the best. You could run calculations on just individual pieces (I usually worked form bottom-up...eg calculate skirt, then shirt, then hair). And you could keep them visible in the viewport, but invisible in dForce so they didn't collide.
But alas...it's no longer available in the Daz store and paywall locked behind the $20/month premium access fee in version 6.
REPLY
! REPORT
Pushee-Ri's simple test is a good place to start after you've checked your drivers and/or reinstalled them. Also, a simple check: In the Simulation window, look under the Advanced tab at which OpenCL device is selected. Not sure if you bought a system with an on-board graphics card, but at one point Daz had defaulted to my flimsy built-in graphics card rather than the Nvidia card.
I also installed the studio drivers instead of the game ready ones (see B-Monster post above).
Once you get past whether you can get anything to dForce at all, Rauko has a decent video that explains the explosions (those acid trips you mention in #3), why they happen, and some ways to avoid them found here. I recommend a lot of his videos because although there are TONS of how-to videos to watch, very few of them explain why we do x over y. Rauko's better at explaining some of the whys Daz behaves the way it does. If you can get past the robo-voice, RenderGuide also has some decent tutorials explaining things more in depth than just "do this", too. And one more tutorial to help with dForce, I found this article on 3Dshards: https://3dshards.com/dforce-in-daz-studio-a-beginners-guide-to-cloth-simulation/ -- even if these specific fixes don't help you, the article gives you an idea of which settings to experiment with to get better results.
I was planning on adding Mjrk's tiny tute (which has already been provided in the post above), but I hadn't put it in my folder so thankfully it's already linked here and I don't have to go hunting. Using dForce with the timeline feels a little more "advanced" but it really does help.
I also installed the studio drivers instead of the game ready ones (see B-Monster post above).
Once you get past whether you can get anything to dForce at all, Rauko has a decent video that explains the explosions (those acid trips you mention in #3), why they happen, and some ways to avoid them found here. I recommend a lot of his videos because although there are TONS of how-to videos to watch, very few of them explain why we do x over y. Rauko's better at explaining some of the whys Daz behaves the way it does. If you can get past the robo-voice, RenderGuide also has some decent tutorials explaining things more in depth than just "do this", too. And one more tutorial to help with dForce, I found this article on 3Dshards: https://3dshards.com/dforce-in-daz-studio-a-beginners-guide-to-cloth-simulation/ -- even if these specific fixes don't help you, the article gives you an idea of which settings to experiment with to get better results.
I was planning on adding Mjrk's tiny tute (which has already been provided in the post above), but I hadn't put it in my folder so thankfully it's already linked here and I don't have to go hunting.
Using dForce with the timeline feels a little more "advanced" but it really does help. REPLY
! REPORT
The more I'm reading here, the more I'm convinced to never mess with D-Force ever again.
Way too convoluted and complicated for me.
Way too convoluted and complicated for me.
REPLY
! REPORT
I haven't even messed with D Force clothing yet. I've spent about 4 years just trying to get D Force to do something - anything - with hair that it's supposed to do.
REPLY
! REPORT
What kind of video card do you have? I have seen replies so far talking about your configuration but no confirmation on your end. Could very well be you don't have an NVidia card?
IRay might work on non NVidia because it would default to CPU rendering, but I think dforce has no fallback like rendering does.
IRay might work on non NVidia because it would default to CPU rendering, but I think dforce has no fallback like rendering does.
REPLY
! REPORT
Pushee-Ri
Karma: 52,482
Tue, Jun 16The PC I used for my first experiments with dForce didn't support Iray. That meant everything was emulated by the CPU. Of course, it felt like it took an eternity... but that eternity had no effect on the simulation or the 'explosions'
Tourmaline72 wrote on Sun, Jun 14 that he had bought a new PC specifically designed for DAZ / 3D. So there really shouldn't be any problems with dForce (even if it's just being emulated). To summarize: old PC -> problems with dForce; new PC -> problems with dForce.
Hmmm I have a hunch about this by now, but I don't want to step on anyone's toes here... but sometimes the problem isn't in the computer, but in front of the monitor
Tourmaline72 wrote on Sun, Jun 14 that he had bought a new PC specifically designed for DAZ / 3D. So there really shouldn't be any problems with dForce (even if it's just being emulated). To summarize: old PC -> problems with dForce; new PC -> problems with dForce.
Hmmm I have a hunch about this by now, but I don't want to step on anyone's toes here... but sometimes the problem isn't in the computer, but in front of the monitor
Luxe Muse
Karma: 7,889
Tue, Jun 16Hi, hi, hi!
I didn't know dforce could be emulated. I had a hunch, but wasn't sure. Thanks for helping me learn new things, Pushee-Ri!
I didn't know dforce could be emulated. I had a hunch, but wasn't sure. Thanks for helping me learn new things, Pushee-Ri!
guy91600
Karma: 19,516
Wed, Jun 17The problem doesn't necessarily stem from the user but from the contents of My Library. To verify this, simply create a new Windows user account (preferably local), create a new My Library folder, and install (from the original compressed folders) a version of Genesis, dForce, and a known working dForce clothing item.
*) If things go wrong, it's due to the PC.
*) If everything works correctly, the problem lies with the contents of the My Library folder.
*) If things go wrong, it's due to the PC.
*) If everything works correctly, the problem lies with the contents of the My Library folder.
Pushee-Ri
Karma: 52,482
Wed, Jun 17@Guy
'The problem doesn't necessarily stem from the user .... '
No, not necessarily... but we can't rule out that possibility either. So far, we've only received very limited information. That leaves room for speculation
A short story that just came to an end: I exchanged messages with a user via private message about one of my Dropables (which had been thoroughly tested). 'It doesn’t work, it explodes, etc., etc.' A few weeks later, the user all-clear came: It works! The user then wrote that the problem wasn’t with my project… but with the person sitting in front of the screen. That’s life
'The problem doesn't necessarily stem from the user .... '
No, not necessarily... but we can't rule out that possibility either. So far, we've only received very limited information. That leaves room for speculation
A short story that just came to an end: I exchanged messages with a user via private message about one of my Dropables (which had been thoroughly tested). 'It doesn’t work, it explodes, etc., etc.' A few weeks later, the user all-clear came: It works! The user then wrote that the problem wasn’t with my project… but with the person sitting in front of the screen. That’s life
"but sometimes the problem isn't in the computer, but in front of the monitor "
For sure.
How do you learn how to do something if everything you try does not work, if every set of directions you find does not help?
And yes, this computer most definitely has an NVIDIA Iray card and a whole lot more RAM than my old one.
For sure.
How do you learn how to do something if everything you try does not work, if every set of directions you find does not help?
And yes, this computer most definitely has an NVIDIA Iray card and a whole lot more RAM than my old one.
REPLY
! REPORT
Pushee-Ri
Karma: 52,482
Wed, Jun 17Sorry for the joke ('in front of the monitor') ... but I just had to say it (see also my short story to Guy above)
In general, using dForce objects should be just as easy as using regular objects. The only exception is that after posing, etc., you click 'Simulate.' As a user, you shouldn't have to worry about surface parameters or anything like that.
So if you have to adjust anything on your test hair object (surface parameters), then the manufacturer has sold you something... less than ideal...
Maybe you could post the name and link for the 3D hair here? That would be really helpful for me and others who want to help you.
On Tue, Jun 16 you wrote: 'I haven't even messed with D Force clothing yet. I've spent about 4 years just trying to get D Force to do something - anything - with hair that it's supposed to do'
Your persistence is admirable... but maybe you shouldn't focus on just one dForce object. It's quite possible that this product is less than ideal... or even useless.
To keep your frustration with dForce from turning into hatred, I’d like to suggest once again: try using dForce clothing that’s been tested. Here are a few suggestions:
For these links or quick tests, simply load the model, assign the clothing, and run the simulation (don’t change the pose):
https://www.renderhub.com/kuraikya/samurai-pants
https://www.renderhub.com/excessive/fairytale-dforce-dress-g8f
https://www.renderhub.com/paulawbs/city-style
My freebies with ultra-fast simulation. Switch the option 'Start Bones From Memorized Pose' to ON (Simulation Settings pane -> Initialization)
https://www.renderhub.com/pushee-ri/cloak-89-dforce-doodle-for-genesis-8-and-9-female
https://www.renderhub.com/pushee-ri/psr-test-skirt-for-gf8
As you can see from the ratings, all of the products have been tested and should therefore work for you. Maybe you'd like to try one or more of these products after all. Maybe that will help ease your dForce frustration
Once again: dForce isn't rocket science. As a user, you shouldn't get bogged down in all sorts of mumbo-jumbo settings; instead, you should be able to use the product with just one additional click on 'Simulate.'
Good luck
In general, using dForce objects should be just as easy as using regular objects. The only exception is that after posing, etc., you click 'Simulate.' As a user, you shouldn't have to worry about surface parameters or anything like that.
So if you have to adjust anything on your test hair object (surface parameters), then the manufacturer has sold you something... less than ideal...
Maybe you could post the name and link for the 3D hair here? That would be really helpful for me and others who want to help you.
On Tue, Jun 16 you wrote: 'I haven't even messed with D Force clothing yet. I've spent about 4 years just trying to get D Force to do something - anything - with hair that it's supposed to do'
Your persistence is admirable... but maybe you shouldn't focus on just one dForce object. It's quite possible that this product is less than ideal... or even useless.
To keep your frustration with dForce from turning into hatred, I’d like to suggest once again: try using dForce clothing that’s been tested. Here are a few suggestions:
For these links or quick tests, simply load the model, assign the clothing, and run the simulation (don’t change the pose):
https://www.renderhub.com/kuraikya/samurai-pants
https://www.renderhub.com/excessive/fairytale-dforce-dress-g8f
https://www.renderhub.com/paulawbs/city-style
My freebies with ultra-fast simulation. Switch the option 'Start Bones From Memorized Pose' to ON (Simulation Settings pane -> Initialization)
https://www.renderhub.com/pushee-ri/cloak-89-dforce-doodle-for-genesis-8-and-9-female
https://www.renderhub.com/pushee-ri/psr-test-skirt-for-gf8
As you can see from the ratings, all of the products have been tested and should therefore work for you. Maybe you'd like to try one or more of these products after all. Maybe that will help ease your dForce frustration
Once again: dForce isn't rocket science. As a user, you shouldn't get bogged down in all sorts of mumbo-jumbo settings; instead, you should be able to use the product with just one additional click on 'Simulate.'
Good luck
"Maybe you could post the name and link for the 3D hair here?"
All of them. Every single hair item I have with D Force. All of them. I've experimented with each of them. It doesn't matter.
It's not just one. It's not a few of them. It is all of them. All of them.
"Once again: dForce isn't rocket science. As a user, you shouldn't get bogged down in all sorts of mumbo-jumbo settings; instead, you should be able to use the product with just one additional click on 'Simulate.'"
Clicking "simulate" is like crossing wires trying to disarm a bomb. The best I can hope for is nothing happens.
That's been my experience with D Force after about four years of attempts.
All of them. Every single hair item I have with D Force. All of them. I've experimented with each of them. It doesn't matter.
It's not just one. It's not a few of them. It is all of them. All of them.
"Once again: dForce isn't rocket science. As a user, you shouldn't get bogged down in all sorts of mumbo-jumbo settings; instead, you should be able to use the product with just one additional click on 'Simulate.'"
Clicking "simulate" is like crossing wires trying to disarm a bomb. The best I can hope for is nothing happens.
That's been my experience with D Force after about four years of attempts.
REPLY
! REPORT
Pushee-Ri
Karma: 52,482
Wed, Jun 17'That's been my experience with D Force after about four years of attempts.'
My goodness — that sounds like hell!
I'd really like to help you get out of this dilemma... but I don't know where to start. Your PC setup sounds good. So that can't be the problem. The product (just one is enough—you don't have to list them all) is still unknown. Unfortunately, neither I nor anyone else can say anything about it.
My only suggestion would be: try one of the linked clothing items. With mine, you have the added advantage that they're very small (less than 4 MB each). If one (or more) of the linked and tested products doesn't work either, you'll at least know two things: 1) It's probably due to your PC / the DAZ version / the DAZ setup (see guy's comment above). 2) The problem isn't sitting in front of the monitor after all
My goodness — that sounds like hell!
I'd really like to help you get out of this dilemma... but I don't know where to start. Your PC setup sounds good. So that can't be the problem. The product (just one is enough—you don't have to list them all) is still unknown. Unfortunately, neither I nor anyone else can say anything about it.
My only suggestion would be: try one of the linked clothing items. With mine, you have the added advantage that they're very small (less than 4 MB each). If one (or more) of the linked and tested products doesn't work either, you'll at least know two things: 1) It's probably due to your PC / the DAZ version / the DAZ setup (see guy's comment above). 2) The problem isn't sitting in front of the monitor after all
I know a lot of the problem is me. I know I don't know what I'm doing. With a failure rate of 100% I haven't been able to learn anything.
REPLY
! REPORT