It's been a while since I first opened this thread so maybe you have forgotten, but the original issue I was pointing out with Rainmeter and Image meters is the fact that even if you load an image with W/H set to small dimensions, it still treats the image as its original resolution, so using transition effects on larger images (say, anything shot with a modern smartphone) can greatly spike the GPU and can even cause overall system lag on lower-end hardware. I'm trying to mitigate this since I personally consider having transition effects important in this skin suite I'm working on, as low-priority as it probably should be, lol.Thanks for sharing your approach. Honestly, to me it seems like you're adding a largely unnecessary step with PS, when Rainmeter can resize images too via W and H and without involving the slow writing of a file to the drive, in a single step - but who knows, maybe PS does it more efficiently than Rainmeter. Not sure about the transition either, if you still do it or not, as that spiked the CPU as well. Yes, the CPU usage getting higher on execution is normal and unavoidable, I guess you could simply compare your previous approach and this one, to choose the approach that takes the least CPU and still does what you want it to do.
Statistics: Posted by DanTheGuy720 — Yesterday, 4:21 am