Tillerz

Hi, see screenshot. When zooming in/out or panning, then other random sections of some layers are not getting rendered (it's going through several layers) If I merge down the layers into one pixel layer, that bug even saves into this layer, so it's not just a visual problem on the screen, it's going deeper. Hardware Acceleration ON, Windows 11, RTX 4090, yesterday's nVidia drivers 537.42 With HW Acceleration OFF the bug disappears. EDIT: Okay, after another restart of Photo the problem is not reproducable right now. It looks that the previous session had some memory problem/corruption inside Photo maybe. I had 2-3 big documents with many layers open. As it now doesn't appear with neither HW Acc. on/off, I cannot confirm if it was an acceleration related problem.

Yay, thanks so much! \o/

You are right. Apparently AP 2 didn't assign itself properly to opening certain files, and clicking them indeed opened 1.x. I have renamed the old Affinity folder so that is doesn't happen again.

Hi, see topic.

Hi, can you please add .webp as output format to batch jobs? Most important thing needed right now. At least for me.

Are you talking about general speed or startup? Using AP was not slow before or is now either (for me), but the 1.9 versions took a TON of time to start up, and now this is even slower. It seems to use like 1 core for a minute, but it's jumping from 1 core to the next every second or something. And EVERYTHING is slow, the whole PC is unusable in that time. I have never seen a program doing that. And I have a fast PC and fast SSDs. My bet still is that there is some issue with font loading or something where it also parses a large XML or similar and is just busy traversing the file up and down. (I mean for THAT bug I at least have a workaround. Open AP, go make coffee, and then don't close it again for the whole day). But still it is annoying if you quickly want to edit something and haven't opened it yet, and you sit there, waiting for it to complete startup.

Well, on PC it seems to load stuff on startup, one big chunk are the fonts apparently. 99% of the time I do not use any fonts at all. And then WHEN I do, it's usually one of my 'favourite' fonts... maybe Photo can only load THESE by default and load the other fonts only on demand? Slowing down the startup of the app for 40 seconds or something for a nice font preview in the fonts dropdown is not reasonable. Also maybe this is something that could use parallel processing. As already written I see the usage of 1 full core which is jumping around from one core on the CPU to the next until the app responds again. There is a minimum of SSD access visible. But I wonder what makes the whole PC VERY slow in response during that time. It's only one core. There's lots of memory, there is zero traffic on network and like almost no access to the SSD (which is a super fast one, btw.) Somehow that loading process for fonts and whatever it is loading (brushes?) must hit a bottleneck somewhere

This is also an issue on Windows 10. I only have 1 plugin (FilterForge10) and AF was also slow starting without the plugin. Is this an issue with loading the fonts/macros/brushes? After starting Affinity Photo I see100% load on one core and the load is jumping around from one core to another random core, every half or full second (I have 16 on my AMD CPU). This slowness is a problem during every fresh AP start. It seems to be some kind of background task, as the UI shows up and I can do a few clicks or open the file dialog, and then right inbetween stuff AP gets reaaally slow and laggy, also the whole PC stalls somehow. Even opening Task Manager is greatly delayed. I can see no intense usage of GPU/CPU/Network/Memory or drives (all pretty new SSDs) except the 1 core being at 100% for like 30-45 seconds. Are the Affinity apps maybe probing network drives or something? And it's not my PC: Win10 Pro/64bit (latest patchlevel), AMD Ryzen 3800X, 64GB RAM, nVidia RTX 3080, Force MP600 NVMe SSD, 2x Samsung 870 QVO 4TB SSD. The Affinity apps are all installed on the fastest NVMe SSD. Sure there is a workaround... open it only once in the morning and then only minimize it. But still there must be a cause for that. And it is rather annoying of you want to "just quickly edit a small photo" ...