phoenixart

[source: https://twitter.com/affinitybyserif/status/1570728566350020608]
 

I want to believe you. But also I want you to know that at this instant moment, you are haemorrhaging your trust and credibility at the creative community on Mastodon. I can see nothing but despair and deception on my timeline.

We were sold version 2 on the understanding that all point releases would be free. If 2.5 turns out to be a paid upgrade, huge swathes of users will abandon ship.

A few days ago I bought V2 universal and now I wish I didn't. If you will get subscription I think your software will die. It is okay to pay for a new major Version. But if you force to pay with a subscription, you will loose your fans and customers.

I must say this was a shock but not a good one - Canva also bought SMARTMOCKUPS.COM which was amazing and now they are shutting it down - I do hope this is not the case with Affinity.
Canva have the cash and resources and do make the final decision which is a shame. All this companies say at the beginning no no we will be independent but in reality that will not be the case.

Yeah, I’ve not a good feeling about it. 
 
That reads to me as, from v3 it’ll be different. 
 
I really really hope we don’t get any Canva crap to deal with and subscription stays away. I’m not that loyal. 
 
 

We’ve all been around the block and saw what happened to PaintShopPro when Corel acquired it (and how it turned into a bloated horrible mess). I feel sad that the Affinity apps will head in the same direction. Really is a sad day. 

Oh well. It was fun whilst it lasted. As soon as you become a £100 a year subscription service (which you will), I'll just go back to Adobe.
 

I love you guys, and I have a big load of respect about you, being a big evangelist of Affinity, but I'm not having a good felling on this. Canva is not what I could name a "professional software" partner. They want to be Adobe, not an adobe alternative.
The first insinuation of subscription model will break any trust on Affinity, and for the love of the goddess, I hope Affinity apps don't become a dumpster of stupid and crappy AI and cheap design tools that Canva really is.
I've read the FAQs you published… they don't give me enough reassessment that nothing is gonna change. Your company and your project is not yours anymore.
I wish to be wrong.

The only question is whether Affinity will offer a subscription in the future? I have bought a lot of brushes for your software. Especially on the Ipad, I am not willing to pay any subscription fees. I have purchased your software twice (v1. & v2). You say there are no plans for subscriptions at this time. But just wait until the Canva bosses change their minds, because greed is a virus in upper management. RIP, Adobe Alternative. 

When you save a macro, you will find it in the Library panel

Yep, that's what I thought. Just a minor UI difference. Only a bit confusing at first, I thought I was doing something wrong.

If they would just fix the open bugs, that would be equivalent to a major release.  So many features that are unusable.

OK so I think I've found a possible workaround for your dev team to fix the bug in Affinity Photo 1.10.4.
If I use Affinity Photo and try to use it as normal, it will crash early on (every session - guaranteed) - especially if I use "File>Open" or "File>Import".
If however, I open Windows File Explorer first and minimise it, then open Affinity Photo. It doesn't crash at all.
If I drag-and-drop files from Desktop or Windows File Explorer onto Affinity Photo, also works fine.

In conclusion, the bug is definitely something to do with the file-browser or the way affinity caches its thumbnails- as it looks and behaves completely differently when opened natively in Windows and when "called" from inside Affinity Photo.

Sorry, didn't catch that, I'm still waking up I guess after a couple of long nights of work 
Yes, I was wondering if the fact that DX Core actually sees three GPUs, while one of them being a Microsoft virtual device (which cannot be used as a GPU accelerator), could possibly be the cause of the issue. I was hoping to get some insight from the developers.

Sorry, didn't catch that, I'm still waking up I guess after a couple of long nights of work 
Yes, I was wondering if the fact that DX Core actually sees three GPUs, while one of them being a Microsoft virtual device (which cannot be used as a GPU accelerator), could possibly be the cause of the issue. I was hoping to get some insight from the developers.

I think that if everyone will just silently turn off the hardware acceleration and "abstain from moaning" it won't help developers to improve hardware acceleration and/or to know about problems with it.
There are known issues with OpenCL on certain AMD cards, there are some issues with Metal on macOS. In general, it is not that easy to maintain consistent GPU utilization and behavior across different platforms with plenty of graphic cards of all sorts. And I really appreciate the efforts Affinity developers put into improving this area in their products.
I believe, we need more topics like this. We shouldn't just accept the fact "oh, okay seems like it doesn't work on my powerful machine, i'll turn it off then, should be fine".
Without hardware acceleration performance is worse. No one can deny that. We shouldn't silently accept the performance loss we're seeing.
Software needs to get all the juices from your system and give you the performance and speed your hardware deserve and actually can provide.
While it may seem to solve your current issues and give you the ability to complete your work, in a much longer and global perspective it is a really harmful advice "just to turn the acceleration off". You have a good CPU and GPU and there's no reason for you to not being able to get all the benefits with hardware acceleration on your system.
Hopefully, Affinity will step up their game in terms of GPU acceleration. I have high hopes for the team and wishing them the very best.
P.S.: Also it may be useful to attach some crash reports here so someone from the team can actually see what's exactly happening with your system at the time application is crashing.

@Mark Ingram
I understand there's no news about the many crash reports posted previously (here, here, and here), so I guess I can't expect much in that territory.
That said, if it might be of any help, I tested 1.10.3.1188, and I can confirm the same crashes once again (DMP files, and logs attached).
As usual, the beta seems to be working fine with the acceleration off, though the latest official 1.9.2.1035 works also with the acceleration on.
While it's possible to use the newest releases with the acceleration off, the difference is quite significant in terms of performance.
You have provided a great software, and I still hope there's a way for the devs to figure this out. It's difficult to go back
For the record, the other software I use with no issues regarding GPU acceleration are:
Cinema 4D R21 with Redshift, Blender 3D 2.93.5, and 3.0 alpha, Davinci Resolve Studio, Fusion Studio, Quixel Mixer, Quadspinner Gaea, Diffractor.
Edit: I forgot to add that the latest official Affinity Designer, and Affinity Publisher work fine with the hardware acceleration on.
As for my system specs:
Computer: Alienware Area-51 R3 CPU: AMD Ryzen Threadripper 1950X (ThreadRipper, ZP-B1) 3400 MHz (34.00x100.0) @ 4116 MHz (41.25x99.8) Motherboard: Alienware 0XF4NJ BIOS: 1.2.0, 07/24/2020 Chipset: AMD X399 (Promontory) Memory: 32768 MBytes @ 1064 MHz, 15-15-15-36 - 16384 MB PC21300 DDR4 SDRAM - Corsair CMK32GX4M2A2666C16 - 16384 MB PC21300 DDR4 SDRAM - Corsair CMK32GX4M2A2666C16 Graphics: ASUS TURBO GTX 1080 Ti NVIDIA GeForce GTX 1080 Ti, 11264 MB GDDR5X SDRAM Graphics: DELL GeForce GTX 1080 Ti NVIDIA GeForce GTX 1080 Ti, 11264 MB GDDR5X SDRAM Drive: Samsung SSD 860 QVO 2TB, 1953.5 GB, Serial ATA 6Gb/s @ 6Gb/s Drive: KXG50ZNV512G NVMe TOSHIBA 512GB, 500.1 GB, NVMe Drive: HL-DT-ST DVD+-RW GS40N, DVD+R DL Sound: NVIDIA GP102 - High Definition Audio Controller Sound: AMD Zen - HD Audio Controller Sound: NVIDIA GP102 - High Definition Audio Controller Network: Qualcomm/Atheros E2500 PCI-E Gigabit Ethernet Controller Network: Killer Wireless-n/a/ac 1535 Wireless Network Adapter Network: Qualcomm/Atheros E2500 PCI-E Gigabit Ethernet Controller OS: Microsoft Windows 10 Professional (x64) Build 19043.1288 (21H1)  
 
reports.zip attachments.zip

@Mark Ingram
I understand there's no news about the many crash reports posted previously (here, here, and here), so I guess I can't expect much in that territory.
That said, if it might be of any help, I tested 1.10.3.1188, and I can confirm the same crashes once again (DMP files, and logs attached).
As usual, the beta seems to be working fine with the acceleration off, though the latest official 1.9.2.1035 works also with the acceleration on.
While it's possible to use the newest releases with the acceleration off, the difference is quite significant in terms of performance.
You have provided a great software, and I still hope there's a way for the devs to figure this out. It's difficult to go back
For the record, the other software I use with no issues regarding GPU acceleration are:
Cinema 4D R21 with Redshift, Blender 3D 2.93.5, and 3.0 alpha, Davinci Resolve Studio, Fusion Studio, Quixel Mixer, Quadspinner Gaea, Diffractor.
Edit: I forgot to add that the latest official Affinity Designer, and Affinity Publisher work fine with the hardware acceleration on.
As for my system specs:
Computer: Alienware Area-51 R3 CPU: AMD Ryzen Threadripper 1950X (ThreadRipper, ZP-B1) 3400 MHz (34.00x100.0) @ 4116 MHz (41.25x99.8) Motherboard: Alienware 0XF4NJ BIOS: 1.2.0, 07/24/2020 Chipset: AMD X399 (Promontory) Memory: 32768 MBytes @ 1064 MHz, 15-15-15-36 - 16384 MB PC21300 DDR4 SDRAM - Corsair CMK32GX4M2A2666C16 - 16384 MB PC21300 DDR4 SDRAM - Corsair CMK32GX4M2A2666C16 Graphics: ASUS TURBO GTX 1080 Ti NVIDIA GeForce GTX 1080 Ti, 11264 MB GDDR5X SDRAM Graphics: DELL GeForce GTX 1080 Ti NVIDIA GeForce GTX 1080 Ti, 11264 MB GDDR5X SDRAM Drive: Samsung SSD 860 QVO 2TB, 1953.5 GB, Serial ATA 6Gb/s @ 6Gb/s Drive: KXG50ZNV512G NVMe TOSHIBA 512GB, 500.1 GB, NVMe Drive: HL-DT-ST DVD+-RW GS40N, DVD+R DL Sound: NVIDIA GP102 - High Definition Audio Controller Sound: AMD Zen - HD Audio Controller Sound: NVIDIA GP102 - High Definition Audio Controller Network: Qualcomm/Atheros E2500 PCI-E Gigabit Ethernet Controller Network: Killer Wireless-n/a/ac 1535 Wireless Network Adapter Network: Qualcomm/Atheros E2500 PCI-E Gigabit Ethernet Controller OS: Microsoft Windows 10 Professional (x64) Build 19043.1288 (21H1)  
 
reports.zip attachments.zip

@Mark Ingram
I understand there's no news about the many crash reports posted previously (here, here, and here), so I guess I can't expect much in that territory.
That said, if it might be of any help, I tested 1.10.3.1188, and I can confirm the same crashes once again (DMP files, and logs attached).
As usual, the beta seems to be working fine with the acceleration off, though the latest official 1.9.2.1035 works also with the acceleration on.
While it's possible to use the newest releases with the acceleration off, the difference is quite significant in terms of performance.
You have provided a great software, and I still hope there's a way for the devs to figure this out. It's difficult to go back
For the record, the other software I use with no issues regarding GPU acceleration are:
Cinema 4D R21 with Redshift, Blender 3D 2.93.5, and 3.0 alpha, Davinci Resolve Studio, Fusion Studio, Quixel Mixer, Quadspinner Gaea, Diffractor.
Edit: I forgot to add that the latest official Affinity Designer, and Affinity Publisher work fine with the hardware acceleration on.
As for my system specs:
Computer: Alienware Area-51 R3 CPU: AMD Ryzen Threadripper 1950X (ThreadRipper, ZP-B1) 3400 MHz (34.00x100.0) @ 4116 MHz (41.25x99.8) Motherboard: Alienware 0XF4NJ BIOS: 1.2.0, 07/24/2020 Chipset: AMD X399 (Promontory) Memory: 32768 MBytes @ 1064 MHz, 15-15-15-36 - 16384 MB PC21300 DDR4 SDRAM - Corsair CMK32GX4M2A2666C16 - 16384 MB PC21300 DDR4 SDRAM - Corsair CMK32GX4M2A2666C16 Graphics: ASUS TURBO GTX 1080 Ti NVIDIA GeForce GTX 1080 Ti, 11264 MB GDDR5X SDRAM Graphics: DELL GeForce GTX 1080 Ti NVIDIA GeForce GTX 1080 Ti, 11264 MB GDDR5X SDRAM Drive: Samsung SSD 860 QVO 2TB, 1953.5 GB, Serial ATA 6Gb/s @ 6Gb/s Drive: KXG50ZNV512G NVMe TOSHIBA 512GB, 500.1 GB, NVMe Drive: HL-DT-ST DVD+-RW GS40N, DVD+R DL Sound: NVIDIA GP102 - High Definition Audio Controller Sound: AMD Zen - HD Audio Controller Sound: NVIDIA GP102 - High Definition Audio Controller Network: Qualcomm/Atheros E2500 PCI-E Gigabit Ethernet Controller Network: Killer Wireless-n/a/ac 1535 Wireless Network Adapter Network: Qualcomm/Atheros E2500 PCI-E Gigabit Ethernet Controller OS: Microsoft Windows 10 Professional (x64) Build 19043.1288 (21H1)  
 
reports.zip attachments.zip

@Mark Ingram
I understand there's no news about the many crash reports posted previously (here, here, and here), so I guess I can't expect much in that territory.
That said, if it might be of any help, I tested 1.10.3.1188, and I can confirm the same crashes once again (DMP files, and logs attached).
As usual, the beta seems to be working fine with the acceleration off, though the latest official 1.9.2.1035 works also with the acceleration on.
While it's possible to use the newest releases with the acceleration off, the difference is quite significant in terms of performance.
You have provided a great software, and I still hope there's a way for the devs to figure this out. It's difficult to go back
For the record, the other software I use with no issues regarding GPU acceleration are:
Cinema 4D R21 with Redshift, Blender 3D 2.93.5, and 3.0 alpha, Davinci Resolve Studio, Fusion Studio, Quixel Mixer, Quadspinner Gaea, Diffractor.
Edit: I forgot to add that the latest official Affinity Designer, and Affinity Publisher work fine with the hardware acceleration on.
As for my system specs:
Computer: Alienware Area-51 R3 CPU: AMD Ryzen Threadripper 1950X (ThreadRipper, ZP-B1) 3400 MHz (34.00x100.0) @ 4116 MHz (41.25x99.8) Motherboard: Alienware 0XF4NJ BIOS: 1.2.0, 07/24/2020 Chipset: AMD X399 (Promontory) Memory: 32768 MBytes @ 1064 MHz, 15-15-15-36 - 16384 MB PC21300 DDR4 SDRAM - Corsair CMK32GX4M2A2666C16 - 16384 MB PC21300 DDR4 SDRAM - Corsair CMK32GX4M2A2666C16 Graphics: ASUS TURBO GTX 1080 Ti NVIDIA GeForce GTX 1080 Ti, 11264 MB GDDR5X SDRAM Graphics: DELL GeForce GTX 1080 Ti NVIDIA GeForce GTX 1080 Ti, 11264 MB GDDR5X SDRAM Drive: Samsung SSD 860 QVO 2TB, 1953.5 GB, Serial ATA 6Gb/s @ 6Gb/s Drive: KXG50ZNV512G NVMe TOSHIBA 512GB, 500.1 GB, NVMe Drive: HL-DT-ST DVD+-RW GS40N, DVD+R DL Sound: NVIDIA GP102 - High Definition Audio Controller Sound: AMD Zen - HD Audio Controller Sound: NVIDIA GP102 - High Definition Audio Controller Network: Qualcomm/Atheros E2500 PCI-E Gigabit Ethernet Controller Network: Killer Wireless-n/a/ac 1535 Wireless Network Adapter Network: Qualcomm/Atheros E2500 PCI-E Gigabit Ethernet Controller OS: Microsoft Windows 10 Professional (x64) Build 19043.1288 (21H1)  
 
reports.zip attachments.zip

Not sure if the sudden crashes here and here are still being looked into, but just to confirm: I tested this latest beta, unfortunately the issue persists.
I still hope the devs will be able to figure this out at some point. For the time being, I stick to 1.9.2.1035 version, which is the latest release that works fine with the hardware acceleration on.

@Chris B
I'm not running the two 1080ti in SLI, the 3d render engines I use work better without SLI.
That said, I believe the crash report will look very similar to the others I posted in the other thread.
Anyway, I attached the latest in case it might be useful.
c894cb77-254c-4b8b-9010-2541c55d9592.dmp

Upon further testing, I think the reason why disabling one GPU works is that Affinity Photo at that point doesn't use GPU acceleration at all.
I tested it on heavier files, and it feels slower than 1.9.2 with hardware acceleration.
So, long story short, I'm reverting to 1.9.2 once again.
I wish Affinity had an option like in Blender 3D to enable/disable GPUs

Ah so 1.9.2 works but 1.10.1 does not... That's surprising. I'd expect neither to work if OpenCL was at fault if I'm being honest. 
Many people report changing drivers doesn't fix it so they use something like DDU to remove all trace of the driver but that seems to have made no difference for you. 
I'll try and get some more advice from Dev.