dForce simulation error - Fixed, follow up thread for bugged asset made
Briarcastle
Posts: 20
Woke up to some dForce errors. I wasn't having any issue with these scenes/objects the day before.
2025-06-05 04:55:00.132 [WARNING] :: \src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce RTX 4070 SUPER (Device 0).
2025-06-05 04:55:01.153 [WARNING] :: \src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce RTX 4070 SUPER (Device 0).
2025-06-05 04:55:01.153 [WARNING] :: \src\dzdynamicsengine.cpp(2498): ERROR: clEnqueueMapBuffer (-36)
2025-06-05 04:55:01.153 [WARNING] :: \src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce RTX 4070 SUPER (Device 0).
I replaced the Game Ready Drivers with the newest Studio Ready drivers and the issue is still occuring.
Nothing changed excepted turning DazStudio off and then back on the next day.
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
Just to troubleshoot some things.
I tried restarting the computer and started an empty scene, placed a basic Genesis 9, and used a hair that was previously simulating without issue the day before.
I recieved a "Error intializing Open CL Kernels"
2025-06-05 05:42:02.182 [WARNING] :: \src\dzdynamicsengine.cpp(427): Using device: NVIDIA GeForce RTX 4070 SUPER
2025-06-05 05:42:02.316 [WARNING] :: \src\dzopenclkernelfactory.cpp(401): ERROR: clCreateContext (-9999)
2025-06-05 05:42:02.316 [WARNING] :: \src\dzopenclkernelfactory.cpp(124): m_isValid = false @ dzopenclkernelfactory.h, line 36 (after setupContext())
2025-06-05 05:42:02.452 [WARNING] :: \src\dzdynamicsengine.cpp(3634): Error initializing OpenCL!
2025-06-05 05:42:02.452 [INFO] :: Total Simulation Time: 0.27 seconds
My PC is
Intel(R) Core(TM) Ultra 7 265K (20 CPUs), ~3.9GHz
Windows 11 Pro 64-bit (10.0, Build 26100)
65536MB RAM
NVIDIA GeForce RTX 4070 SUPER (updated to latest studio drivers)
And a 2TB/2TB/ and 4TB internal hard drives.
I'm just super confused. Everything was working fine yesterday. Nothing changed.
I uninstalled DazStudio and did my best to clear the nested files in user data.
Reinstalled, bloaded a blank genesis 9, loaded dforce hair and tried to simulate (I was trying to get it to recompile kernels.) and it looked lke the process went by so quick it didn't even do anything, but it just is resulting in the same errors.
And everything is taking much longer to load on 4.24 so that was a fun waste of time.
update: more confusingly, clothing seems to simulate without issue? No errors, no problems.
I'm kind of going asset by asset now but the majority of dforce hair is still causing errors.
So I think I've narrowed down the issue a little further.
Hair assets like "FE Cyberpunk Hair" and "dFroce Strand-Based Side Low Curly Hair" are kicking back errors. I know for sure FE Cyberpunk Hair was working without issue. I just picked up the second one today.
So - and I truly don't know why this would just start happening - Strand-Based Hairs are now incompatible with dforce simulations?
I think I figured out the issue. I purchased and added "dForce Strand-Based FE Side Low Curly Hair for Genesis 9" from FeSoul to my library this evening.
I just went through and removed all of it's files. Everything is fine now, I can simulate other FeSoul dForce hair and other vendor's hairs without any issue.
"dForce Strand-Based FE Side Low Curly Hair for Genesis 9" is bugged, and even when not in the scene, appeared to cause simulation issues.
How do I send in a ticket/report about this? I've never done it before.
I made a follow up thread specifically about this bugged asset here, since this specific issue is fixed. https://www.daz3d.com/forums/discussion/732951/dforce-strand-based-fe-side-low-curly-hair-for-genesis-9-breaking-dforce-simulation
So I went through a very confusing issue with dForce tonight as seem with my minor emotional meltdown here https://www.daz3d.com/forums/discussion/732926/dforce-simulation-error-with-dforce-strand-based-fe-side-low-curly-hair-for-genesis-9 and I narrowed it down to "dForce Strand-Based FE Side Low Curly Hair for Genesis 9" being the culprit, which I had just bought that night. I have no idea how to send in a support ticket so, just re-iterating the issue here and hoping for a fix for this nice looking asset.
After installing this hair asset - a majority of other hair assets would kick back simulation errors. After removing all of the assets files (I assume it's /data folder being the most important to remove), everything is back to normal, no simulation issues.
Link to product https://www.daz3d.com/dforce-strand-based-fe-side-low-curly-hair-for-genesis-9
I don't have it.
I can't imagine how one dForce hair can mess it up for all.
I tried to get to the readme to which files it included, but it just timed out.
Unless others can bring more information, I can only suggest to raise a ticket.
Hello there,
that is a very strange issue for one product to 'bug' the entire dforce hair library. I have never heard of that before. You can send a ticket via the help center.
Do let us know if you hear anything from the support team or the vendor. This is a very curious issue.
Toyen
Will do, thanks for informing me!
Merged threads since one follows the other directly.
I am not seeing any shared files in the File List that might be being applied too generally or overwriting others to break a general feature. You do usually need to restart DS after dForce has gone wonky, to be sure of getting a good simulation.
Hello, I have seen this issue and have submitted a modification package. It should be a parameter problem when storing assets. The good news is that the problem you mentioned has been solved. Here is a fix package, which only needs to be covered in the product catalog. The daz product download should also be updated later. Continuously improving user feedback is our basic obligation. Thank you very much, Briarcastle!
In addition, we tested it and it did not cause crashes or simulation problems in other products. Is it caused by other factors? We need to observe this further.
There