Jump to content
THESE FORUMS ARE READ-ONLY: Please Read Me ×

Recommended Posts

Posted

I can confirm this, not only in AD but AP as well.

Affinity Photo 2.6..; Affinity Designer 2.6..; Affinity Publisher 2.6..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win11 Home Version:24H2, Build: 26100.1742: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD; Wacom Intuos 3 PTZ-431W

Posted

Hi @Wildwood and welcome to the forums,

This is a known bug which was logged back in March 2021 (AFD-5311) which, as far as I'm aware, is still awaiting a fix...

Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted (edited)
3 hours ago, Hangman said:

This is a known bug which was logged back in March 2021 (AFD-5311) which, as far as I'm aware, is still awaiting a fix...

Thanks for the welcome, ....that's strange. I used this software earlier this summer and didn't have this issue, only now, after this new update.

Edited by Wildwood
Posted
2 hours ago, Wildwood said:

Thanks for the welcome, ....that's strange. I used this software earlier this summer and didn't have this issue, only now, after this new update.

Do you recall which version you would have been using at the time?

Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted
1 hour ago, Hangman said:

Do you recall which version you would have been using at the time?

I used 2.1.0 before. ... I just tested it and it works with this version, not sure with 2.1.1... Going to test it.

Posted
4 minutes ago, Wildwood said:

I used 2.1.0 before. ... I just tested it and it works with this version, not sure with 2.1.1... Going to test it.

In which case it sounds like a possible regression...

Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted
10 minutes ago, Hangman said:

In which case it sounds like a possible regression...

Seems like it, 2.1.1 works fine too, issue only in 2.2 so far.

  • 4 weeks later...
Posted

I can confirm this is an issues on Designer v2.2.0 on Windows. I don't recall this being an issues on previous versions going back to v1.8.5. I can recreate this issue consistently on my computer with the same behavior...dragging a swatch onto the node on the gradient as pictured by the OP. Freezes Designer then crashes. I am able to work around it by selecting the node first then just clicking the desired color in the palette, but that is not as intuitive. My co-worker is able to reproduce this as well on his Windows machine as well. 

I just tested on my Intel 2018 Macbook Pro running Big Sur 11.4 and I can confirm it is an issues on Mac as well. I had no issues on the previous version 2.1.x, then I ran the updater and tried again and it crashed. I haven't had a chance to verify this on my Apple Silicon Mac yet. 

  • 1 year later...
  • Staff
Posted

The issue "Gradient Tool: crash when dragging a swatch to a gradient node" (REF: AF-354) has been fixed by the developers in the latest beta build (2.6.0.3058). The fix is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

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