![]() It will always fall back to CPU now, and if I force it to use GPU, it will not render at all. So I can perfectly reproduce this issue every time on two computers, and all I have to do is install Daz 4.14, and it breaks my GPU rendering. I tried on the other Mac Pro now, after making a backup of the hard drive for imaging in case it happened on that one too. After upgrading the other Mac Pro to 4.14, it did start having the exact same issues. But then I tried to upgrade to 4.14, assuming it would work now, and the same issue came back again immediately. Again, the only solution was to re-image the hard drive. ![]() So I assumed, the issue was something with other unknown variables associated with the install of the OS or DAZ. ![]() But then I tried imaging the SSD with a clone of the SSD from the other Mac Pro, so they both have the exact same OS and Daz and CUDA and everything. The issue persisted, and I was beginning to think it was my graphics card. I even tried to downgrade to 4.12 by copying my version of 4.12 from my other Mac Pro which had not yet updated to 4.14. I tried clearing the DAZ3d application support and preferences, creating a new user account with fresh settings, and reinstalling Daz and Daz central. When I upgraded one to 4.14 recently on one of them, it completely broke GPU rendering. They have been running 4.12 (and 4.12.1). I have 2 Mac Pros (5,1 and 3,1) each with a GTX 1070.
0 Comments
Leave a Reply. |