Jump to content


  • Posts

  • Joined

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Los Angeles

Recent Profile Visitors

636 profile views
  1. Only it's not the 90s anymore. The development happens much faster nowadays. With this, I'm not implying Serif should or should not update their products more often, only objecting that a comparison to thirty years ago is not exactly on point.
  2. Oh, totally, for me too. Even the most simple things would make it crash. Now with this workaround, at least I can open the files, and do some basic CC. Definitely an improvement, thanks for sharing it!
  3. Thanks @PeteMacca It kind of worked for me. It's definitely more stable than before, until I use live filters which make Photo close unexpectedly. I don't know if I should keep posting logs, and dump files though, it seems there isn't much response from the devs.
  4. 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.
  5. @Mark Ingram Since I'm stuck with, as newer releases don't work with hardware acceleration, is it possible that the reason why newer releases crash is due to the adapters recognized by the DXCORE? I tried the latest, and after I turned on hardware acceleration, it crashed again. In the log I noticed this: [DXCore] Found 3 adapters Even though I actually have only two physical GPU installed (two 1080ti). So, it seems Affinity Photo is also using Microsoft Basic Render Driver. Log, and dump file attached. Thanks attachment_Log.txt b5d256f4-9d01-4e0e-9561-151d14d76285.dmp
  6. Yes, in both cases with acceleration off, the performance degrades. Luckily for me, and apparently for other people who are experiencing this issue with the latest versions of Affinity Photo, 1.9.2 works fine with the acceleration on. Not sure what changed in the latest releases with the GPU acceleration.
  7. I see the suggestion to turn the acceleration off rather often on this forum, and I appreciate the fact that people here help. I only wanted to add that, in regard to the acceleration crash issues, it would be fair to add that turning acceleration off doesn't actually fix the issue, it's just a workaround. In fact, the performance is affected (quite badly, in my experience). Some users could read it as a solution. I too, as @Joergen Geerds am back working with I haven't seen any news regarding the acceleration in the latest betas, though I still hope the issue is being investigated. I understand this seems to be particularly tricky, so I still hope at some point the solution will be found.
  8. @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, 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 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
  9. 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 version, which is the latest release that works fine with the hardware acceleration on.
  10. @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
  11. 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
  12. After further testing, I can confirm that the crashes happen when two 1080ti are both active. After I plugged back in the second GPU, I noticed that when I tried to open two documents, Affinity Photo was again closing with no warning. Next, I simply disabled one GPU from the device manager And tried to open the two documents, which now I can open without issues.
  13. Hi there, I'm in the middle of doing some hardware change to my PC, and thus I momentarily removed one of my two 1080ti. So, while at the moment working with one 1080ti only, I decided to give Affinity Photo 1.10.1 another try. To my surprise, it hasn't crashed yet. I have the feeling that if I plug back my second 1080ti things my start breaking again. Not sure whether this helps the devs in any way, but I thought to report this here just in case. Best, Piero
  14. @Chris B the thing is, the latest Designer and Publisher work fine here. It seems there's something going on with Photo specifically. I also tried three or four different drivers with no luck. Photo 1.9.2 works fine with hardware acceleration, which is why I went back to using that version. I haven't checked the Designer or Publisher bugs section, but it seems several other users are reporting similar issues with Affinity Photo, that is why I assumed the developers would be looking into it. But if that's not the case, I think I'm stuck with 1.9.2.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.