HELP: Window Update to Driver made DForce Stop working

almeidap

  I've posted this before and no real answer yet, but now I have a bit more information.

1.   Inter (R) HD Graphics 630 was updated 21 May 2020

2.  Prior to that date Dforce was working  (I had to search through images I name each image using yearmonthdatetime  202006262020  (June 26, 2020 8:20PM)

3.  I can't roll back to the previous version (not listed in roll back/restore point) or if there is another way I don't know how

4.  Does anyone have a fix

5.  DazStudio 4.12  64   Windows 10 

 

  Any help would be super appreaciated!

 

Thanks.

ParallaxCreates

Follow this link: https://downloadcenter.intel.com/product/98909

If you click on "Show More" you will see older drivers for your integrated graphics card though I suspect that may not be the issue. Try that and see what happens.

Good luck.

almeidap

 Thanks,  you.  I tried that but since I already have the 'better' one it won't let me touch it.

kenshaw011267

Did you download and save it? If not do so and then get DDU. Do a clean uninstall and install.

almeidap

downloaded, unistalled the old but windows finds 'the best' driver and I'm back to square one.  I just may upgrage and buy a nvd or radeon graphics card

almeidap

Just upgraded my memory from 8 to 16GBs....still nothing on the DForce issue tho' :(

kenshaw011267

almeidap said:

downloaded, unistalled the old but windows finds 'the best' driver and I'm back to square one.  I just may upgrage and buy a nvd or radeon graphics card

You can turn off windows updating drivers.

Google "Turn off automatic driver updates Windows 10"

Mythocentric

I suspect that the graphics card drivers are not in fact the problem but Microsoft and it’s somewhat erratic updates being the root of the problems we are having with dForce. Given that others are commenting on problems with their chosen 3D programs following Microsofts latest round of updates, also that they are coming from people with far more experience than me (see latest Renderosity magazine issue!) I am inclined to attribute the current state of affairs to Microsoft’s poorly executed updates of late especially where Windows 10 is concerned.

My own experience is as follows:

I currently run DS on two separate laptops, one a HP running an Intel graphics card. I purchased this to keep me working when my previous machine (Acer) suffered a hard drive failure and until repairs could be effected. This has now been completed with the only other change being an ‘upgrade’ from Windows 8 to Windows 10 on the Acer. Specs are pretty much similar with 8 gb RAM. The main difference being that the Acer retains its nVidia graphics card.

In a nutshell, two machines running different graphics cards and different drivers, both of which are the latest versions for their respective cards. While I could accept that problem’s could potentially arise on one machine because of a driver glitch, experiencing the same problem on two different machines with different drivers is too much a stretch of the imagination. Both machines were handling dForce (which was a major reason for me switching to DS and which constitutes a major part of my work) without problems right up until Microsoft’s round of updates a couple of weeks back immediately following which dForce went up the Swannee with the HP receiving the updates and failing followed by the Acer the following day which is when I updated that machine.

What I am now left with is slightly different on both machines. On the HP I load the figure, dForce clothing and add the pose. Hit Simulate which results in DS loading dForce kernals, followed by a window telling me that DS is recovering/restoring files (which has never happened before the updates) and apparantly comprises of looking for the files which make up the scene before beginning the simulation which freezes at one second. And there ends the story with the only option I have is to turn off the laptop to escape. Pressing Cancel only results in me being told the program is not responding. The Acer is slightly different with everything proceeding up to hitting Simulation which produces the same windows, including that strange recovering/restoring files thing after which the simulation sometimes runs as it should (but not always). The problems start after that with any consequent item of Dforce clothing loading but being invisible. I.E. The item appears to load, is listed in the Scene tab but is invisible in the viewport. I can select it in the Scene tab but any attempt to Simulate it results in the program freezing as with the HP. And that’s as far as the story goes so far. I’ve invested an awful lot of money in DS of late because it has a lot going for it which I have come to appreciate having been disparaging in the past. I trust I can continue that process and that Microsoft gets its act together and puts things right ASAP. I really would hate having to go back to Poser because of something for which Daz has no responsibility. We can only wait and hope!