Deforce ain't with me, clothing and hair ...
marty.russell56_7809659940
Posts: 47
Anyone else having problems with deforce clothing just sliding through your figure to the ground even though all collisions are checked correctly? At first I thought it was the shirt but tried other clothing items with same result. Also, at least certain of my deforce hairs aren't rendering, even though all the ''render in ...'' settings are checked. I'm (taking a big risk) and using 4.20.11 beta and just updated Nvidia driver to 4.15. Any suggestions, thoughts, inventive ideas to inflict pain on Daz?
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Have you tried a plane (with a decent number of divisions) coliding with a sphere? What tool is active - Tools menu? The non-rendering hair could certainly be down to having a geometry editing or set-up tool active.
I may have a geometry tool active from attempting to edit some clothing to prevent the sliding down. But the reason it's (maybe) still active is that it was sliding to begin with. I'll have to check, don't have it open now. Haven't tried the old plane/ball trick but, as I said, I have tried different clothing (and on different figures) with the same result: People dropping their clothes to the floor.
OK, I did have geometery tool active but switched it off and got the same result with clothing. So I tried plane/sphere and same thing. Plane goes through sphere.
Which tool is active now? You can't just switch tools off - you have to select a different tool.
I know certain tools will prevent dForce hair from rendering, but does any tool prevent collisions?
When you're using the sphere and plane to test dForce, what are your settings for the sphere and plane? DForce (and physics generally) require polygons to collide against, so if you're just making, say, a plane with 1 division, dForce doesn't have enough information to work with.
No, I did the whole deforce modifier apply and even subd'd the plane and it still went straight through the sphere.
With which tool active?
The navigator tool. I switched tools just so geometry tool wouldn't be active. Not sure how to turn it off or shut down all tools.
There is always an active tool, using one of the posing tools or the Node Selection is probably the most vanilla and least likely to cause conflicts but I'd think the Region Navigator would be safe too.
Thanks. No idea what caused this. I haven't fiddled with anything. Sims just suddenly stopped working. I've even tried them on an old 4.16 beta version I found on my computer which seems to be working otherwise but same result - no collisons with figures or objects.
Do you have a plugin such as ManFriday's dForce Companion installed? I've had that issue before when I've left that set to ignore certain items and forgot about it. Eventually I uninstalled it for that very reason.
No, nothing like that. Just plain old dforce. No special settings.
I know that dForce Companion doesn't do anything that I couldn't do myself, but I can't imagine working without it now because of how much time and effort it saves.
You may check that there's a dforce device available in the advanced tab. Also check the log for errors. Reinstall the gpu drivers.
Depending on the device you use for dforce you may get a different precision for collisions. Even with the same dforce parameters. For example my ati card is less precise than my nvidia card. Setting collisions to "best" may work better.
Maybe it's a typo, but I'm not aware of any NVIDIA driver numbered 4.15
I'm using the latest available Studio Driver for my GPU (an old1660ti) and that's numbered 512.15
Maybe that's your problem?
Thanks. May have misstated the latest Nvidia drive numbers but I have installed (clean install) the latest (March) studio driver update. I'm running a GTX 1660 TI GPU. One thing I haven't mentioned is that I've been getting a load of ''spring reports'' as the sim starts.
If you have added a dForce modifier yourself, then the Spring Reports are normal. It sounds like you may want to update your driver, or perhaps even re-install the same driver. That's always the first thing I do if anything gets strange in DAZ. Windows Updates often mess with GPU drivers. I assume you're downloading drivers direct from NVIDIA.
Yeah, directly from Nvidia. I've learned to always do a clean install from them and I know I have the latest version of studio driver, just did it a day or two ago. Thanks, never noticed the ''spring reports'' before. Glad to know that's normal.
GOOD NEWS! I should have tried this earlier. If something ain't working, unplug it and plug it back in. Had to shut down my computer last night because of severe thunderstorms in my area. When I turned it back on this morning, everything was working again in simulations. No rhyme or reason but it's working again. Duh.
Home PCs are not designed to stay turned on for a long time. That is what servers are designed for. As general rule it is good to turn off the PC at least every few days.