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

1.7.2.147: Magic wand tool not working


Recommended Posts

In latest beta Magic wand for the layer under the topmost one is totally broken - sometimes it always select "empty areas" (regardless of color under cursor - on screenshot i clicked inside yellow blob and get selection OUTSIDE of it!). Sometimes select nothing at all, even on high tolerance. This is with "Current layer" option enabled

Selecting "All layers" helps - but for isolated editing (alt-enter layer) this option is not usable at all, since wand select areas including invisible areas, ignoring current isolation (isolated layer)

Снимок экрана 2019-07-22 в 11.55.03.png

Untitled.afphoto

Link to comment
Share on other sites

5 hours ago, IPv6 said:

since wand select areas including invisible areas, ignoring current isolation (isolated layer)

Try changing your tolerance. It is at 20%

Mac Pro (Late 2013) Mac OS 12.7.4 
Affinity Designer 2.4.1 | Affinity Photo 2.4.1 | Affinity Publisher 2.4.1 | 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

1 hour ago, Old Bruce said:

Try changing your tolerance. It is at 20%

Does not help // Plus, it`s a blob of the same color, you can check attached file.
This blob should be selectable even on 0 tolerance (without semitransparent edges), i suppose

Link to comment
Share on other sites

12 hours ago, IPv6 said:

Does not help // Plus, it`s a blob of the same color, you can check attached file.
This blob should be selectable even on 0 tolerance (without semitransparent edges), i suppose

Same here. It doesn't work!

iMac 2017, 16 GB RAM, Intel Iris Plus Graphics 640 1536 MB, MacOS Ventura 13.6.6 (22G630) - Affinity V2-Universallizenz 

Link to comment
Share on other sites

  • 8 months later...
  • Staff

Sorry.

Thank you for reporting a problem using the pre 1.8.0 beta builds. It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script. 

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the release build.

Patrick Connor
Serif Europe Ltd

"There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self."  W. L. Sheldon

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • 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.