Expand Stroke it's worst ?

[Pedro Eira]

I tried expand stroke in different situations and it seems worst than before. Very sad :(
See example here : https://imgur.com/a/iEanWPO

[StraightFromSpace]

Same thing here... ouch this is bad.

[MEB]

Hi Pedro Eira,
Welcome to Affinity Forums
The Expand Stroke command is much more accurate than before unfortunately there's a few specific cases where it fails. Can you please attach the file original afdesign file shown in your screenshot for us to check/test against new code revisions? Thank you. If you stumble upon more cases please let us know/provide a sample file so we can add them to out log/report.

[Enes]

the expanded stroke changes even when I change the position of the element.

I hope the file can help.

stroke bug.afdesign

[Pedro Eira]

here you have the file. 
I've been testing all afternoon and It happens the same with other simple cases. Overall it's really really bad.

expand stroke bug 1.afdesign

[Dazmondo77]

That's pretty bad

[Oval]

15 hours ago, Enes said:

the expanded stroke changes even when I change the position of the element

since ever

[retrograde]

15 hours ago, Pedro Eira said:

here you have the file. 
I've been testing all afternoon and It happens the same with other simple cases. Overall it's really really bad.

expand stroke bug 1.afdesign 16.12 kB · 6 downloads

Weird. I downloaded the file and got the same result, but when I bumped up the stroke weight to 12 points it expanded fine...

[Dazmondo77]

1 hour ago, retrograde said:

Weird. I downloaded the file and got the same result, but when I bumped up the stroke weight to 12 points it expanded fine...

Not for me, I went unto 30pt and still get a mess - very similar bug to boolean operations and compounds with 1.8 ------ I was expecting improvements?!?!?!

[Brian D]

18 hours ago, MEB said:

The Expand Stroke command is much more accurate than before unfortunately there's a few specific cases where it fails.

I disagree, it's far worse than before in every scenario for me. I tried expanding a simple stroke around the Honda logo for a customer and it turned into abstract art. Expanding strokes around any text seems to fail for me, and combining the results with the original shape is an absolute disaster.

[MEB]

Hi Eines, Pedro Eira,
Thanks for providing the files. I've added them to our log.

Hi Brian,
I understand your frustration. What i meant is that the shapes it generates now (in the cases where it works) are more accurate than they were before. Unfortunately there was also a few regressions (due to the rewritten code): some cap options, text objects, a couple shape tools are failing to expand/resolve properly. These issues are being looked at as we speak. My apologies for the inconvenience this is causing you. We are doing our best to fix them as soon as we can. Thanks for understanding.

[rovedajr]

3 minutes ago, MEB said:

These issues are being looked at as we speak. My apologies for the inconvenience this is causing you. We are doing our best to fix them as soon as we can. Thanks for understanding.

Is there any way to "downgrade" temporarily to 1.7 while these issues are solved?

[Brian D]

I get that it's going to take a little time to fix whatever has gone wrong, that's totally understandable.

So my next question, is there any way to roll back the Mac App Store version to the previous (1.7) build? Simple jobs that were taking 10 minutes are now taking 45 mins to an hours of playing around until I get somewhat satisfactory results, it's very hard to work this way.

[MEB]

Hi rovedajr, Brian D,

For Affinity Store users only (these versions require a product key for activation) please check the links below:
- Affinity Photo
- Affinity Designer
- Affinity Publisher

For Mac App Store users there's no way to revert to a previous version unless you have made a backup before.

[Pedro Eira]

Thanks for the quick responses MEB.
I hope this will be fixed soon.

[Brian D]

12 minutes ago, MEB said:

For Mac App Store users there's no way to revert to a previous version unless you have made a backup before.

Well balls... that'll teach me for giving Apple a 30% cut.

[kaiwienen]

here are another example 

[MEB]

Hi kaiwienen,
Thank you for your feedback. Whenever possible please attach the original afdesign file. Thank you.

[rovedajr]

1 hour ago, MEB said:

Hi kaiwienen,
Thank you for your feedback. Whenever possible please attach the original afdesign file. Thank you.

Well, MEB, I took the liberty to attach a file too. It shows the error quite clearly. I hope it helps.

alcazar.afdesign

[camloken]

I have noticed the 'Add' feature is also broken and does the same thing when combining shapes. The bug is probably related. I have attached a file. Try expanding only the topmost stroke, then combine it to the top shape. You will see a very similar problem where it fills the right area of the combined shape. My guess is in both cases, where the intersection happens, you are forgetting to create a node (or point).

rig-icon.afdesign

[Paul Mudditt]

On 2/27/2020 at 5:26 PM, Pedro Eira said:

here you have the file. 
I've been testing all afternoon and It happens the same with other simple cases. Overall it's really really bad.

expand stroke bug 1.afdesign 16.12 kB · 11 downloads

This appears fixed in AP 1.8.2.172 beta.

[Pedro Eira]

That's Great news. It seems that you are using the iPad version, I hope it's fixed too on the mac pro. I will test it when I get home.

[Pedro Eira]

I don't have that update on my Mac. And I'm really struggling because beside the stroke problem, the Affinity doesn't save the files as before. So I'm loosing a lot of work because of that. Is horrible.

[stldoug]

Here's another example of a failing expand stroke.

MacOS 10.15.3
Affinity Designer 1.8.1

Edit: Seems to be fixed in Affinity Designer Beta 1.8.2.4

 

broken-document-icon.afdesign

Edited March 14, 2020 by stldoug
Tested in latest Beta (1.8.2.4)