SuperUser Posted March 9, 2020 Share Posted March 9, 2020 It's not always broken, sometimes it behaves unexpectedly. Here's what happens when I tried to expand stroke on this particular icon. Attached the file as well. I don't get why one side becomes all wack and the other side is perfectly fine. The curves seem to be identical. expand-stroke-bugged.afdesign Link to comment Share on other sites More sharing options...
Graphite Addict Posted March 9, 2020 Share Posted March 9, 2020 I don't think that particular file has a bug exactly, although the behaviour is odd and inconsistent. You have a pair of overlapping nodes on the stroke at that location (before expanding) and also some overlapping nodes on the mirrored side which expand just fine. I just tested it myself and the overlapping nodes on the right, when expanded, cause the mistake. Steps to fix when this happens. 1. Note the location of error on the EXPANDED stroke. 2. UNDO the Expand. 3. Find the node on the STROKE at the location weird error. 4. With the NODE TOOL click that node (do not marquee select) and move it to reveal the duplicate node. 5. BREAK CURVE on one of the duplicate nodes, delete any spare nodes and then rejoin to close. SuperUser and Sean P 1 1 Link to comment Share on other sites More sharing options...
Staff Sean P Posted March 11, 2020 Staff Share Posted March 11, 2020 Graphite Addict is correct, however I will get it passed on to see if improvements can be made for situations like these. Link to comment Share on other sites More sharing options...
Aammppaa Posted March 11, 2020 Share Posted March 11, 2020 @Sean P I am not convinced that duplicated nodes is the sole cause of this. See… Peg11 1 Win10 Home x64 | AMD Ryzen 7 2700X @ 3.7GHz | 48 GB RAM | 1TB SSD | nVidia GTX 1660 | Wacom Intuos Pro Link to comment Share on other sites More sharing options...
Staff Sean P Posted March 11, 2020 Staff Share Posted March 11, 2020 2 hours ago, Aammppaa said: @Sean P I am not convinced that duplicated nodes is the sole cause of this. See… Thanks for that - I'll look into that thread. As an update I've changed it to a bug, as it is actually a regression over 1.7.3 behaviour! SuperUser 1 Link to comment Share on other sites More sharing options...
Recommended Posts