Catshill Posted May 20, 2022 Share Posted May 20, 2022 This is 100% reproducible for me and results in a crash. Load the attached > Select all (CTRL A) > From layers menu choose Expand Stroke Expand Stroke Crash.afdesign Quote Link to comment Share on other sites More sharing options...
NotMyFault Posted May 20, 2022 Share Posted May 20, 2022 Confirm on Mac M1. Probably related to multiple strokes. If you deactivate one of the strokes, no crash. Even more interesting: it then expands the curve 2 times (for every stroke, even the deactivate one) Catshill 1 Quote Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080 LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 iPad Air Gen 5 (2022) A2589 Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps. Link to comment Share on other sites More sharing options...
Old Bruce Posted May 21, 2022 Share Posted May 21, 2022 22 hours ago, NotMyFault said: Even more interesting: it then expands the curve 2 times (for every stroke, even the deactivate one) It is after all effectively 2 strokes, the black and the white from the appearance panel. Quote Mac Pro (Late 2013) Mac OS 12.7.4 Affinity Designer 2.4.1 | Affinity Photo 2.4.1 | Affinity Publisher 2.4.1 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
Staff EmT Posted May 23, 2022 Staff Share Posted May 23, 2022 Hi @Catshill This is something we are aware of and it has been passed over to our developers for further investigation. If you follow the 'News and Information' thread on our Forum, it will advise you when an update is available. https://forum.affinity.serif.com/index.php?/forum/4-news-and-information/ Quote How to format a bug report | List of V2 FAQ's | Affinity Photo (V2) Tutorials | Affinity Designer (V2) Tutorials | Affinity Publisher (V2) Tutorials Link to comment Share on other sites More sharing options...
Catshill Posted November 21, 2022 Author Share Posted November 21, 2022 I've now tried this with V2. The good news is that there is no crash, the bad news is that the result is not what is intended Expand Stroke Crash.afdesign Quote Link to comment Share on other sites More sharing options...
Staff EmT Posted November 22, 2022 Staff Share Posted November 22, 2022 @Catshill Is the first X supposed to be set to blend mode subtract? If you set that back to Normal then it does show correctly. NotMyFault 1 Quote How to format a bug report | List of V2 FAQ's | Affinity Photo (V2) Tutorials | Affinity Designer (V2) Tutorials | Affinity Publisher (V2) Tutorials Link to comment Share on other sites More sharing options...
Catshill Posted November 23, 2022 Author Share Posted November 23, 2022 Setting both lines to Blend mode Normal results in Not what I wanted either. I need to revisit the two methods of drawing roads and to see if it is possible to connect roads of different widths as I do not believe it is. see Quote Link to comment Share on other sites More sharing options...
Staff EmT Posted November 23, 2022 Staff Share Posted November 23, 2022 @Catshill You could try setting blend mode to Add or select both curves and go Geometry > Add to merge them into one curve, both would remove the central line that overlaps. Quote How to format a bug report | List of V2 FAQ's | Affinity Photo (V2) Tutorials | Affinity Designer (V2) Tutorials | Affinity Publisher (V2) Tutorials Link to comment Share on other sites More sharing options...
Catshill Posted November 24, 2022 Author Share Posted November 24, 2022 Perfect - many thanks @EmT EmT 1 Quote Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted August 23, 2023 Staff Share Posted August 23, 2023 The issue "Crash when expanding more than one 'multiple stroke' object" (REF: AFD-3892) has been fixed by the developers in internal build "2.2.0.1971". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.