Jump to content

Recommended Posts

Posted

Tech stuff:

  • Apple M1 13" MacBook Pro
  • 16GB RAM
  • macOS Sonoma 14.5
  • Affinity Designer version 2.5.5
  • Hardware Acceleration: Same behavior with it on or off.

I'm not sure if this is related to the bug I posted yesterday (AF-4999) or not. If it is, you can roll it all together, if it's not, well then sorry here's a new bug.

I've been working on a series of sketches/copies as a learning exercise. So I have a large file with a bunch of artboards, and compound shapes made with a lot of curves, everything working as expected until I got to the selected artboard:

Screenshot2024-11-08at1_01_56PM.png.a507ff856f01fcdded6682f684d6383c.png

I thought maybe I reached some memory limit or something but unfortunately the behavior replicates in a new file: Boolean Bug.afdesign

The artboards in the file are scattered because I was wondering if it wasn't related to artboard positioning, like in my previous bug, but no luck with that so far. 

Here's a video of the operation working with no problem on artboard "Compound":

 

And here's it working with a straightforward boolean operation on the artboard "boolean":

 

But here's what happens on the "Broken" artboard:

 

Note that I'm testing first with "Add" because that eliminates the possibility that I'm misunderstanding what the result of a complex XOR operation should be. ADD just combines the two. Regardless, you can see that it's just not doing anything until Divide just erases the shapes (like with the other bug). It doesn't even register the operation in the History panel. Trying to do compound shapes (which is how I discovered the bug) is equally unpredictable.

Also, the curves in the "buggy" panel are different in the ones that are working. I've rebuilt the curves from scratch and had the same issue. In the first screenshot you can see that there are a TON of similar curves and designs and all of them worked until this exact variation. 

  • M1 Macbook Pro
  • 16gb RAM
  • Sequoia 15.5
  • Affinity Designer 2.6.0
Posted

Interesting. Using the additional "add" operation combine the merged curves gets me sort of the way there. I have to put the shapes in a compound and mess with the order until they stop disappearing to get the outcome I want.

For what it's worth, in the working example, the curve is broken up in the same way with no issue (in fact nearly every curve in my original doc is that way, just about (clip from my original dog an a similar shape):

NodesonWorkingShape.png.3c9afa1a0817f6a1d53913422c91fe3c.png

 

One thing I noticed was that when I was pressing "add" on the "broken" shape, nothing would happen in the history panel. Like an exception is occurring but not getting captured anywhere:

 

Whereas even clicking "Add" on a single shape it registers the action in the History:

 

 

  • M1 Macbook Pro
  • 16gb RAM
  • Sequoia 15.5
  • Affinity Designer 2.6.0

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.