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

Marina P.

Members
  • Posts

    30
  • Joined

  • Last visited

Everything posted by Marina P.

  1. Ah, now I understand this, thank you for the explanation! I hope the developpers will fix this problem soon!
  2. --> 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.
  3. 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 ... ?
  4. 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.)
  5. 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 ...
  6. 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.
  7. Damaged masked layer with rectangle brush.mp4 Strange brush, rectangles.mp4 Rectangles 2.mp4 Erased rectangles, in history.mp4
  8. 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?
  9. 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.
  10. 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?
  11. 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.
  12. 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.
  13. Erased rectangles, in history.mp4 Erased rectangles, in history.mp4 Rectangles 2.mp4 Strange brush, rectangles.mp4 Damaged masked layer with rectangle brush.mp4
  14. 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.
  15. 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.
  16. Yes, I know and as I've described in my first post, this happened also to me very often. It happened to me that 1. Zooming in and out got problematic (Note: Zooming a selected area produced even strange patterns ...) 2. Brushes paint rectangles which damage the layer, especially after undoing. 3. The whole layer got cropped down to a little rectangle. 4. Brushes cut out irreversible rectangles in the layer. 5. All of these issues could not be resolved. As I was trying to reproduce one of these problems today, I was surprised by the rendering-issue above. But you're right, this was not the same, as it got ok again.
  17. Yesterday I've continued working on the actual drawing without any problems. Today I tried to trigger the bug one more time in an older file of the same project, drawing like crazy, with zooming. I don't know what happened but also the zooming is working quite well, two weeks ago it was hardly possible any more. However, just before I dediced to close AD, the bug appeared for one time, after I had "undone" all strikes with brush and eraser, with the canvas slightly rotated. But then something strange happened. I decided to take a screenshot of the corrupted layer. After I saved the screenhot and closed it, the layer was fine again! I'm really confused now. But here's the screenshot, so I can prove it wasn't a bad dream:
  18. Yes, I've only got Affinity Designer on the iPad - I find it interesting that this bug appears in both apps, so the problem might lie somehow deeper in the construction of the Affinity programming. Which would not be very reassuring ... I think that there are many more issues which are reported to the developpers, but for me ours is certainly a major one. So I hope it will be right on the top of their "bucket list". Normally I would never want to be annoying, but in this case we are right to report the problem regularly, as we surely speak for a lot of more frustrated users who are not in this forum.
  19. Hey ericosmos, I just converted your file on the Desktop Version into "afdesign" to open it on my iPad and then tried to cause the bug, but it didn't happen. What exactly would have to be done to trigger it? I tried to draw on existing as on new added pixel layers, I zoomed like crazy and painted with different brushes in giant and normal sizes, different colours, used the "undo"-function very often and it all worked. It's crazy because I myself was near the point to stop doing anything on AD because the bug appeared in every file and got worse and worse. So until now I don't have a clue what REALLY causes the bug, which components are necessary to prompt it. The only thing that was apparent was that most of the strokes had a very, very strong delay, especially when the brush was very high sized - but maybe this is normal considering all the complex layers in the document? During this time of delay I could see something interesting, because I could see how the brush is "working": At first the brush produces a rectangle! And this rectangle then is "filled" by the pixel information. So I could imagine that - when the bug happens - the brush will delete data in these rectangles. On the other side, it also happens that a whole layer is cropped to a tiny little rectangle by itself ... I don't know why I could not provoke the bug yet, but still don't dare to believe my iPad is healed. I will share all news I get with you. I looked up again in this forum what iPad types are affected by the bug: iPad Pro 10,5 (2017) iPad Pro 12,9 (2017) iPad Pro 12,9 (2018) (two cases) iPad Air 3. generation (2019) iPad Pro 12,9 (2021) I'm not sure but I think the reason for most of the iPads being Pro models is that other iPads don't support the Apple pencil and iPad Air 3 was the first to do that. For me it doesn'l look like the bug is depending on the device, it can happen with every one. I hope the developpers will be able to fix this, this would really be important!
  20. I didn't have the possibility yet to try to trigger the bug for al longer time. I painted wildly with different brushes in different sizes and colours, zoomed in and out. Nothing bad happened! (I bet I have to continue my painting until I get a creative flow and forget about the bug - then it appears .. ?) I wanted to share my iPad info here. And I'm "curious" what I'll experience once I continue the actual drawing.
  21. Yes, that i right that the undo-function often removes more. Several times I didn't have the issue with the rectangles, but if I had (for example) a drawing out of 20 lines and I clicked "undo", the last 15 lines were removed at once.
  22. Hi Vosje! As I described "my" issue more in terms of the destructive "undo"-functions, I've also always supposed it has sth to do with the pixel brushes, Neptune, Rusty Nib & Co. It's interesting that it seems to get worse with encreasing the brushe's size - I will test this. With the brushes I already had another issues, too, for example that they didn't paint, or that there is a strong delay. Also zooming in and out is mostly not possible without waiting several seconds. I wonder if all these problems are caused by one single bug? And why don't other iPad users have this problem as well? Which iPad do you use? Mine is an iPad Pro 2. Generation (2017). I don't know if the issues depend on the devices. The RAM of my iPad is 4GB but there are these issues anyway.
  23. Oh I didn't know I'm part of a club!:-) In my case, it's Affinity Designer, but the same problem. It is a bug and there is currently no solution yet. It needs to be fixed by the developers who already know about the issue.
  24. What you discribe is exactly the same to my issue. Also that using a pen can cause the damage has happened sometimes. And changing brushes seems also to be problematic in some cases. I'm "glad" to hear that this issue is a known bug so that I hope that it can be fixed in the near future. I didn't have the opportunity to work with AD after the Update to 15.3.1., but I don't really believe that the issue has vanished by that.
×
×
  • 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.