Luis Canau Posted August 16, 2021 Posted August 16, 2021 Hello, This bug was reported two years ago on this thread: It still occurs in Affinity Photo 1.10.0.1127. I can't use a keyboard shortcut or via a button on my Intuos. I have to do it manually, and when it's something you need to do often it's not very practical. Since it's a current bug I thought it should be on the 1.10 forum. Quote
Ron P. Posted August 16, 2021 Posted August 16, 2021 I agree, it still causes the program to crash. Quote Affinity Photo 2.5..; Affinity Designer 2.5..; Affinity Publisher 2.5..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD
Subclavius Posted August 16, 2021 Posted August 16, 2021 APhoto crashes for me too. I agree that this should be fixed since it causes the program to crash and is easily and consistently repeatable. @Luis Canau The only minor consolation is that the problem is not lost in the sense of being archived as it has a fault number: aw-3726 which is presumably still 'open'. Quote
SPaceBar Posted August 17, 2021 Posted August 17, 2021 HI @Luis Canau The issue has been logged as explained by @Subclavius and it's still open. I will add the details from this post and pass it on to the development team to give it a little bump. Quote
i5963c Posted August 17, 2021 Posted August 17, 2021 I just did a quick test on my machine, and I can confirm the consistent crash. Quote Windows 11 Pro - 24H2 | AMD Ryzen 9 3900X - 12 core - 3.8 GHz | 32GB DDR4 - 3.6 GHz RAM | Nvidia RTX 3060 - 12GB VRAM | 2TB SSD Samsung 970 EVO Plus | Wacom Intuos 4M Full Affinity Suite (Photo, Designer & Publisher): all version 2.6.0, Nvidia Studio drivers (560.94) Capture One 22 PRO (build 15.4.2.10) | Nik Collection (DXO version 4.3.6) | Topaz AI (Denoise 3.6.1, Sharpen 4.1.0 & Gigapixel 5.8.0)
Luis Canau Posted August 17, 2021 Author Posted August 17, 2021 4 hours ago, SPaceBar said: HI @Luis Canau The issue has been logged as explained by @Subclavius and it's still open. I will add the details from this post and pass it on to the development team to give it a little bump. Hi, Thank you both for the feedback. SPaceBar 1 Quote
Luis Canau Posted August 31, 2021 Author Posted August 31, 2021 Just noting it still occurs in 1.10.1.1142. Quote
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.