Jump to content

Join Curves Weirdness


Recommended Posts

I created a curve. Then copied it to make a mirror image for perfect symmetry when joined. I positioned them, selected them, clicked on the node tool, then clicked on Join Curves from the context menu.  Not thrilled with the result. Any thoughts as to what I am doing wrong? 

Before and after Join pictures below. Red is just to show that there are two curves before join.  Changing to black isn't the problem. The weird jag in the curve is.

Screenshot 2023-09-15 at 7.01.09 PM.png

Screenshot 2023-09-15 at 7.02.13 PM.png

Link to comment
Share on other sites

Try changing the direction of one of the curves.

Alternatively, try to delete the end point for one of the curves so that the two node are not so close to each other.

Edited by Pšenda

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.5.2636 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.4317.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.4317.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

11 hours ago, GregoryOR said:

Any thoughts as to what I am doing wrong? 

Possibly there is a bug. Often best to attach a document (in the state before doing the join) for examination, otherwise multiple incorrect guesses could confuse matters in addition to being a waste of time and effort.

Link to comment
Share on other sites

@GregoryOR, Try this. Select these two nodes

ScreenShot2023-09-16at6_38_34AM.png.5678030961a65dbe6ed74ae0019cdac8.png

Convert them to Sharp nodes. This will get rid of the loop out and back, the curve should just go from one the other in a straight line afterwards.

Mac Pro (Late 2013) Mac OS 12.7.6 
Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Link to comment
Share on other sites

23 minutes ago, Old Bruce said:

Convert them to Sharp nodes.

Doesn't the square shape of this nodes indicate that they are/were sharp nodes already?

To me the resulting loop looks rather like a relevant overlapping of the two curves before joining them, with the upper node belonging to the lower (red) curve – although the first screenshot doesn't look like an overlapping position of this nodes (but shows rather empty space between this two nodes).

macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1

Link to comment
Share on other sites

3 minutes ago, thomaso said:

Doesn't the square shape of this nodes indicate that they are/were sharp nodes already?

To me the resulting loop looks rather like a relevant overlapping of the two curves before joining them, with the upper node belonging to the lower (red) curve – although the first screenshot doesn't look like an overlapping position of this nodes (but shows rather empty space between this two nodes).

Yes they are Sharp but I'll wager that there is a handle coming off of each of them.

No two curves are not overlapping, they are a discreet distance apart. They only appear to be overlapping due the the Cap settings.

Mac Pro (Late 2013) Mac OS 12.7.6 
Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 | Beta versions as they appear.

I have never mastered color management, period, so I cannot help with that.

Link to comment
Share on other sites

11 minutes ago, Old Bruce said:

I'll wager that there is a handle coming off of each of them.

Wouldn't such a handle be visible in the first screenshot, even for unselected nodes? (… which as you confirm do not show any line between the two nodes)

Like so, either or: (in both samples the lower square node belongs to the yellow curve / no node overlapping):

squarednode2.jpg.41c351ec17a9f9913a2a4efa8b3850fc.jpgsquarednode1.jpg.7658d70e19334e28827526da5aa1e126.jpgsquarednode3.jpg.9b800663d9ee385cc370f256c6fb7c93.jpg

However, maybe we can get a screenshot of @GregoryOR with the two nodes selected, before + after joining.

macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1

Link to comment
Share on other sites

Thanks everyone for the discussion. Things I tried based on the discussion, which didn't change the result:

1. Selecting both nodes and clicking on the sharp button in the Convert section (whether that changed them or just made them sharp again, I don't know). That removed a node next to the end node, but didn't change the result of the Join action.

2. Moving them further apart, which also didn't change it

3. Changing direction of one of the curves

4. I can't see any handles, but have attached screenshots that @thomaso suggested. The strange added selection point after the join, way off my artboard is clearly related, but I don't know how it got there.

I have also attached the file, with a bunch of copies of the curves, in case that helps with troubleshooting. If it's a bug, then I guess I don't feel as stupid. My solution to move forward with the project was to expand the stroke and add them together, which gave me the desired result. I'd still like to understand why the joining curve function isn't working as I would expect.

Thanks again for the help

Screenshot 2023-09-16 at 10.43.05 AM.png

Screenshot 2023-09-16 at 10.47.57 AM.png

JoinTest.afdesign

Link to comment
Share on other sites

13 hours ago, GregoryOR said:

So it IS a bug then.  I am also using 2.1.1, but with the latest Mac OS: 13.5.2 (Studio M1)

I've noticed today your bug has been reported a few times by iPad users, therefore it seems to be a problem on Apple Silicon devices but not on Intel devices.

Link to comment
Share on other sites

On Monterey 12.6.9 (MBP 14" M1 Pro), no problem. 

  1. Open the file JoinTest.afdesign (in Publisher 2.1.1, as I'm more used to it…)
  2. (Move tool: Shift-select both curves)
  3. (Node tool: Shift-select both extremity nodes to link)
  4. Click on the Join curves button in Contextual toolbar
  5. Only one curve results, with two square nodes in place of what were extremity nodes. 

Affinity Suite 2.5 – Monterey 12.7.5 – MacBookPro 14" 2021 M1 Pro 16Go/1To

I apologise for any approximations in my English. It is not my mother tongue.

Link to comment
Share on other sites

7 hours ago, lacerto said:

Interestingly, does not work on a Silicon mac (2.1.1 on Ventura 13.5.2) even when forcing Rosetta, but does work when using Designer 1.10.6 on the same computer (native and Rosetta).

Hmm, I just tested it myself, and yes, in v.1 it works fine. So it's the interaction of v.2 with OS 13 with M1.

Link to comment
Share on other sites

8 hours ago, GarryP said:

One way to do what I think you want to do is shown in my attached video.

Note: This only works with Designer as I use the Point Transform Tool (in Translate mode) to get the two end points of the curves to the same position before the join. (If the two ends aren’t in the same position you will get a line between them.)

Interesting. I just tried the Merge Geometry function myself, without the point transform or overlapping the 2 end point, and it worked fine.  Not sure conceptually what the difference is between merge and join, but merge works and join doesn't. Quite odd! This is the easiest fix so far! Thanks.

Link to comment
Share on other sites

14 hours ago, GregoryOR said:

So it's the interaction of v.2 with OS 13 with M1.

Rather, just out of interest - the influence of the OS on the internal calculations of the application is strange. It must probably be the effect of HW Acceleration, which may be used for calculations. Would you try turning off HW Acceleration?

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.5.2636 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.4317.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.4317.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

On 9/18/2023 at 12:59 AM, Pšenda said:

Rather, just out of interest - the influence of the OS on the internal calculations of the application is strange. It must probably be the effect of HW Acceleration, which may be used for calculations. Would you try turning off HW Acceleration?

Thanks for the suggestion. I tried deselecting "Enable Metal compute acceleration" in settings under Performance>Hardware acceleration, but there was no change in the behavior.

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.