nitro912gr

@Eroica yes, brush performance on amd cards is abysmal, especially with rdna1 and 2 cards.

i got my hands on intel arc A750 - i have to play around with it some more, but with a ryzen 5 3600 @4,3 ghz the gpu scores 8000 points in raster single gpu. gonna upload the screenshot later, its saved on my testbench in the basement.

considering @debraspicher had an rtx3080 score 10500 points here, with a faster cpu, the result for the intel gpu is actually quite good when you look at the price of just $290 for the A750.

It is really nice that Serif has finally enabled OpenCL support for AMD GPUs on v.2.0. Please keep it that way !!!
Through some testing i came to the conclusion that it really works. Lets look, not only the benchmark but also some real case performance. I am using the latest AMD Pro Driver 22.Q4 but even with Windows 11 default driver v.30 or v.31 it still works great. Actually Windows 11 store driver v.30 might be slightly better. When looking at the benchmark result, it is really low for the GPU tested (i have an RX 6900 XT), compared to the results at the thread below:
When this GPU is used in Metal it is capable of a score of nearly 50000. When measured on Windows 11 i got only slightly more than 1000 (the result between versions are not directly comparable and is used just indicatively). So where does the difference of 50x comes from , and does it really matter?
If you look at the picture below, i run the benchmark and in parallel i simply have the Windows performance monitor showing what's going on. The result in the graphs includes only the benchmark in it's full duration. A close look on the graphs, can clearly explain why the performance is so low. During the benchmark the CPU is continuously utilized at almost 100% during the entire duration, even when GPU execution is taking place. It seems to me that GPU performance is actually throttled by the CPU capability to JIT compile the OpenCL kernels. So, no matter what GPU you have RX 5500, or RX 5700 or RX 6900 the result will be pretty much the same, because it's anyway limited by the CPU ability to compile the kernels. Similarly if the CPU can compile and spawn kernels at a higher rate, most likely the GPU performance will increase. Now if we take a look at the GPU performance, we observe that the GPU is utilized at a peak of less than 15%. NVIDIA's implementation (and i believe the same applies to Apple's Metal) pre-caches compiled OpenCL kernels, and as a result the benchmark result is substantially higher just because the CPU doesn't need to recompile the kernels.
But the most interesting question is does it really matter? To find out if the low benchmark result somewhat affects the user experience i stitched a large panorama, exported it on a large 16bit tiff and reloaded it (without layers or anything else); and started testing the live blur filters. To my surprise, the behavior of the application was excellent. Those filters that were implemented to use the GPU have been working really smooth, and flawless. Monitoring the GPU activity i verified that there was copy and compute activity. The compute activity was actually higher than in the benchmark but still resulted in device under-utilization, which is pretty normal considering that most likely i didn't have enough data to fully utilize the GPU. To conclude, i think it's really great that Serif has finally enabled OpenCL acceleration on AMD GPUs. The benchmark results might be on the low side but this i believe doesn't necessarily translate to bad user experience, as i believe the typical usage scenario when you apply an OpenCL filter is to spent at least a few seconds until you get the right result. And there is of course plenty of room for optimization for the developers (e.g., manual kernel pre-caching and compilation at startup, etc), although i don't think it's needed. The typical overhead of the driver (as i measured it using hello-world like code) is in the range of a few ms (50-70), so it should be completely unnoticed even if it happens at filter loading.
So don't stick to the benchmark, test it out
 

Hi,
My results are on same version of Affinity Photo V2 2.0.0.1640.
I have some PCs.
Ryzen 9 3900X/64GB 3200MHz/Radeon RX6800
Ryzen 5 1600AF/32GB 2666MHz/GeForce GTX 1070

Benchmark is running a different version and so your results are not comparable with the V1.9 measurements. Therefore, it's likely it's scoring or measuring GPU differently, not that your performance is necessarily diminished. I'm getting about 10K single/up to 7000 combined on a 3080, whereas before I was getting as high as 22K single. If you go one post up, you can see my old results. My performance is better overall in V2 as far as I can tell.
I actually tested the 3900X at some point on V1 on the same setup.
 

As much as I would like to believe in that, it is almost above 2 years so...
From other hand, once I had a problem with Substance Painter and AMD did provide me a beta driver within a week after I politely nag (only once) one of the higher-ups in Radeon structures.
I don't know, maybe we Radeon and Affinity users have to put some polite and civilized pressure on AMD to finally do something about that. Or if they have something wrong with their architecture that creates this issue, to at last admit it in our face.

Just updated to designer 2, 5500XT 4GB is working with GPGPU acceleration again.

The best part is they worked just fine from 1 to 2

Would it be useful to have a topic indicating where various settings are stored? For example, I've tried importing my Favourite fonts (Fonts.xml) and the relative locations differ between V1 and V2, as shown below...
V1 = C:\Users\ME\AppData\Roaming\Affinity\Designer\1.0\Settings\Fonts.xml
V2 = C:\Users\ME\.affinity\Designer\2.0\Settings\Fonts.xml
I seem to have managed it - time will tell.

The file formats are common among the three Affinity applications, and therefore when you Open an application in Designer that you created in Publisher there are many functions that need to work, even though they are not native functions in Designer.
Designer will handle linked text frames if you set them up in Publisher, but creating linked text frames is intentionally a Publisher-only function.

Photo V2 can enable OpenCL acceleration with my RX6800 and adrenalin 22.10.3 on Windows 11.
Serif may not update V1 anymore, I use V2 from now.

We're not changing anything and our apps will continue to include Pantone colours.

This topic is about AMD RX graphics, and you seem to have Nvidia RTX graphics, so it does not sound like the same issue. 
I think you should post your own topic, and provide some additional info such as a screenshot of your Performance Preferences in the application. Also, a screenshot of the output of the dxdiag command might be useful. I can't check right now but I think we'd want to see the Display tab for each of your GPUs.

If the Affinity apps are crashing when typing into the Font selection box please uninstall the following updates dependant on your version of Windows:
Windows 11: KB5017264, KB5017267, KB5017271, KB5017859, KB5018341, KB5018546, KB5018859, KB5020695, KB5020617 
Windows 10: KB5013887, KB5017262, KB5017266, KB5017858, KB5018329, KB5018543, KB5018544, KB5018545, KB5020613
Some users have also reported crashes/issues when placing images, updating resources, adding pages, amending table columns and converting colour profiles. If you're suddenly experiencing crashes when performing actions which worked previously it is also recommended that these updates be uninstalled. 
If you're unsure on how to uninstall these updates, please follow the below:
Press the Windows Key + R and enter 'Control Panel' Go to 'Uninstall a program' Select 'View Installed updates' Find the associated KB number, right click and select 'Uninstall' Restart your PC On Windows 11 you may need to press the Windows Key and search for 'Uninstall Updates'. You will then be able to uninstall the relevant update.
This update can then be hidden to prevent it being installed with future updates by following the guide in the link below.
https://pureinfotech.com/show-hide-updates-windows-11/

If you want to select everything inside the rectangle with a view to moving those items outside the rectangle then simply group those items inside the rectangle as @N.P.M. mentioned either as a whole or in relevant groups...

It looks as though you have the Rectangle selected when you select Release which will move it and all it's contents to be outside the Artboard. If you only want individual layers to appear outside you rectangle but still on the Artboard then you need to select the layers themselves and then right click and select Release...

on gaming side they are fine, this is what hurts actually. I enjoy my games with the 5500XT for the last 2 years with zero issues, but this thing with the openCL is biting bad right now.

To be clear, "on gaming side", I mean that even that crowd is aware the driver issues that can exist or just bad updates. Vast majority of people play games fine on the hardware. The hardware itself is excellent. Just drivers in specific situations/workstation setups and maybe specific graphics settings. My husband was using AMD in his rig until very recently, but moved to Nvidia when I updated mainly because there was a hack around it for pool-mining. The GPU will probably end up in a Linux rig eventually.

on gaming side they are fine, this is what hurts actually. I enjoy my games with the 5500XT for the last 2 years with zero issues, but this thing with the openCL is biting bad right now.

on gaming side they are fine, this is what hurts actually. I enjoy my games with the 5500XT for the last 2 years with zero issues, but this thing with the openCL is biting bad right now.

Just to clarify this slightly, OpenCL is not utilised widespread across an entire app and is mainly used for specific functionality—e.g. Photoshop uses hardware acceleration for a small subset of its functionality like the blur gallery, camera raw development, neural filters and some selection tools (source: https://helpx.adobe.com/uk/photoshop/kb/photoshop-cc-gpu-card-faq.html). In fact, on that page OpenCL appears to be used very sparsely:
Affinity Photo leverages hardware acceleration for practically all raster operations in the software—from basic resampling to expensive live filter compositing—requiring many different permutations of kernels to be compiled on the fly. Every time you add a new live filter or apply a destructive filter, paint with a brush tool, add an adjustment layer or perform many other operations, these all need to load kernels for hardware acceleration. With the majority of GPUs and driver combinations, this kernel compilation time is more or less negligible, but as Mark has posted previously with benchmarks, the Navi architecture with its current drivers appears to be problematic here. Any kind of comparison to Photoshop's OpenCL implementation is not appropriate, as the two apps use it very differently.
I previously had a 5700XT, and loading a single RAW image was painfully slow because a number of kernels needed to be compiled simultaneously (for all the standard adjustments you can apply in the Develop Persona). We're talking almost a minute from loading in a RAW file to being able to move sliders around. The previous Polaris generation of cards are, to my understanding, absolutely fine with OpenCL kernel compilation.

Adobe products use OpenCL on AMD GPUs, they have zero issues running on there. DaVinci Resolve uses OpenCL, but surprisingly it doesn't have any issues on AMD either.
Blender switched from OpenCL to HIP on AMD GPUs, because this API is more reliable, versatile, faster, future proof and very similar to CUDA. Also OpenCL as a whole has really big problems in general, it's hard and annoying to implement for hardware manufacturers, that's why everyone sticks to 2.0. OpenCL 3.0 is a big reset which makes most features optional because Khronos (standardisation organisation) has realized 2.0+ was a big mistake.
Serif has 3 options to handle this:
- fix the OpenCL bug like all other creative apps, make use of OpenCL 3.0's feature query function in the future.
- think straigh forward, future proof and switch to a better API (HIP and CUDA)
- or just do nothing and blame AMD for not supporting a broken API
Obviously the latter option does not fix anything.

Went here to have some news, and we have the same problem! AMD is really slow.

Soooo I guess this still hasn't been resolved yet? I'm on latest RTM build of Windows 11 and still can't enable hardware acceleration on my RX5600.

please follow up with that other applications have somehow fixed this problem so how is it still on AMD's side if others made it work?
I still don't understand why the silence here.

Can't disagree with that, the low entry price make it easy to jump in. Also the big sale point was that designer (that I use mostly) perform 10fold better and utilize the modern hardware, unlike adobe illustrator that refuse to see more than a core (not that designer use them all the time, but I have noticed way more utilization and many times hit 100% of CPU usage).
But the hardware that is having problem now is not some cheap intel integrated GPU, are top tier AMD cards and that's what it bites hard.
And atm I honestly believe that AMD GPUs are offering a better value than nVidia (that had the audacity to charge 200 euros for 1630). That being said I don't disagree that changing GPUs is not the way to fix to the problem, if you are not about to upgrade anyway.
Anyway, the biggest issue here is the lack of input from serif themselves, they don't say anything about it here, they don't even bother to upgrade the system requirements so people at least know, they still state that all you need for GPU acceleration is a DX 12.0 GPU.
And honestly I think the apps now are leaning more heavy on GPU than on CPU because with no GPU acceleration the performance is horrible, something that I didn't noticed before they introduce GPU acceleration.