Marand313 Posted February 16, 2023 Posted February 16, 2023 I have been having issues with this since a recent update. This was not an issue in version 1 but initially it was only on more specialized brushes. Now it is showing up on soft round brushes and the freehand selection tool. I have noticed that it does have something to do with the size of the brush or selection or when zoomed in. I am not sure. But right now the app is almost unusable because of it. Quote
Staff Callum Posted February 20, 2023 Staff Posted February 20, 2023 Hi Marand313, If you fully restart the iPad app does this issue still occur? Thanks C Quote Please tag me using @ in your reply so I can be sure to respond ASAP.
Marand313 Posted February 20, 2023 Author Posted February 20, 2023 Still happens after a full restart. Not immediately but over time of using the app it gets worse and worse. What’s posted above is the worst it’s ever gotten. It always shows up on the specialty brushes and gradually builds up to the basic soft round brushes. Does not happen when brush is large, only under 200px and happens mostly when I zoom in. After the full restart the brushes work fine for a while but the brush menu ALWAYS looks like what’s pictured above. I’m on an iPad Air 5th gen. iPadOS 16.3.1. Latest affinity version. Quote
Marand313 Posted February 20, 2023 Author Posted February 20, 2023 Ok I am now seeing this on large brushes. I am not sure what I’m doing to cause this. It happens with the basic brush tool as well as cloning and healing. I use the brush at very low flow 3-7%. And I shift between large and small brushes a lot in my workflow. I did a full restart again and it cleared the artifacts from the brush menu but came back the more I used the app. I noticed it came back the more projects I opened including ones I have been working on for a couple days. Quote
Staff Affinity Info Bot Posted May 4, 2023 Staff Posted May 4, 2023 The issue "[iPad] Brush Panel corruption can occur with multiple brush kits installed" (REF: AFP-6132) has been fixed by the developers in internal build "2.1.0.1790". This fix should soon be available as a customer beta and 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 @Serif Info Bot to notify us. Quote
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.