M1000 Posted November 23, 2022 Share Posted November 23, 2022 This is the CPU usage while only moving the cursor over the testfile I added. HighCPU.afphoto Quote Windows 10 Home 64 / AMD Ryzen 1700 @ 3.6 GHz / Asus Prime B350-Plus / 32 GB RAM / GeForce RTX 3060 12GB with latest studio drivers Affinity Suite V2 latest official versions Link to comment Share on other sites More sharing options...
NotMyFault Posted January 13 Share Posted January 13 This is probably by design and no bug. A get high CPU utilisation on Mac mini (up to about 50%), too whenever the PT filter is active, and a bit lower (30%) when inactive. As long as Photo renders the file correctly and with good refresh rate and reacts snappy to any user input there is no reason to assume any bug, as the sw works as designed. Quote Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected. Link to comment Share on other sites More sharing options...
M1000 Posted February 11 Author Share Posted February 11 On 1/13/2024 at 5:26 PM, NotMyFault said: with good refresh rate and reacts snappy to any user input And there's the problem. When I add a pixel layer and try too draw, it gets very choppy. And it also depends on the zoom level from usable at a low zoom level (7,5 %) too unusable at a high zoom level (100%). Added a video to demonstrate this. HighCPUvid.mp4 Quote Windows 10 Home 64 / AMD Ryzen 1700 @ 3.6 GHz / Asus Prime B350-Plus / 32 GB RAM / GeForce RTX 3060 12GB with latest studio drivers Affinity Suite V2 latest official versions Link to comment Share on other sites More sharing options...
NotMyFault Posted February 12 Share Posted February 12 That is correct, but probably unavoidable. I complained about the same issue long time ago. The Live mesh war and perspective filter have a computational complexity where every pixel depends on all other pixels in the document (not only visible, but out oof canvas areas, too). I don't think there will be any cure. Workaround: temporarily add rasterised copies of for PT filters, and deactivate PT. If you modify anything below, delete the temp layers and make a fresh copy. Quote Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. My posts focus on technical aspects and leave out most of social grease like „maybe“, „in my opinion“, „I might be wrong“ etc. just add copy/paste all these softeners from this signature to make reading more comfortable for you. Otherwise I’m a fine person which respects you and everyone and wants to be respected. Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.