...4.5 stalling out with Silkessence and Fisty's Sparkles
...over the last couple days I've been experiencing 4.5 "freezing up" with a Windows "Not Responding" error when trying to apply textures using Silkessence (Fabricator) and Fisty's Sparkles in the surfacing tab on some clothing content. The two clothing items I was using when the conflict arose are the Classy Swimsuit and the Mall Girl Jacket in different scenes.
I ran an extensive number of tests, just using one figure with no other props background or lighting (just using the preview lights) trying different approaches, and in all instances, the application would stall.
The version of Studio I am running is 126.96.36.199 (which is the most recent "stable" version) on WIn7 Premium 64 bit (build #7006) with the most recent updates.
With the both items all the Silkessence textures it to lock up while only the Velvet textures in Sparkles do so. I zeroed out the original shaders (selecting "None" in the Surfaces tab) before applying the textures, but that didn't help. I even uninstalled/reinstalled all the Fabricator plugins as well as the swimsuit, yet the issue still persists in every test I ran.
I am unable to view any logfile to determine the possible cause when this occurs as the application doesn't exactly "crash" (which would normally generate the usual crash report that could be filed with a support ticket). For some reason Win7 has me locked out of the Application Data folder where this is is stored (as well as other ones like "My Documents", "Start Menu" etc) even though I have "Administrator" status (another can of worms I've been dealing with to no avail).
I find this issue of the application stalling to be rather frustrating after spending nearly eighteen months researching components, hardware compatibility, system design, and dropping over 1,200$ to build a system that should be able to handle the demands. It has more than enough processing power (8 threads) and Memory (12G) as well as a dedicated GPU with 1GB VRAM with the most up to date drivers (OpenGL 4.3). I've also used the Fabricator and it's expansions on my old 32 bit XP system (that had the old Intel Integrated Chipset) without such issues, so this really doesn't make any sense as to why I'm running into this on a system with far superior processing and memory resources.
When I monitor the application's performance in Task Manager, it shows minimal CPU and memory load at the time. In the processes tab, the Daz Studio process shows absolutely no change in activity whatsoever in either CPU usage or memory committed. For all intents and purposes it appears to be hung up in some kind of infinite loop which can only be exited by ending the entire process tree thus shutting down the programme. I cannot even save the scene after the shader change as clicking on anything in the UI sends teh application into the "Not Responding" loop.
The only conclusion I can arrive at is that it must be some kind of odd bug in 4.5 that is triggered by these particular mesh and shader combinations (and who knows which others I haven't run into yet?) along with possibly something in the way Win7 handles the operation.