Strokes acting weird when increasing beyond size of shape/holes

[Peter vw]

Haven't found an existing bug report about this. Sorry if this is a repeat...

When you have a shape and give it a stroke, when this gets larger than a certain point, it acts weird.

Here, the strokes are blue. Easy to reproduce. Just make a letter, give it a stroke, and drag the size up until you see it separate from the object.

 

[HCl]

.

[Peter vw]

Is it still an open issue?

[HCl]

.

[Peter vw]

Ah, that leaves me filled with hope! Then they are surely about to fix it right now! 😉

[HCl]

.

[MEB]

Hi @Peter van Westen,
Thank you for your feedback. I understand these are unexpected results, but in typical daily use, you rarely push things that far. These are edge cases where other apps also struggle to deliver accurate results. Below is a comparison of the 'e' following the steps you suggested in Affinity (in red) and in two other popular vector apps. The fact that the app allows you to push it to such extremes doesn’t necessarily mean it doesn’t "work". Similarly, in photo editing apps, there are controls and adjustments that can easily ruin an image if pushed to the limit.

[Peter vw]

The extremes are just to easily see the weird results. It also happens in smaller values.
See here where I just have a stroke of 2pt on a certain font:

[Peter vw]

Quote

The fact that the app allows you to push it to such extremes doesn’t necessarily mean it doesn’t "work"

Personally, I think if an app gives you the ability to push it beyond a point that things fall apart, then yes, that is a bug and it doesn't "work".
It should either provide a stable and predictable result, or not at all.

But again, this issue doesn't just affect the extremes. Strokes seem to act weird in other cases too.

[NotMyFault]

On of the older reports 

 

[MEB]

Hi Peter,
Can you post a screenshot of the same object with the zoom at 100% (1:1 scale)? The screenshot above is out of scale. It's likely small text with a blue stroke. The hole of the letter "e" becomes so small the app is probably struggling to resolve the rendering of the internal stroke properly (that's what I meant by extreme - edge cases -, not necessarily very high values in some controls only). Typically scaling up the whole object (keeping its proportions) should resolve the stroke issue a bit better as the size increases (I'm aware this is not a solution).

Is the text legible and functional at its intended 1:1 scale? If so, this issue might warrant logging. If it’s more of a demonstration of the tool’s limitations in a hypothetical scenario that doesn’t reflect typical real world use, then I don't see the point - the issue is already known by the dev team anyway.
Thank you for your feedback.

[Peter vw]

The white little thing inside the hole is not visible when zoomed out. But it is there in the a png export (for instance).
So the issue is not with the visual rendering but with the actual stroke shape.

test stroke.afdesign

[kenmcd]

1 hour ago, Peter van Westen said:

The extremes are just to easily see the weird results. It also happens in smaller values.
See here where I just have a stroke of 2pt on a certain font:

What font is that?

Some fonts have messy outlines which can affect the stroke. Cleaning-up the outlines can help.

[Peter vw]

Has nothing to do with the font.
See here a file with just a pretty simple shape. No fonts. Just paths.

test stroke.afdesign

[Peter vw]

Shape is about 20mm large. The stroke is 6pt. Nothing extreme.
Scaling it up or down has no different results.
So no, the issue is not about extremes. It is not about fonts. It is not about pushing the app beyond normal.

But: why am I wasting time explaining this? If the issue has been known for 10 years, there is no logic in expecting me showing the issue to have any value.