Daz 4.10 freezes Win 10 when using Morph Sliders

notiusweb

Using 388.13 Nvidia driver on Win 10 Pro, every 3d application and renderer I use is fine.  But man, every time I move a morph slider in Daz, the system will every 10 seconds or so freeze, then unfreeze, and this pattern repeats over and over, even after closing down Daz.  So I have to re-boot the whole system.  When I use Daz, I use the numeric type-in fields instead, and it works fine.  I can predictably repeat it too, sometimes ity happens right away, other times I was lucky and it worked fine and then later would get screwy.

One time it even froze where it went to Blue Screen 'Machine Check Exception'.

Also, I noticed if I have several apps open (ie Browser), and if I switch back and forth, Daz then will go into a freezing pattern, but it does not repeat like it does when I use the sliders.  Just weird all around.  But just with Daz 4.10, and it happened in the Public build of 4.10 as well I had when I was using Win 7 64.   It works all fine if I just type in the values and stay in the app.  Never happened in 4.9 series of Daz on my machine.

 

Anyoneone else ever experience stuff like this? 

-Regards

nonesuch00

Best you can do until DAZ Studio is made more efficient is to 

1) Task Manager -> Details -> DAZ Studio -> Right Clight -> Set Affinity -> and uncheck 2 or even 3 of your CPU cores being used.

2) Go to DAZ Studio -> P references -> Display Properties -> Interface -> Display optimization -> Best

                                                                                                                      Hardware Anti-Aliasing - On

  as it's unlikely you changed them it's probably not a big help to your problem

Richard Haseltine

nonesuch00 said:

Best you can do until DAZ Studio is made more efficient is to 

1) Task Manager -> Details -> DAZ Studio -> Right Clight -> Set Affinity -> and uncheck 2 or even 3 of your CPU cores being used.

2) Go to DAZ Studio -> P references -> Display Properties -> Interface -> Display optimization -> Best

                                                                                                                      Hardware Anti-Aliasing - On

  as it's unlikely you changed them it's probably not a big help to your problem

That would help reduce the load from multi-thread processes (such as rendering), but I don't think moprh loading is multi-threaded.

notiusweb said:

Using 388.13 Nvidia driver on Win 10 Pro, every 3d application and renderer I use is fine.  But man, every time I move a morph slider in Daz, the system will every 10 seconds or so freeze, then unfreeze, and this pattern repeats over and over, even after closing down Daz.  So I have to re-boot the whole system.  When I use Daz, I use the numeric type-in fields instead, and it works fine.  I can predictably repeat it too, sometimes ity happens right away, other times I was lucky and it worked fine and then later would get screwy.

One time it even froze where it went to Blue Screen 'Machine Check Exception'.

Also, I noticed if I have several apps open (ie Browser), and if I switch back and forth, Daz then will go into a freezing pattern, but it does not repeat like it does when I use the sliders.  Just weird all around.  But just with Daz 4.10, and it happened in the Public build of 4.10 as well I had when I was using Win 7 64.   It works all fine if I just type in the values and stay in the app.  Never happened in 4.9 series of Daz on my machine.

 

Anyoneone else ever experience stuff like this? 

-Regards

The first time (in a session) that you set a slider to a non-zero value the moprh deltas (the actual changes in position of the vertices) have to be loaded from disc. However, that will happen regardless of how the non-zero value is applied. I suppose it's possible that your security software is kicking in when the drive is accessed and that might be genrating soem kind of conflicting activity, I can't think of many other ways such a simple act could trigger a cascade ending in a blue-screen.

nonesuch00

Richard Haseltine said:

nonesuch00 said:

Best you can do until DAZ Studio is made more efficient is to 

1) Task Manager -> Details -> DAZ Studio -> Right Clight -> Set Affinity -> and uncheck 2 or even 3 of your CPU cores being used.

2) Go to DAZ Studio -> P references -> Display Properties -> Interface -> Display optimization -> Best

                                                                                                                      Hardware Anti-Aliasing - On

  as it's unlikely you changed them it's probably not a big help to your problem

That would help reduce the load from multi-thread processes (such as rendering), but I don't think moprh loading is multi-threaded.

notiusweb said:

Using 388.13 Nvidia driver on Win 10 Pro, every 3d application and renderer I use is fine.  But man, every time I move a morph slider in Daz, the system will every 10 seconds or so freeze, then unfreeze, and this pattern repeats over and over, even after closing down Daz.  So I have to re-boot the whole system.  When I use Daz, I use the numeric type-in fields instead, and it works fine.  I can predictably repeat it too, sometimes ity happens right away, other times I was lucky and it worked fine and then later would get screwy.

One time it even froze where it went to Blue Screen 'Machine Check Exception'.

Also, I noticed if I have several apps open (ie Browser), and if I switch back and forth, Daz then will go into a freezing pattern, but it does not repeat like it does when I use the sliders.  Just weird all around.  But just with Daz 4.10, and it happened in the Public build of 4.10 as well I had when I was using Win 7 64.   It works all fine if I just type in the values and stay in the app.  Never happened in 4.9 series of Daz on my machine.

 

Anyoneone else ever experience stuff like this? 

-Regards

The first time (in a session) that you set a slider to a non-zero value the moprh deltas (the actual changes in position of the vertices) have to be loaded from disc. However, that will happen regardless of how the non-zero value is applied. I suppose it's possible that your security software is kicking in when the drive is accessed and that might be genrating soem kind of conflicting activity, I can't think of many other ways such a simple act could trigger a cascade ending in a blue-screen.

The morph loading itself wouldn't be multi-threaded but the redrawing of the viewport would be I think.

I just reset my 'Interface' in DS to defaults and restarted and that help a little bit, seems l choose one of the Interface values incorrectly. I only now only use 4 or 8 CPU cores for DS in my DS shortcut on my desktop, The hex code you need for that is hex F Use the windows command shell with this argument

 

"EXAMPLE: windows commandshell.exe" /c start "DAZ Studio" /affinity F "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\DAZStudio.exe"

 

change the DS executable path to match yours though.