Jump to content
You must now use your email address to sign in [click for more info] ×

Affinity Designer [] - Bugs of contour tool and expand stroke with visual artefacts

Recommended Posts

I have already noticed this solution, but it was not available "like this" until now. 
It seems to be related to the "refresh rate" of the editing window, or it only refreshes when you zoom in and out or switch between documents. 
In addition, the visual artefacts only occur with artboards. No artefacts occur in the normal document, but the bugs of contour tool and expand stroke get worse.




Link to comment
Share on other sites


Now, I´m just trying to reproduce the glitch in a new document, but it doesn´t happen exactly in this moment. Nevertheless, I have to say it doesn´t occur only in artboards, because it has happened to me in normal documents (without artboards) before.


Link to comment
Share on other sites

  • Staff

Hi ChristAlix,

Thanks for your files. I can reproduce that here and I think its happening due to the small artboard size/document size. Removing the artboard does cause the issues to go away, so it could likely be why you've not encountered it before and also why spsorrel isn't able to reproduce it in a new document. Though with that said I can't reproduce on new document with similar size and creation method!

The Expand Stroke, looks to be caused by two nodes overlapping which is a separate issue we do have logged.

I'll get these both passed over to development as vector commands shouldn't really be affected by the document size.

Link to comment
Share on other sites

Experiencing similar artifact issues using the contour tool in the latest release of AD ( I didn't want to create a duplicate thread, so posting here. This happens with OpenCL disabled as well as enabled. Please see the attached video.

Hardware specs: AMD Ryzen 4800h with RTX 2060 (laptop) running Windows 10 20H2. All drivers updated to the latest (Nvidia studio).

PS: I'm also seeing high CPU usage with this release (sudden spikes up to 90-100%), which wasn't the case with the 1.8.x versions. This pushes the CPU temps dangerously close to the 100 degree Celsius mark. The GPU usage remains very low, however, barely exceeding 50% in a stressful document. I know vector programs are CPU-heavy but wasn't the 1.9 version promising full HW acceleration support with the new Nvidia drivers?

Link to comment
Share on other sites

  • 4 weeks later...

It this the new "Expand Strokes Still Sucks" thread? :)

(Or is it this one... or this one...?)

Either way, here's my result in 1.9...



However, pasting it into a new document makes the bug go away, and these are files for a client so I can't share the entire thing.



EDIT: Wow, changed the stroke from round to mitre and the result is actually THE SAME... it expands exactly the same as if it has a round join!!!

Link to comment
Share on other sites

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.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.