DForce Simulation NVidia Studio 522.30

Getting the following error when running dforce simulation using the studio drivers,as well as the latest gaming drivers. Also tried different clothing just in case, and tried with a basic genesis 8, 8.1 with several different clothes, nothing worked, same error appears in logs over and over.

2022-10-30 20:49:24.085 [WARNING] :: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce RTX 3080 Ti (Device 0).

2022-10-30 20:50:30.597 [WARNING] :: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce RTX 3080 Ti (Device 0).

2022-10-30 20:50:31.117 [WARNING] :: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce RTX 3080 Ti (Device 0).

2022-10-30 20:50:31.119 [WARNING] :: ..\..\..\src\dzdynamicsengine.cpp(2489): ERROR: clEnqueueMapBuffer (-36)
2022-10-30 20:50:31.169 [WARNING] :: ..\..\..\src\dzopenclkernelfactory.cpp(32): Open CL notify: Unknown error executing clFlush on NVIDIA GeForce RTX 3080 Ti (Device 0).

In addition, I did a clean NVidia driver install. All works fine when using CPU for simulation.

 

Comments

  • Most likely this is an issue with the curent nVidia drivers, you need to go back to a slightly older version (517.40 works) until their change log shows they have fixed the issue.

  • Question how do we roll back Nvidia drivers? I'm new to this card & don't know how to do this.

  • I figured it out :)

  • Richard Haseltine said:

    Most likely this is an issue with the curent nVidia drivers, you need to go back to a slightly older version (517.40 works) until their change log shows they have fixed the issue.

    Yeah, I'll just use CPU for now, don't have a lot to simulate, but thought I rase the issue. Another thing I see is that IRAY renderer is falling back to CPU a lot, so I'm guessing tons of non supported issues there as well 

  • IceDragonArtIceDragonArt Posts: 12,548
    Hmm I'm getting this error message too. I'll have to give this a try
Sign In or Register to comment.