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
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Agreed. Especially since dForce is completely reliant on OpenCL which is no longer supported by AMD, especially in their newer processor chipsets.
Testing a dated but highly reliable GTX960 with the latest drivers from nVidia on an AMD X470 chipset was a total failure for OpenCL. Unless AMD is forced to re-support OpenCL by either nVidia or the users, OpenCL & dForce is now usable on an Intel-only platform for Windows 10.
You are misinformed about AMD not supporting openCL anymore. One of the main selling points they use in selling their ProRenderer is that it uses only openCL and so is portable across hardware and software platforms.
Uh I have a Ryzen 3 Win10 PC and it works
Setting aside the factual accuracy of your statements, how exactly would you propose Nvidia “force” AMD to support OpenCL?
interestingly it stopped working in my other intel machine with the latest driver for the integrated graphics chip on the motherboard and I had to install an older driver, it works very well there now but of course no graphics card so only CPU for iray which is not actually too bad on that better machine.
Windoze has an annoying tendancy of installing a made-by-THEM video card driver, instead of the one from the manufacturer of that card... and the Microshaft version typically leaves OUT the features you bought the card for. 0o When you have a feature like OpenCL suddenly stop working due to a driver update, probably best to go directly to the card maker's website and grab the latest driver from there.
You are misinformed about AMD not supporting openCL anymore. One of the main selling points they use in selling their ProRenderer is that it uses only openCL and so is portable across hardware and software platforms.
Then I challenge you to find the OpenCL support for the x470 chipset on their website instead of this nebulous OpenApp they've announced to "compete" with OpenCL.
OpenCL SDKs & Driver pages along with almost every reference to OpenCL has been deleted from AMD's website, and their support staff along with ASUS' people have been thoroughly unwilling to do anything when I brought this issue to their attention.
They one way nVidia can force AMD is through the courts by proving that AMD has unfairly devalued their products by denying 3rd party features (OpenCL) to connect between the video card & OS through their chipsets in an anticompetitive manner.
If a 2nd party were to spend the wad of time & money it will take to develop machine-level OpenCL drivers for AMD Chipsets, that lets AMD out of their warranty if you use it.
I have been using AMD's chipset drivers & video drivers from nVidia (which have OpenCL buit into them). I even tried ASUS's chipset drivers & they also failed. The OpenCL block is in the chipset smack between the OS & video card, and appears to be an attempt to push AMDs preferred OpenApp standard over the OpenCL championed by their competitor in only one of AMD's 3 main product lines.
Opencl is only supported for graphics chipsets, including integrated graphics on apus, including ryzen apus. So it's not something you find in the chipset drivers, but you find it in the graphics drivers.
Dforce clothing simulations will be much slower with hair in the scene, so I usually load hair after I have the simulation done.
Typically the clothing explosion happens when the figure geometry intersects with other geometry in the scene at some point during the simulation, so I typically do the simulation on the figure outside of my scene and save the results as a scene subset -- which can then be loaded into my target scene. Likewise I have found sometimes poorly made poses that have self-intersection can cause explosions...
Just doing those 2 things consistently allows me to use Dforce clothing quickly and successfully more often than not.
Better than that all you have to do is use the AMD Pro Renderer in Blender on a X470 motherboard to know that openCL is still running on motherboards that use a X470 chipset. openCL is a graphics protocol not a motherboard I/O protocol.
You are getting the numbers confused between the line of AMD 470 GPUs and the AMD AM4 motherboard with the X470 I/O chipset. It's not your fault, I am surprised AMD management didn't have their product developers rename the X470 & X570 motherboard chipsets to something that didn't imply that they are required to run a RX 470 or RX 570 or RX 5700 and so on GPU. Pretty wierd of them to do that when those video cards are so popular.
I had heard that for clothing that is dforce optional that vendors are required to rig enough morphs that is still worthwhile for ppl to want to purchase it for non-dforce use.
well a lot of what I bought lately those morphs are pretty useless, the Gate guardian outfit I last mentioned it pokes though the coat regardless of any morphs and even dforce, I had to add a geoshell to the character and collide it against that to use it even with Dforce.
This was after applying every loosen morph on it and the overlaying garments.
Even though I usually manage to make dForce "ready" clothing work as expected, there often are moments where I wish for the PA to have added some basic morphs for just some basic moves, as it can get a wee bit tedious to try out poses in a set to find the right one and each time having to go through the dForcing process...
Luckily there are some vendors who do that. Too bad many of them don't sell here at the DAZ shop...
There is so much wasted time trying to pose, simulate, get the wrong results and having to start over. If it wasn't so time consuming, it almost would be worth it. I agree the better developers provide good morphs to get you part of the way ther and give you more reliable results