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

Search the Community

Showing results for tags 'boolean operation'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.3 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



Member Title

Found 12 results

  1. Hello. I ensured to search this issue as much as I could so that I wouldn't create a duplicate. Since the last time this problem was reported in the Pre 1.10 subforum and we are in 1.10.5 now, I felt this was the right place. Windows 10 Version As the title suggests, this is a problem with Affinity Designer Boolean Operations, primarily the Divide operation and I've found something that I feel wasn't touched on in the previous reporting. Consider image below, divide works as you would expect. Works perfectly, with each circle only overlapping each other once. Now consider what happens when the left and right circle is already overlapped, and the top circle gets overlapped IN the overlap of the left and right (confusing ish), I've used a red arrow to show where: You can see in the layer panel that the line in between the overlap that already exists, now just has points instead of being a solid line: Now showing with all the shapes separated to show the points: Now I will show my discovery. The longer the line in the overlap, the more points it will create. As if proportional to the amount of space within an overlap. If I were to do it closer to the top or the bottom of the overlap, it would only generate 2-3 points. But watch what happens when I increase the side of the line within the overlap, the first image being the before operation and the line shown at the red arrow: And now look at how many points... I was excited to use this software as it had shown a lot of promise in replacing Adobe for me. I couldn't justify spending so much on CC and Affinity looked solid. So far it had been. But it came time to do some shape building to create a logo using a bunch of circles (similar to how the Twitter logo was created) and I ran into this problem. I've tried this both with Hardware Acceleration turned on (by default) and with it turned off just in case. I secretly am hoping that I've just done something wrong and this can be sorted much sooner so I can get back to enjoying using Affinity products. =] Another thing to note: Intersect operation causes a single layer of curves to appear, but nothing is in it; Xor operation adds a few straight lines with some of the ellipses but combines all ellipses into a single curves layer shape, so those aren't working correctly either with so many overlaps. I had a sudden panic moment thinking that this 'could' be intended behaviour, but then I found this: https://affinityspotlight.com/article/creating-compound-shape-variants-using-boolean-operations/ which even shows an example of 4 ellipses being used and it separating properly. =] Note: I'm assuming Photo and Designer have the same logic, because I tried to replicate this in Affinity Photo and the same thing happens via Layer > Geometry. (Which then lead me to another problem where if Designer is open, Photo won't open at the same time, and if Photo is open, Designer won't open. Both programs show the splash screen, loads fonts...and then just silently closes; did I break everything!?) I should stop now before I break something else... - Shane Avery
  2. Hi, I'm trying to create a singular curve by joining multiple individual curves together using the ADD boolean operation, but it is not working as expected. I have the following design below consisting of multiple curves, and basically I want to join them together so it becomes one single curve: When I used the ADD boolean operation to attempt to join the curves together it came out looking like this: I also tried to use the XOR boolean operation and then use the "Break Curve" and "Join Curve" options respectively to remove the newly intersecting pen curves, but for some reason the areas where the curves should join right after implementing the XOR operation become a jumbled mess (which makes using the Break- and Join Curve actions almost impossible): Hence I'm asking for help with this because I truly don't know how else to achieve this. Not sure if this question has been asked before in the Forum, but any help would be truly appreciated :).
  3. I have recently shifted from Adobe to Affinity. Most of my work is related to Designer, I use Photo occasionally. I’m very satisfied with it overall. I can do pretty much everything on Affinity which I could do on Adobe. But I have noticed that there are some very basic tools which are missing in Affinity apps. Here, I’m making a list of those tools. My request to Affinity decision makers & developer team is that, please include these tools in Affinity 2.0 as designers are desperately waiting see these in Affinity (Most of them are just related to Designer but some are missing in Photo too): Freeform Gradients Gradient Mesh Tool Vector/Pattern Fill Shape Builder Tool Live Tracing Perspective Distort/Free Transform RTL Languages Support Blend Shapes Inefficient Boolean Operations 3D Text Tool Simplify Curves Live Mesh Warp Filter
  4. Hello, I'm using Affinity Designer almost every days for the last 2 years and everything was fine, until i update it to the version. Now, i can't use Boolean operations anymore : it freeze when i try to do so. Sometime it works, but most of the time it doesn't. When it freeze, i have to close the window to close AD. What can i do ? Affinity Designer is my working tool n°1 ! Thanks for your help ! Edit : i tried to desinstall and reinstall Affinity Designer and the 1.8.4 update, but boolean operations still freeze AD... Edit 2 : actually, it seems that it's only with an old afdesign.file that i have this issue. But i really need to work again on this file, that i first create only 4 months ago, not so long ! Any tips ?
  5. I'm expecting smooth cuts when I subtract the lines from the circle. I happened before but i made an error, now it keeps staggering near the top few lines. Any pointers as to what im doing wrong? The circle and rectangles have been converted to curves. I have tried doing them individually but keep getting the same error.
  6. I’m working on seamless pattern tiles in Affinity Designer and need to keep objects inside a square. Everything touching/outside of the square edge needs to be cropped. I’ve simplified my question on the attached image. The problem is: It looks like the Boolean crop operation can only work on two objects at a time. With hundreds of objects, how should I crop the parts outside of the square? (with different colour I am unable to create compound shapes.) p.s. clipping, masking, hiding the parts out of view not an option.
  7. Almost every time I run a boolean operation to divide or unite vector curves in AD, it freezes on me as shown in attached image. I have to force quit and restart the app and try again in smaller doses or move it to Illustrator and try again there. I have an iMac with 12GB of RAM - I don't know if the issue is I need more RAM, or if it's still a bug Affinity is fixing? I ordered more RAM recently, so I'll be able to try it again after installing it to see - but I wanted to see if anyone had any info pertaining to this issue - thanks!
  8. I do a lot of logo designs and I'm running into some issues, when I'm building a shape using multiple pieces of geometry, and want to "Add" them together to create a single compound shape it sometimes leaves micro-gaps. It's most notable when you "Divide" overlapping shapes, and then "Add" them again - it will always leave these gaps and it's really annoying. When I do "Add" I expect it to fill in those micro-gaps. I wish we had the Shape Builder tool already
  9. Hi ,I am not able to do the Boolean operation in iPad.what ever I click it does only addition and I saw a tutorial and in that selected shape will change color of the other layer down .it didn't happen in mine . what am I doing wrong?
  10. Good day! As you can see, there are 2 objects in the attachment: a circle and a line. I was trying to divide the circle into 2 pieces using the divide Boolean operation but failed. I believe the circle is supposed to be divided into 2 pieces, but that's not happening. But why?
  11. Hello guys, I was wondering if it is possible to do non desctructive boolean operation and yes it is possible. My only regret is that is very hidden. Wouldn't it be possible to create a "compound" group directly in the "Layers"? Say you select several shapes and you have the option to create compound group with a default boolean operation which you can change for every object afterwards? Other thing, it is really hidden that you have to alt-click a boolean operation to make it non desctructive. Would it be possible at least to add something in the tooltip and even better indicate on the boolean operation there is more that one op? You could fore example popup a menu if you click and hold on the boolean operation. Cheers, DrM0lek
  12. I love the corner tool - awesome stuff. But as soon as I apply a boolean operation to shapes (add, subtract, intersect, divide, combine) their corners become baked and the ability to edit corners is lost. I imagine that it *might* be possible for any unaffected corners to retain their corner tool setting (i.e. existing corners with a corner tool setting applied, that are not created or changed by the boolean operation being applied). This would be a great help. Currently when ever I want to apply a boolean operation on a shape that has a corner, I first have to zero the corner, remember what it was, then reapply it after the boolean operation is applied.
  • 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.