Well, my previous thread on this has been locked, so I will carry on with a new one.
I’ve gotten back to work in SL12 today and have noticed sluggish issues/ hanging with typical workflow which had been working great during the trial and with SL11. I had thought it might be a windows update and planned obsolecence of Win10. Hmmm, that’s still not certain at this time on my machine.
Fortunately, I left the previous install of SL11. Well, I see that there is a “SpectraLayers 12” folder inside of the “SpectraLayers 12” folder on my programs drive. That is not the case for my SL11 install. Clearly my fault somewhere along the line. So, I’ll have to uninstall get it down to one folder named “SpectraLayers 12” and see if that clears up the buggy behaviour…cuz last week, before today’s KB5065429 and KB5065957, this install path has been working fine for SLP12.0.20.
hmmmm
SL11 working great…
I will uninstall/ re-install
hmmm, I have re-installed SLP 12.0.20 without the extra folder…still, some bizarros happening when using Cut To…
…freezes and sluggish performance, feels like a crash waiting to happen…maybe it’s a windows update thing, I dunno
I think SLP is using a cache system when working on these things. So it might be well worth checking the cache path in the settings. Per default it is in your Windows user path. You might set that cache path to your fastest drive (SSD).
1 Like
@Robert_Niessner Thanks so much for helping 
caching is the impression I get as well…a few hang-y sessions and eventually the cache feels indexed for SLP functions is what it seems like to me, but I really don’t know, I just write up what I experience. All my SLP work has the exe running off a year-old Kingston Fury M.2…which was previously a Samsung 960 Pro…maybe that’s why I tend to get reasonable performance with this old machine? I will check the path. All my slp jobs are on a 3 year old SSD 860 Pro
Still, I’ve had no issues until yesterday’s windows update…and win updates have hosed me before