dnwls Posted July 3, 2022 Posted July 3, 2022 It's seem working fine on latest driver? Has AMD fixed the issue? I recently purchased affinity designer on pc, just tried the 1.9.0.932(which still allow amd rx5700 opencl acceleration), the gpu acceleration seems working fine to me, much faster than without gpu acceleration enable. The problem tho is I cant install both 1.9.0.932 and latest affinity designer in the same pc, is there way to fix this? Quote
Komatös Posted July 3, 2022 Posted July 3, 2022 Hi, @dnwls The short version: No. dnwls 1 Quote MAC mini M4 | MacOS Sequoia 15.2 | 16 GB RAM | 256 GB SSD AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.2605) Affinity Suite V 2.5.7 & Beta 2.6 (latest) Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF Ferengi Acquisition Rule No. 49: “A deal is a deal is a deal.”
NotMyFault Posted July 3, 2022 Posted July 3, 2022 7 hours ago, dnwls said: It's seem working fine on latest driver? Has AMD fixed the issue? I recently purchased affinity designer on pc, just tried the 1.9.0.932(which still allow amd rx5700 opencl acceleration), the gpu acceleration seems working fine to me, much faster than without gpu acceleration enable. The problem tho is I cant install both 1.9.0.932 and latest affinity designer in the same pc, is there way to fix this? You could use one beta version in parallel to one retail version. But Affinity recommends against using beta versions for productive use, as they often contain bugs fixed in later versions, and file format could be changed, so later retail version refuse to offer some beta documents. There are some betas almost identical to retail versions, but using them is on your own risk. while HW acceleration is faster in many cases, some filters or e.g. blend ranges lead to Photo falls back to unaccelerated. It really depends on your workflow. dnwls 1 Quote Mac mini M1 A2348 | MBP M3 Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K 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. I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.
Mel_P Posted July 3, 2022 Posted July 3, 2022 Well I have latest Affinity Photo and have just updated the AMD driver (end of June) on my RX6600 - no difference. STILL won't work if I try to tick hardware acceleration. Still waiting for action / feedback from somebody................AMD or Affinity. Quote
walt.farrell Posted July 3, 2022 Posted July 3, 2022 Just now, Mel_P said: Well I have latest Affinity Photo and have just updated the AMD driver (end of June) on my RX6600 - no difference. STILL won't work if I try to tick hardware acceleration. Still waiting for action / feedback from somebody................AMD or Affinity. The latest Affinity release (1.10.5) still has the restriction, so once AMD has a working driver you will need an updated Affinity release to support it. And once it is supported, I'm sure Serif will let us know. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
kkoukos Posted July 3, 2022 Posted July 3, 2022 I have been evaluating the compile latency of AMD drivers, using the code posted by the developers at github for a few months now (since i noticed the issue myself). https://github.com/MarkIngramUK/ocl-compile-benchmark My experimentation in Windows 11, starting from driver Adrenalin 21.10.2 all the way up the most recent Pro 22Q2 shows very reasonable latency with the latest (22Q2) being around 62-63ms on an RX6900. The best result on Windows was with the default Win11 driver (no AMD driver installed) with a latency slightly above 53ms, while with a small modification (of time measurement code) the same code can run in Linux. I tested it with the open source driver (in linux-kernel 5.17-5.18) the latency I measured was around 22ms. So, no matter how hard i tried to reproduce the issue (out of my own academic curiosity); i couldn't get any latency in the order of magnitude mentioned (of around 1400ms) in the github post (for the Radeon 5000 series). Sadly it also seems that all recent Affinity releases have this restriction, so there is now way to enable HW acceleration in the application and test it, if they don't remove this restriction in a future release. We can only hope that they address this issue at least in their next major release (v.2). And i personally don't see a reason for it any longer, although i understand that there might have been an issue affecting several users at a given point in time using a specific system configuration (OS, driver, etc). Even if for specific configurations this might still be the case, i believe they should make it at least possible to enable the hardware acceleration (even if we need to acknowledge the risk and modify some configuration file) in any OpenCL capable device, so that we can also measure the performance from the benchmark as well as in real test cases in the application and provide feedback back to the developers. dnwls, nitro912gr, Subclavius and 2 others 5 Quote
ziplock9000 Posted July 3, 2022 Posted July 3, 2022 3 hours ago, kkoukos said: I have been evaluating the compile latency of AMD drivers, using the code posted by the developers at github for a few months now (since i noticed the issue myself). https://github.com/MarkIngramUK/ocl-compile-benchmark My experimentation in Windows 11, starting from driver Adrenalin 21.10.2 all the way up the most recent Pro 22Q2 shows very reasonable latency with the latest (22Q2) being around 62-63ms on an RX6900. The best result on Windows was with the default Win11 driver (no AMD driver installed) with a latency slightly above 53ms, while with a small modification (of time measurement code) the same code can run in Linux. I tested it with the open source driver (in linux-kernel 5.17-5.18) the latency I measured was around 22ms. So, no matter how hard i tried to reproduce the issue (out of my own academic curiosity); i couldn't get any latency in the order of magnitude mentioned (of around 1400ms) in the github post (for the Radeon 5000 series). Sadly it also seems that all recent Affinity releases have this restriction, so there is now way to enable HW acceleration in the application and test it, if they don't remove this restriction in a future release. We can only hope that they address this issue at least in their next major release (v.2). And i personally don't see a reason for it any longer, although i understand that there might have been an issue affecting several users at a given point in time using a specific system configuration (OS, driver, etc). Even if for specific configurations this might still be the case, i believe they should make it at least possible to enable the hardware acceleration (even if we need to acknowledge the risk and modify some configuration file) in any OpenCL capable device, so that we can also measure the performance from the benchmark as well as in real test cases in the application and provide feedback back to the developers. Agreed. I've said this several times that the option should be put back for those who want to try anyway, with it defaulting to off. dnwls 1 Quote
nitro912gr Posted July 4, 2022 Posted July 4, 2022 On 7/3/2022 at 5:35 AM, dnwls said: It's seem working fine on latest driver? Has AMD fixed the issue? I recently purchased affinity designer on pc, just tried the 1.9.0.932(which still allow amd rx5700 opencl acceleration), the gpu acceleration seems working fine to me, much faster than without gpu acceleration enable. The problem tho is I cant install both 1.9.0.932 and latest affinity designer in the same pc, is there way to fix this? wait what? it works with older affinity versions? Quote Current Workstation: CPU: AMD Ryzen 5 5500 - MOBO: Asus B450 - RAM: 16GB DDR4 2667Mhz - GPU: AMD Radeon 7850 1GB NVMe SSD: Crusial P3 1TB M.2 - SSD: Samsung Evo 850 256GB - PSU: XFX TS450 - OS: Win10
dnwls Posted July 4, 2022 Posted July 4, 2022 @nitro912gr yes it works with the older version(v1.9.0.932), i believe rx5000 support removed after version 1.9.1(?). I'm not sure if everything work, so far I only tried some simple drawing with brush tool, opencl acceleration seems working fine to me. The raster brush was significantly faster, barely any delay/lag when opencl enabled. Quote
NotMyFault Posted July 4, 2022 Posted July 4, 2022 1 hour ago, nitro912gr said: wait what? it works with older affinity versions? introduced in 1.9.0 on 2021-02-04 removed for affected AMD gpu in 1.9.1 on 2021-02-25 Quote Mac mini M1 A2348 | MBP M3 Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K 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. I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.
nitro912gr Posted July 4, 2022 Posted July 4, 2022 oh yeah sorry, this problem is going for so long that I totally forgot that they disabled it due to poor performance... But I agree we should get the option back and see for ourselves if it worth it. I believe in my scenario at home that I have a Ryzen 2600 and Radeon 5500XT I will get better performance no matter what. dnwls 1 Quote Current Workstation: CPU: AMD Ryzen 5 5500 - MOBO: Asus B450 - RAM: 16GB DDR4 2667Mhz - GPU: AMD Radeon 7850 1GB NVMe SSD: Crusial P3 1TB M.2 - SSD: Samsung Evo 850 256GB - PSU: XFX TS450 - OS: Win10
ziplock9000 Posted July 4, 2022 Posted July 4, 2022 1 hour ago, nitro912gr said: oh yeah sorry, this problem is going for so long that I totally forgot that they disabled it due to poor performance... But I agree we should get the option back and see for ourselves if it worth it. I believe in my scenario at home that I have a Ryzen 2600 and Radeon 5500XT I will get better performance no matter what. Agreed. We should get an official response as to why we can't have this option back with a message that basically says "use at your own risk". Can we get that official response please? Quote
mb69 Posted July 4, 2022 Posted July 4, 2022 (edited) I'm posting just to bump this, I'm big fan of affinity as an adobe alternative but shooting yourself in the foot like this is ridiculous, just allow user to enable it and test it out with default being off. Also, why don't you offer paid major feature upgrades, maybe once in two years? With the speed and size of the updates it feels like you're struggling, I would gladly pay for proper new stable major version, I wonder if the current way is sustainable. Edited July 4, 2022 by mb69 Quote
omiK Posted July 9, 2022 Posted July 9, 2022 (edited) Any update on this issue? New drivers came a couple of weeks ago and i think we really need some kind of clarification after a year whitout a valid solution. Edited July 9, 2022 by omiK Tormy, Subclavius and PSDfield 3 Quote
Subclavius Posted July 12, 2022 Posted July 12, 2022 Seeing as everyone else is piling in here, I thought I would too. @omiK I agree. Some clarification at least would be useful and much appreciated. Perhaps a mooted v2 is what's stopping updates here? As a side note, in the latest release notes from AMD (22.6.1) there is a somewhat oblique reference to OpenCL performance with their drivers, viz "Lower than expected Folding@home™ compute performance with OpenCL™ API on some AMD Graphics Products such as the Radeon™ RX 6800" Although this impacts folding@home I wonder if it's related to the problem Serif reported. Maybe it means the the issue is (finally) bubbling its way to the surface as far as AMD are concerned. PSDfield and omiK 2 Quote
PSDfield Posted July 12, 2022 Posted July 12, 2022 38 minutes ago, Subclavius said: Seeing as everyone else is piling in here, I thought I would too. @omiK I agree. Some clarification at least would be useful and much appreciated. Perhaps a mooted v2 is what's stopping updates here? As a side note, in the latest release notes from AMD (22.6.1) there is a somewhat oblique reference to OpenCL performance with their drivers, viz "Lower than expected Folding@home™ compute performance with OpenCL™ API on some AMD Graphics Products such as the Radeon™ RX 6800" Although this impacts folding@home I wonder if it's related to the problem Serif reported. Maybe it means the the issue is (finally) bubbling its way to the surface as far as AMD are concerned. thx for checking that out, looks like there may still be hope for this issue Quote
Mel_P Posted July 21, 2022 Posted July 21, 2022 Has anybody found a way of leaving a message on an AMD site re this issue - I have visited their site and, like most companies, they seem to send you in loops circles and get nowhere - perhaps there is some AMD forum? Mel Quote
ziplock9000 Posted July 21, 2022 Posted July 21, 2022 46 minutes ago, Mel_P said: Has anybody found a way of leaving a message on an AMD site re this issue - I have visited their site and, like most companies, they seem to send you in loops circles and get nowhere - perhaps there is some AMD forum? Mel Serif need to be the ones doing this. Individuals will have no effect at all unless there was a huge number of us talking about a blockbuster game title. Quote
nitro912gr Posted July 21, 2022 Posted July 21, 2022 52 minutes ago, Mel_P said: Has anybody found a way of leaving a message on an AMD site re this issue - I have visited their site and, like most companies, they seem to send you in loops circles and get nowhere - perhaps there is some AMD forum? Mel Open Radeon software and find the bug icon (looks like a lady bug) press to report a bug. Quote Current Workstation: CPU: AMD Ryzen 5 5500 - MOBO: Asus B450 - RAM: 16GB DDR4 2667Mhz - GPU: AMD Radeon 7850 1GB NVMe SSD: Crusial P3 1TB M.2 - SSD: Samsung Evo 850 256GB - PSU: XFX TS450 - OS: Win10
Mel_P Posted July 21, 2022 Posted July 21, 2022 1 hour ago, nitro912gr said: Open Radeon software and find the bug icon (looks like a lady bug) press to report a bug. Thanks Quote
mb69 Posted July 27, 2022 Posted July 27, 2022 (edited) by the way davinci resolve is apparently using opencl for its gpu accel on my 6600 card and it is running very well... I would pay 20 usd no problem for proper gpu accel for affinity. But I guess they have the stats and amd card users are probably such a small percentage of the userbase, multiplied by small percentage that have heavy enough use cases to even care about the gpu accel, that they decided not to bother. Back to photoshop I guess, shame, it really felt great with the GPU, not even the big operations but the general responsivness of the layer stack gui etc... Edited July 27, 2022 by mb69 Quote
ysbuff Posted August 1, 2022 Posted August 1, 2022 Since this is an ongoing issue, Serif should state that support for Radeon Graphics cards is limited and they recommend nVidia GPU. I just bought Radeon 6700 XT and after installing it and discovering this problem, I feel like an idiot. Serif should be the one to deal with AMD, not the users. Quote
Mel_P Posted August 1, 2022 Posted August 1, 2022 4 hours ago, ysbuff said: Since this is an ongoing issue, Serif should state that support for Radeon Graphics cards is limited and they recommend nVidia GPU. I just bought Radeon 6700 XT and after installing it and discovering this problem, I feel like an idiot. Serif should be the one to deal with AMD, not the users. I have an RX 6600 - similarily totally hacked off! Quote
Nox Posted August 3, 2022 Posted August 3, 2022 I just bought a RX 6800 XT and finally switched from my 1060, a purchase for which I have saved money for over 2 years. I'm experiencing worse performance in my project files than before, now I'm here, read the thread and my disappointment is unmeasurable... Quote
nitro912gr Posted August 4, 2022 Posted August 4, 2022 13 hours ago, Nox said: I just bought a RX 6800 XT and finally switched from my 1060, a purchase for which I have saved money for over 2 years. I'm experiencing worse performance in my project files than before, now I'm here, read the thread and my disappointment is unmeasurable... I though about having 2 different GPUs to avoid this stupid problem in my other system where I have the 5500XT, I was told that it is possible to have an nvidia alongside the amd GPU and check in affinity to use the nvidia one. Stupid? yeah, but it can be a temporary solution till serif decide to tell us more on the topic or fix it with amd, if you still have the 1060 around. Quote Current Workstation: CPU: AMD Ryzen 5 5500 - MOBO: Asus B450 - RAM: 16GB DDR4 2667Mhz - GPU: AMD Radeon 7850 1GB NVMe SSD: Crusial P3 1TB M.2 - SSD: Samsung Evo 850 256GB - PSU: XFX TS450 - OS: Win10
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.