Subclavius

Thank you @lepr and @Alfred  The document is indeed set to 300dpi
I shall put in a request to the suggestions forum.

Thank you @lepr and @Alfred  The document is indeed set to 300dpi
I shall put in a request to the suggestions forum.

Affinity internally uses pixel as its unit of measure. The maximum corner radius seems to be 1991.1 px, and that is equivalent to 168.6 mm when PPI is 300.

At 96 ppi, 168.6 mm is 638 px (i.e. 2 px less than 640 px). Maybe that means something, or not!

Use the Pie tool to draw the arc you want, set the hole radius to 100%. Now you have your "arc" even though it is a Pie. Just convert the Pie to a curve.

Hi @entropy
Are your graphics drivers up to date?  If Windows is crashing, this suggests to me a problem with the drivers rather than Affinity Photo.  The latest version according to the NVIDIA website is studio driver 516.94

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.

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.

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.

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.

Regardless ... Its got beautiful plumage!

Using Affinity Photo to create curves (pen mode) - when objects on the same layer are filled, the intersecting area is always empty (no fill).  This is equivalent to 'Alternate (even-odd)' mode in Affinity Designer.  It would be very, very useful for me to have the 'Winding (non-zero)' mode from Affinity Designer available to counter this problem.  I use the pen mode to trace objects - writing in particular, and where strokes intersect there is always a blank area which has to be later manually filled.  I would like to make a plea for this enhancement which on the face of it looks not too dificult to implement.

I haven't (yet) found a request for this one or any help on how to do it, so I would like to submit a request for this new feature.
Please would you add a menu under "Select same" for the same named (or coloured) objects only within the current artboard.  With multiple artboards of similar content it's a real nuisance to constantly have to rename objects just to that artboard (and the choice of colours is limited too) so that only objects on the particular artboard are selected.

I haven't (yet) found a request for this one or any help on how to do it, so I would like to submit a request for this new feature.
Please would you add a menu under "Select same" for the same named (or coloured) objects only within the current artboard.  With multiple artboards of similar content it's a real nuisance to constantly have to rename objects just to that artboard (and the choice of colours is limited too) so that only objects on the particular artboard are selected.

I haven't (yet) found a request for this one or any help on how to do it, so I would like to submit a request for this new feature.
Please would you add a menu under "Select same" for the same named (or coloured) objects only within the current artboard.  With multiple artboards of similar content it's a real nuisance to constantly have to rename objects just to that artboard (and the choice of colours is limited too) so that only objects on the particular artboard are selected.

Hello and welcome to the forums.
Are you using a graphics tablet e.g. Wacom or another make?  Have you tried the same operations using the mouse?  Does the application crash each time you use the "pentool" or just with particular operations?  Some more details here would be helpful.
Have you checked whether the graphics drivers (from Dell or Nvidia) are up to date?

Thanks for sharing the pics. Your Fuji files stitch together fine on my pc, both with and without HA (see pic).
Things to consider now:
also on the Performance panel you will see a memory limit - try increasing this as high as it will allow, as a test.  On my pc I have it set to the maximum check out this post about other software which can conflict with APhoto other things might be the graphics drivers, or just possibly the hardware.  Are you able to give any details about hardware/graphics drivers installed in your system?

Thanks for sharing the pics. Your Fuji files stitch together fine on my pc, both with and without HA (see pic).
Things to consider now:
also on the Performance panel you will see a memory limit - try increasing this as high as it will allow, as a test.  On my pc I have it set to the maximum check out this post about other software which can conflict with APhoto other things might be the graphics drivers, or just possibly the hardware.  Are you able to give any details about hardware/graphics drivers installed in your system?

I was able to open the file successfully using Microsoft Paint and  then do a 'Save As' to a tiff file.  This new tiff file opens successfully in APhoto but the size is significantly larger (18.4MB) than the original (2.38MB) so clearly some compression has been applied to the original scan.

@Gnobelix, just a thought: I note that the live perspective filter is buried in between other layers.  Does it make a difference if, for example it is on top? Is it worth deleting some of the other layers and see whether you still get the crash?  That might point the finger at an interaction between layers rather than the filter itself.

Apps I've used previous assign CTRL+TAB for tabs in table cells
Interestingly...
You can assign CTRL+TAB to Text > Insert > Spaces and tabs > Tabs in publisher but you get a "warning" that it is already assigned to Next Window
But go ahead and click OK/Close and then if used in a table it gives you a tab as required and if used outside a table you still get Next Window
So, a nice doubling up of an existing shortcut and no need to assign a (precious) unused one...
...and logically CTRL+TAB is probably easier to remember than ALT+T if you don't use tables that often
 
 

@StuartRc, @Brian_J, @David in Яuislip,
Thank you all for your suggestions. I wanted to do the thing just as a (quickish) one-off exercise but clearly I can't without learning a lot more about Affinity Pub tables first. I  feel it's a pity that the ability to keep simple things simple seems to have been lost.

Try selecting the cells except the last column, then choose All Vertical, select colour and line width
I have to say that formatting borders drives me nuts

As StuartRc mentioned, the Table studio has what you need. You can also create a global color and apply it to the table borders... so if you decide to change the color you can edit the global color instead of having to go back into the table settings.
Table Borders.m4v