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

Boolean operations still unusable after all these years


Recommended Posts

After all these years, it's still impossible to get clean combined vectors using the "add" boolean. If I use vector strokes that overlap and then expand them and try to merge them with the "add" boolean, if it does not shut down the app, it leaves behind "dirty nodes" or it makes part of the design disappear. This happens on ipad and desktop, both with 1.10

I understand Affinity is all about keeping things editable, but at some point, we need the option to compress down and finalize a version for output. Designer is also missing a "unite" equivalent boolean operation. 

I have to export my expanded strokes from Affinity into Illustrator to use the "merge" and "unite" tools there. 

Link to comment
Share on other sites

  • 2 weeks later...

+1 I second this. Booleans are important part of my workflow.

 

On 8/19/2021 at 7:00 AM, PixelPest said:

Don´t have the issue you describe. Can you upload such a file?

 

Just create and overlap a few circles and then Divide them. You will get a whole bunch of layers/curves. Then select a certain area and try to Add them together. I will not work.

Link to comment
Share on other sites

I use this every now and then to do a reality check. No improvements so far:

divisioan_add_problem.jpg.90bebb8b09040867cfb017bae9a7f821.jpg

In Illustrator:

divisioan_add_problem_not.jpg.8f9db00a56e2d4ae2f772d494aa00e08.jpg

It does not have to be anything complex: I think this happens whenever segments are aligned rather than overlap each other. The problem is that the app cannot handle its own accuracy. I suppose this can be worked around by increasing the size of the objects, or at least cleaned by performing additional Boolean operations, but if it is a complex drawing there is really no possibility to check whether a specific Boolean operation causes artifacts somewhere else in the drawing.

 

division_add_problem.eps

Link to comment
Share on other sites

20 minutes ago, PixelPest said:

These "empty" nodes are easy detectable in the layers panel and deletable.

There were about 225 of them in this case, and they could be easily deleted. But often deleting the surplus nodes changes the slope of segments. I wonder if there has been recent development in this area, or if nodes generated by Boolean operations have always been easy to remove.

divisioan_add_problem_surplusnodes.jpg.b19bcd195611caf457839e6c27793045.jpg

 

Link to comment
Share on other sites

Hi all

Ajouter quelque chose qui ressemble à pathfiner/contour de AI serait déjà pas mal, et viendrait compléter diviser.

Adding something like AI pathfiner/contour would be good, and would complement divide.

Toujours pas !
Windows 10 Pro 21H2 - Intel Core i7-3630QM CPU @ 2.40GHz - 16 Gb Ram - GeForce GT 650M - Intel HD 4000
Affinity Photo | Affinity Designer | Affinity Publisher | 2

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.

Guest
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.

Loading...
×
×
  • 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.