What's limiting the radius of the corner tool?

[Serioja]

I'm trying to use the corner tool to round two identical corners of the same shape. When I drag the point that represents the center of the curve to increase the radius, one stops while the other one allows me to use a higher value. See attached video. I want both corners to have the same radius value. Anyone knows what's causing this?

[Hangman]

Hi @Serioja,

Certainly nothing obvious but I can replicate the issue.

Selecting the right node when applying the corner tool results in both increasing with the same radii though there is then a maximum radius of 56.8198 mm.

In v1 this is working as expected so this is clearly a bug.

Corner Tool V1 Behaviour

 

[GarryP]

I’ve attached a video showing an example of how to replicate this in V2 on Windows.

The first time I tried to replicate it the effect didn’t happen until I had moved the nodes which I was later adding the corners to, but this didn’t happen with some later attempts at replication.

Sometimes, after moving the whole layer, the problem goes away.

I’m wondering if the X/Y values of the nodes has some input into the problem.

[Hangman]

Hi @GarryP,

In v2, this happens regardless of whether the nodes are pixel aligned or not so I'm not sure this is necessarily the cause as the same doesn't happen in v1 regrdless of the node alignment and as mentioned, selecting the right node and applying the corner tool gives you a different result in as much as there is a restriction on the maximum radii of the corner which there shouldn't be.

The corner radii should be tangential to where the selected node intersects the adjacent node which it isn't for either corner in v2 but is in v1, so neither of the corner radii are actually correct in v2.

Even selecting the nodes individually the corner radii are incorrect for both nodes...

[Aammppaa]

First reported soon after v2 release... 

 

[GarryP]

3 hours ago, Hangman said:

In v2, this happens regardless of whether the nodes are pixel aligned or not so I'm not sure this is necessarily the cause

I didn’t think pixel alignment would be a factor but I wondered, because my experiments showed that the same curve would sometimes exhibit different cornering results after being moved, whether the actual numerical values could make a difference somehow.

Such as, perhaps the X/Y value was somehow being mixed up with something else in the routine which determined the maximum radius, or something like that; it’s easily done – just accidentally type the wrong variable name.

(I only used the grid to show that the nodes were at the same angle but reversed.)

Anyway, since this has already been reported elsewhere we can just wait and see.

[Dan C]

Hi @Serioja,

Thanks for your report - and thanks for the further testing by other members above

I can confirm that I have been able to replicate this here using a similar setup as shown in GarryP's recording, without pixel alignment enabled.

Interestingly in this example, if I use the right hand node with the corner tool, both radii stop at the same point. If I use the left hand node, the radius continues much further than the left.

I believe this is similar, but not quite the same issue that was reported in the above thread - so I will be logging this with our development team now separately and 'linking' the issues internally.

I hope this helps!

[mimolette]

I'd just like to add that this issue still havent been resolved as of AD 2.2.1 :
Radius get stuck somewhere along the road, before reaching any point or edge. Files that worked in AD 1.x open with smaller radis..

(Thank you for otherwise very appreciable software)

 

[Dan C]

Welcome to the Affinity Forums @mimolette & thanks for the update.

Unfortunately this issue is still open with our development team at this time, I'll be sure to 'bump' this with your report to bring it to their attention once again.

I hope this helps

[udaanjargal]

I would also like to add this to the thread: 

Affinity Designer 2.5.4

MacOS Sonoma 14.5

 

[Dan C]

Thanks for your report & screen recorded provided @udaanjargal!

I can see this issue is still open with our development team, our apologies. I'll be sure to 'bump' this with them once again now