phoenixart

Hi, Today I installed the new beta, and I think I've found a bug. When I resize the canvas, the chain icon in between the width, and height field is not present. The canvas can only be resized proportionally with the ratio locked.

@carl123 I'm on Windows 11 @Hangman I think what happened it's me getting tricked by habits. Basically, nothing has changed between the beta version, and the official one. For some reason, I forgot that, at least on Windows, double-click rolls-up the panel, but then to open the panel back again, double-click doesn't exactly work as expected. In fact, the only way to open the panel again is to click on the tab. For instance, in the case below, clicking on the tab Character (or Paragraph) will roll down the panel. So, double-clicking on the empty area of the panel, only works to roll it up. It's actually a bit counterintuitive. One would think that it would work both ways. So, no bug to report here.

If I double-click on a floating panel to roll it up, double-clicking on it to roll down the panel seems to have no effect.

Thanks @NathanC Exactly, I plugged an external hard drive while Photo 2 was running. I indeed checked the task manager before opening the event log, and I noticed a spike in the GPU usage, both of them (two 3080ti). It's still hard to tell what caused the slow-down as I also had a few other apps open at the same time, but in the event log all I could find is the error I posted related to Photo 2. I'll do more test, and keep an eye on it.

Hi there, I've noticed a strange error in the events log: Faulting application name: Photo.exe, version: 2.0.4.1701, time stamp: 0x63ceb04f Faulting module name: libaffinity.dll, version: 0.0.0.0, time stamp: 0x63ceaabc Exception code: 0xc0000005 Fault offset: 0x00000000001ae8ca Faulting process id: 0x0x3B60 Faulting application start time: 0x0x1D93CAA1AD42D45 Faulting application path: C:\Program Files\WindowsApps\SerifEuropeLtd.AffinityPhoto2_2.0.4.1701_x64__3cqzy0nppv2rt\App\Photo.exe Faulting module path: C:\Program Files\WindowsApps\SerifEuropeLtd.AffinityPhoto2_2.0.4.1701_x64__3cqzy0nppv2rt\App\libaffinity.dll Report Id: acb052f5-3b20-4bb9-bb9f-a4c55c3faf17 Faulting package full name: SerifEuropeLtd.AffinityPhoto2_2.0.4.1701_x64__3cqzy0nppv2rt Faulting package-relative application ID: SerifEuropeLtd.AffinityPhoto2 I looked at the events log because all of a sudden Windows 11 slowed down considerably. It happened as soon as I plugged in an external hard drive, which never caused any issue. I was wondering if there might be some relation between Photo, and external hard drives which could trigger this unexpected behavior.

Thanks @carl123 That did it.

I saved a macro, but when I start a new session, the macro panel is empty: It looks like a bug, though I'm not sure if I'm missing something in the workflow.

In Affinity Photo 1(x) I used to Ctrl + Click on the alpha channel when I wanted to get the selection. In V2, that is not working anymore. Has that feature been removed?

I haven't read all the posts in this thread, but I just wanted to mention that in other software, there are actually issues when using AMD for graphic applications. I posted this on the 3D Coat forum, where it were discussed potential issues related to the use of AMD CPUs (and here too).

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

Thanks @walt.farrell I think I haven't explained myself too well, sorry for the confusion. What I wanted to say it's simply this: in the YT video you'll notice there's an Output item in the toolbar which is greyed out, and it appears after the raw has been imported, that is, the second time when James accesses develop persona. I'm doing the same step: I'm importing a RAW file, in the Output I pick RAW Layer, and I'm ready to add new layers to my document. Now, when I open develop persona, I don't have the Output on the toolbar. As I said, it's a minor UI thing, as the option can't be changed at that point. But in James' demo, the Output is there, which is what confused me at first. P.S. and to be blear, I'm using Serif Lab, which is actually the only option available on Windows.

Regarding the screenshot, I'm referring to this part of the YT video, which still shows the Output, though is greyed out, whereas on my end it's not showing up. It's just a minor UI difference which doesn't seem to have any practical effect, but at first the discrepancies with the YT video confused me. Maybe it's a difference between the Mac and PC version.

Correct, but on Serif's official tutorial it looks different, though I understand it's just a UI thing as the option at that point is disabled, but that throw me off for a moment. That said, I thought the non-destructive raw development would apply to anything, like with Adobe camera raw, which is very handy. Instead, in Affinity Photo, it only applies to an actual raw file the first time it's opened. Quite a missed opportunity there, hopefully it will be extended in the future.

How do I activate that option? I don't see the Output drop-down menu:

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.

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!

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.

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.

@nezumi Not sure to understand what you mean.

@Mark Ingram Since I'm stuck with 1.9.2.1035, 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 1.10.5.1282, 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

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.

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 1.9.2.1035. 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.

@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