Wagner Tamborin Posted September 29, 2024 Posted September 29, 2024 The stroke width tool is completely broken and impossible to use when I turn the lines into vectors (expand stroke). (Beta version 2.5.5.2636) The result it generates most of the time is extremely broken, which completely breaks the workflow (because I have to fix the nodes manually or create more width nodes at random points before expand, and hope it works). It adds curves that don't exist, angles that don't exist, splits pieces of the vector, creates gaps in the corners, and more. Please treat this as a priority, it is not possible that you have officially launched the tool with this kind of behavior. (I'm using Beta, but this happens in the launched 2.5.5 version too) Working with vectors means working with precision, and that's the complete opposite 😓 Gravação de Tela 2024-09-29 192827.mp4 bbrother, Krustysimplex and thomaso 2 1 Quote
Ron P. Posted September 30, 2024 Posted September 30, 2024 11 hours ago, Wagner Tamborin said: (I'm using Beta, but this happens in the launched 2.5.5 version too) They are the same version, there is no difference. Quote Affinity Photo 2.6..; Affinity Designer 2.6..; Affinity Publisher 2.6..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win11 Home Version:24H2, Build: 26100.1742: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD; Wacom Intuos 3 PTZ-431W
Meliora spero Posted October 1, 2024 Posted October 1, 2024 You're absolutely right @Wagner Tamborin. If we need to linguistically explain to newcomers and others what the issue is, it's unfortunately not that it worked and then broke by mistake. It has always been poorly implemented; the algorithms are no better than what you're seeing. Memories of previous releases are concerning. When a bad feature is implemented, Serif tends to shift focus to adding new half-baked features to Affinity and rarely addresses the underlying problems. You can only hope that Canva's takeover will bring about a regime change regarding respect for customers, service, and quality perception, by refactoring old issues and hiring new developers with real competencies in vector graphics on par with other programs. You'll have to do this, Canva, if you dream of gaining further market share ... and you do, don't you? Wagner Tamborin, bbrother, thomaso and 3 others 6 Quote Serif, did you foolishly fill the usability specialist role you advertised internally? If so, be transparent with your customers. Continuing without proper UX expertise both insults and affects your entire customer base.
bbrother Posted October 2, 2024 Posted October 2, 2024 The results this tool gives, especially when combined with expand stroke, are simply a misunderstanding. As said the stroke width tool or rather pressure profile algorithm as this is what the width tool is build on top has a bad algorithm, but its also worth mention that expand stroke has its own long-standing problems that trying to adres in 2.5 resulted in bad regressions. In my opinion, giving customers such poorly designed tool is a mockery and shouldn't happen if they consider themselves a serious company period. I sign with both hands under what the OP and my predecessor wrote. Wagner Tamborin, IthinkthereforeIam, Krustysimplex and 2 others 5 Quote
thomaso Posted October 5, 2024 Posted October 5, 2024 On 9/30/2024 at 12:39 AM, Wagner Tamborin said: It adds curves that don't exist, angles that don't exist, splits pieces of the vector, creates gaps in the corners, and more. This reminds me of the – possibly related – "Smooth Curve" function, which seems to refuse to produce a really usable result for most or perhaps all required situations. Although the issues have been known for years (decades?), testing, confirmation, and reminders by moderators to the company and/or development team still seem to be necessary. Meliora spero 1 Quote • MacBookPro Retina 15" | macOS 10.14.6 | Eizo 27" | Affinity V1 • iPad 10.Gen. | iOS 18.5. | Affinity V2.6
Staff Callum Posted October 8, 2024 Staff Posted October 8, 2024 Hi @Wagner Tamborin Please could you provide a copy of the file shown in your attached recording so I can pass this on to our developers to be investigated further? If you would rather not provide the entire file you should be able to copy the problem curve into a new file and then attach a copy of the new file to this thread. Thanks C Quote Please tag me using @ in your reply so I can be sure to respond ASAP.
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.