IanSG Posted April 12, 2019 Share Posted April 12, 2019 Not for the first time, the selection brush in AP has stopped working for me. Previously I've reset AP and everything starts working again, but I was wondering if there's any information I can get hold of to help the devs fix this oft reported problem? Quote AP, AD & APub user, running Win10 Link to comment Share on other sites More sharing options...
carl123 Posted April 12, 2019 Share Posted April 12, 2019 Is this on the released version or the beta? Unless it's reproducible on the beta it's possible it's already fixed. The 1.7 beta has had numerous fixes/improvements since it started and cant be that far away from being released officially Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time. Link to comment Share on other sites More sharing options...
IanSG Posted April 12, 2019 Author Share Posted April 12, 2019 2 minutes ago, carl123 said: Is this on the released version or the beta? Unless it's reproducible on the beta it's possible it's already fixed. The 1.7 beta has had numerous fixes/improvements since it started and cant be that far away from being released officially It's the release version - it works with the beta. This has happened to me maybe half a dozen times over the last couple of years (but count how many times it's cropped up in this forum). Each time it's happened I've gone to the beta to make sure I'm not doing something wrong, and then cleared the problem by resetting AP. It's possible that it's been fixed in the latest release, but I've got a solid example of an intermittent problem that's survived for a couple of years. Quote AP, AD & APub user, running Win10 Link to comment Share on other sites More sharing options...
carl123 Posted April 12, 2019 Share Posted April 12, 2019 It is my understanding that the released (1.6) versions will now never be patched. (Unless something like a major OS upgrade breaks them) Any bugs found in 1.6 that are fixed will be fixed in the 1.7 versions (beta and release) The 1.6 versions will always have those bugs for now and forever. So, if it has been fixed, your only choice is to use the 1.7 beta or wait for the official release of 1.7 Reporting known bugs in 1.6 that are already fixed in 1.7 seems pretty redundant now but new bugs found in 1.6 should still be reported as the fixes can be added to the 1.7 versions (beta then release) Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time. Link to comment Share on other sites More sharing options...
IanSG Posted April 12, 2019 Author Share Posted April 12, 2019 11 minutes ago, carl123 said: It is my understanding that the released (1.6) versions will now never be patched. (Unless something like a major OS upgrade breaks them) Any bugs found in 1.6 that are fixed will be fixed in the 1.7 versions (beta and release) The 1.6 versions will always have those bugs for now and forever. So, if it has been fixed, your only choice is to use the 1.7 beta or wait for the official release of 1.7 Reporting known bugs in 1.6 that are already fixed in 1.7 seems pretty redundant now but new bugs found in 1.6 should still be reported as the fixes can be added to the 1.7 versions (beta then release) All true - especially since we're looking at a new point release. But the same argument could have been made 6 months ago, and maybe 6 months hence. There's nothing in the beta release notes to suggest that the problem's been fixed. Quote AP, AD & APub user, running Win10 Link to comment Share on other sites More sharing options...
Jaffa Posted April 12, 2019 Share Posted April 12, 2019 Hi Ian, I hope that my suggestion is too basic, nevertheless, I recall that when I first started the selection brush happened to be in the "subtract" option. Simply switching on the toolbar above to "add" solved the problem. This happened many times before I "cottoned on". Quote Jafa - Just Another Fantastic Aucklander (Jim) Windows 11 Affinity Photo 2.4 Lightroom 6 Nik Collection and Topaz Denoise AI Intel Core i7 9700K @ 3.60GHz 32 °C Coffee Lake 14nm Technology Link to comment Share on other sites More sharing options...
Magi Posted April 12, 2019 Share Posted April 12, 2019 My retail version 1.6.5.123 brushes quit, so I down loaded the beta version 1.7.0.293. Same results. Using Windows 10. Help Please! Is there a windows update that is messing with affinity? Quote Link to comment Share on other sites More sharing options...
dutchshader Posted April 12, 2019 Share Posted April 12, 2019 @Magi Could you post a screenshot Quote intel core i5, 16GB 128Gb ssd win10 Pro Huion new 1060plus. philips 272p 2560x1440px on intel HD2500 onboard graphics Razer Tartarus Chroma Link to comment Share on other sites More sharing options...
Magi Posted April 12, 2019 Share Posted April 12, 2019 What is happening is that I select the healing brush or any brush press the alt key then I try to edit ,but nothing happens. Retail or Beta. Quote Link to comment Share on other sites More sharing options...
dutchshader Posted April 12, 2019 Share Posted April 12, 2019 @Magi is the layer You are working on selected in the Layerspanel? Quote intel core i5, 16GB 128Gb ssd win10 Pro Huion new 1060plus. philips 272p 2560x1440px on intel HD2500 onboard graphics Razer Tartarus Chroma Link to comment Share on other sites More sharing options...
Magi Posted April 12, 2019 Share Posted April 12, 2019 Using windows 10 home, i7 3.07 GHz., 12gs. ram, Asus Mother board, AMD Radeon HD 6800, 4 Samsung 32" monitors. Will have new computer build and on line in a week or two. Cooler Master full tower, Intel i9 9900k, Msi mother board, 64 gs. ram, M.2 hard drive with 2T SSD backup, ect. ect. ect., but I don't think my system is the issue. It worked fine a few weeks ago. Quote Link to comment Share on other sites More sharing options...
Magi Posted April 12, 2019 Share Posted April 12, 2019 The image is already merged. Just doing the final touches. Quote Link to comment Share on other sites More sharing options...
dutchshader Posted April 12, 2019 Share Posted April 12, 2019 After lhe layers are merged, is the merged layer selected? Quote intel core i5, 16GB 128Gb ssd win10 Pro Huion new 1060plus. philips 272p 2560x1440px on intel HD2500 onboard graphics Razer Tartarus Chroma Link to comment Share on other sites More sharing options...
Magi Posted April 12, 2019 Share Posted April 12, 2019 The brush doesn't even do the preview when you go over the image. Quote Link to comment Share on other sites More sharing options...
Magi Posted April 12, 2019 Share Posted April 12, 2019 Yes because all the other images are closed. Quote Link to comment Share on other sites More sharing options...
dutchshader Posted April 12, 2019 Share Posted April 12, 2019 Posting a screenshot would help Quote intel core i5, 16GB 128Gb ssd win10 Pro Huion new 1060plus. philips 272p 2560x1440px on intel HD2500 onboard graphics Razer Tartarus Chroma Link to comment Share on other sites More sharing options...
R C-R Posted April 12, 2019 Share Posted April 12, 2019 29 minutes ago, IanSG said: There's nothing in the beta release notes to suggest that the problem's been fixed. In the release notes for one or more beta versions there is typically a reference to "stability improvements." Such improvements can fix several different seemingly unrelated problems by eliminating the conditions that put the app in the unstable state that is the root cause of one or more functions not working as intended. Quote All 3 1.10.8, & all 3 V2.5.6 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 All 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
Magi Posted April 12, 2019 Share Posted April 12, 2019 I've closed affinity and reopened it with the image that I'm editing only. Quote Link to comment Share on other sites More sharing options...
Magi Posted April 12, 2019 Share Posted April 12, 2019 How can I give you a screen shoot in affinity? Quote Link to comment Share on other sites More sharing options...
dutchshader Posted April 12, 2019 Share Posted April 12, 2019 On your keyboard press " printscreen" after that in photo file>new from clipboard Quote intel core i5, 16GB 128Gb ssd win10 Pro Huion new 1060plus. philips 272p 2560x1440px on intel HD2500 onboard graphics Razer Tartarus Chroma Link to comment Share on other sites More sharing options...
Move Along People Posted April 12, 2019 Share Posted April 12, 2019 - Quote Move Along people,nothing to see here Link to comment Share on other sites More sharing options...
Magi Posted April 12, 2019 Share Posted April 12, 2019 Here you go. Quote Link to comment Share on other sites More sharing options...
Magi Posted April 12, 2019 Share Posted April 12, 2019 sorry I've got a lot going on. Quote Link to comment Share on other sites More sharing options...
Magi Posted April 12, 2019 Share Posted April 12, 2019 Kind of weird because like I said it worked fine a few weeks ago. Here's beta and retail. Quote Link to comment Share on other sites More sharing options...
dutchshader Posted April 12, 2019 Share Posted April 12, 2019 Nothing wrong in the screenshot that i can see. Only thing i can't see is if the layer is active in the layerspanel Quote intel core i5, 16GB 128Gb ssd win10 Pro Huion new 1060plus. philips 272p 2560x1440px on intel HD2500 onboard graphics Razer Tartarus Chroma Link to comment Share on other sites More sharing options...
Recommended Posts
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.