Marina P.

Ah, now I understand this, thank you for the explanation! I hope the developpers will fix this problem soon!

--> Yipppiiieeeee! I hope SO much that this absolutely annoying and disappointing issue will vanish in the (near) future!!!! --> I am not sure if "RAM" is the real problem? I mean, my iPad Pro has got 4GB of RAM and there are no other RAM-challenging Apps open.

I don't understand that either. In my case I can do what I want, the bag comes up in every single document, too. Earlier or later, but certain. This is a major bug ... Sometimes I wonder if they are just not able to fix it and so ignoring the best strategy ... ?

Thank you for the useful trick! I wonder if everyone else has accepted this bug or if the bug has vanished? As it comes to my case, I'm still waiting for a fixing - Update!!!! 😩😡 Because I mean, it can't be that we have to invent strange methods for not having wasted the money, can it?!? Is this really the interest of Sérif? (Sorry but this bug is more than annoying, and not fixing it is really outrageous.)

Hi Waterlili2020, I'm not sure if your problem has something to do with the random rectangles on iPad, but there are similarities ... That "Undo" doesn't help is one of the problem because there is - very often - data deleted, also in the history. In the cases where undo helped, it was only a question of time until the next issue occured. The only way to stop the permanent damage unfortunately only is to open a new project and to hope that you've got the luck to have healthy copies of the damaged layer in storage. But this way of course, a workflow is not possible, 'cause you cannot endlessly copy layers and save copies of the project and so on. So in my opinion the app has become somehow unusable ... To be honest I can't exactly tell what is the concrete defect in your artwork. There are many rectangles "over" the drawing, but this could be purpose? Which area exactly is the one with the blue recangle in the layer panel? Can you tell the exact moment the error occured in your layer, so can you remember what was the direct cause? Because I somehow suspect some of the brush-plugins to be the problem. When I avoid them and only use standard brushes, the error stays away, at least as far as I could test it. I'm not sure if the developpers really search for solutions ...

In the third clip you can see that the brush startet to erase pixels around itself. When I startet filming, it seemed to be normal again, but undoing led to full damage of the layer.Strangely, today I wanted to trigger new "examples" in the same file with the same brush, but everything worked well. I don't understand this.

Damaged masked layer with rectangle brush.mp4 Strange brush, rectangles.mp4 Rectangles 2.mp4 Erased rectangles, in history.mp4

Hello, some days ago startet a little drawing but after a few minutes the bug happened again. It got worse and worse so that I wasn't really able to work on it any more. I want to show you in four little clips how the issues looked like. There are some aspects of what could have been the cause for the sudden problem: 1. Unfortunately, there is the annoying case that when I want to lay down my (left) hand on the display, it happens that in the first instance, one point of my little finger and one point of the hand are touching it at first: The App thinks it is zooming, and the layers flicker rapidly and often also I touch some other commands like masking out the functions ( I don't know the English terms) or I activate unintentionally the pipette. Yesterday it was the fast flickering and masking out, and shortly after that the problems began. 2. It could have been the Frankentoon Neptune Brush ("Osaka"), having had a latent strange performance so that I thought: "Oh dear this won't go well ..." 3. Also the zooming was problematic, but I'm not sure if this was before or after the bug occured. 4. As always the "undo"-function was the direct trigger. 5. Yesterday I noticed that the adjustment-layer for changing colours doesn't work as flowingly as it did for a long time. While using the slider for going through the colours, there was not the clean surface but at first big rectangles in wrong colours to see. I know that this might not be fit to this case, but I wonder if there isn't a coherence?

Hello ericosmosNEW, mainly I work with pixel brushes, but somehow there are much more functions in AD than in Procreate, I was so happy to have this wonderful Sérif-App. But now this issue has changed that badly. And there would be much more to do for the developpers: I know someone who purchased AD and AF as Desktop Versions, but they always crash after some time without saving. No update changed this, the programs are completely useless for him, so he went back to Photoshop very quickly. Happily on my laptop Designer and Photo both work well. So I think that somehow, all these issues depend on the devices/hardware/versions, whatever.

Yes, this would be really great. I wonder if it would be an option to send a report via email directly to the Affinity Support?

Thanks for your advice! I have Procreate installed a time before Affinity Designer, but it was indeed too simple for me. I don't do such giant work like you but this drawing above is so simple because the bug forced me to keep it that way, as every second stroke and layer got ruined.

In the third clip you can see that the brush startet to erase pixels around itself. When I startet filming, it seemed to be normal again, but undoing led to the damage again. Strangely, today I wanted to trigger new "examples" in the same file with the same brush, but everything worked well. I don't understand this.

Erased rectangles, in history.mp4 Erased rectangles, in history.mp4 Rectangles 2.mp4 Strange brush, rectangles.mp4 Damaged masked layer with rectangle brush.mp4

Here I show you the clips. You can see how the layers are destroyed. Sometimes it could be "repaired" going back in history, sometimes not. --> The undo function was the direct cause.

Hello, yesterday I startet a little drawing but after a few minutes the bug happened again! It got worse and worse so that I wasn't really able to work on it any more. I want to show you in four little clips how the issues looked like. There are some aspects of what could have been the cause for the sudden problem: 1. Unfortunately, there is the annoying case that when I want to lay down my (left) hand on the display, it happens that in the first instance, one point of my little finger and one point of the hand are touching it at first: The App thinks it is Zooming, and the layers flicker rapidly and often also I touch some other commands like masking out the functions ( I don't know the English terms) or I activate unintentionally the pipette. Yesterday it was the fast flickering and masking out, and shortly after that the problems began. 2. It could have been the Frankentoon Neptune Brush ("Osaka"), having had a latent strange performance so that I thought: "Oh dear this won't go well ..." 3. Also the zooming was problematic, but I'm not sure if this was before or after the bug occured.