Jump to content


  • Content Count

  • Joined

  • Last visited

About danmerey

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. This is not the solution of the problem. If I change it to Russian keys, the I won't be able to use them in English. I want every hotkey work on any language (how it should be). "Everyone not using English keyboard need to do this" – this is not how it should work. Any normal Software / Service treat keys for shortcuts the same way, without deviding it on Russian, Spanish etc. symbols. Every key has it's ID on a keyboard, and it's the same whether it English or Russian. English "Q" and Russian "Й" has the same ID, same should be for "[", "]" and "Х", "Ъ". I'm sure it's very common issue, but not every user have enough patience to report these things.
  2. Brush resize shortcuts ("[" and "]") doesn't work on Russian language. To change brush size I need to switch keyboard to English every time (Alt+Shift). It's very annoying because I type in Russian a lot and every time I try to press [ or ] nothing happends until I switch input method. Most of other shortcuts work fine on both languages (like "B", "S" etc.). Please fix this
  3. Thanks for the response. You should definitely fix that in a new version, because default layout is bad IMHO, and I managed to restore my old one fast only thanks to my recorded videos of my work for my devlog. Also I had to restore my shortcut settings for Brush Tool, Pixel Tool, Select Tool, Erase Tool (I remove all duplicated shortcuts, so it doesn't change Tool Subtype on several presses) All other settings remain, but those that I lost was the most important anyway, so consider fix that in future versions please
  4. Hey, I just updated Affinity Photo from to 1.7 (downloaded installer and updated old version). I thought all my settings will persist after update, but no – all my settings reset, so now I have to restore my layout settings, hotkeys and maybe some other things. At least Favorite Fonts and Custom Brushes didn't reset. So, tell my is that so? Is that a bug? Is it intended behaviour (I hope, not)? If yes and it's because old settings and not compatible, why wouldn't you do migration from old ones to new, is that so hard? Is there a way to restore my old settings at this point without manually changing every thing?
  5. Jeez, it's not blurry, did you even watch video in the thread or check my *.afphoto file? It's called antialiasing or just some pixels with transparency and have nothing with corrupring/blurring image after merge. Also check video on the previous answer from @JimmyJack, there's no blur at all, because there's no antialiasing. Though image become blurred after the merge. How about to read the thread first? I mean, it's not that hard, right? I'll give you a tip, it's in the first message: >> To get "bugged" layer you can resize existing normal layer and it becomes corrupted for future merges Don't want to offend anyone here, but I'm tired of explaining simple things to people, who doesn't want to understand and to developers who don't give a f*ck about their own product. That's so furstrating. I was so happy that I found something instead of Photoshop and now I see how crappy support is. Or does Support should be so and it's "By Design", huh?
  6. In a nutshell: they are NOT blurry before merge, so they shouldn't be blurry after merge. Seems like you don't understand your own product. Worst support ever
  7. Didn't know that, since you were too active in these topics. Ok, then please stop saying nonesence since we need answer from the developers and you may confuse them when they come. You are not helping. We are trying to fix important issue here, and you just come to argue. It is not expected behaviour since my "pixel-allignment" always on but decimals will appear anyway. And it doesn't justify fact, that image after merge is not what it was before merge. I'm pretty sure that adding line of code like "RasterizeLayer(layer2);" before "MergeDown(layer1, layer2);" will do the trick. Because that's what I do with my own hands to avoid issue.
  8. Seems like you didn't read anything. I already mentioned how to get bugged layers: resizing it. And don't you dare to tell me not to resize anything to avoid the problem. Maybe I shouldn't use brushes too? It is one line of code that will close this issue once and for all, please stop this useless resistance. It seems that your team lack some QA, because no normal QA ever let pass such terrible bug and say "it's not a bug, it's intended behaviour" P. S. didn't know you are not a part of the Team, since you are way too active in those topics.
  9. It is in the app, jeez. Stop talking about technical reasons and pay attention to why this shouldn't occure. Please watch the video that I attached in the previous post and tell me it is normal behaviour. Now it looks like you are trolling us or just don't want to fix the bug. Worst customer support ever. None of what you mentioned shouldn't affect Blurriness of the picture and corrupt it. All that you explain is just "why this happens". Cool, now fix this please, because it's a bug and not intended behaviour for any normal software. We already showed how to fix this (by rasterizing lowest layer before merging)
  10. Thanks, olivierlafitte, this is what I was talking about. I've recorded video with Current Behaviour and Expected Behaviour (with rasterize before merge and without losing quality). If after this Affinity Developers will still insist that's it's "not a bug", I have no idea what to do here Merge_Down_Blur_Bug.mp4
  11. The fact that Affinity Developers try to convince us that it's "not a bug" is so frustrating. Seems like they never used their editor and don't understand simple UX rules. This is really disappointing and sad. Ok we got it – you didn't think of such scenario while developing Affinity, that's why such strange behaviour occured. Well, how about to fix that now, when a lot of people ask for it? – "NO, IT'S NOT A BUG, GUYS! SUFFER MORE"
  12. Can you please stop running away from problem and accept that there's a huge bug here? This facts shouldn't affect the merging anyway, this is not expected behaviour for any normal user. Merging shouldn't corrupt image in any way. "How it looks before merge" must be equal to "How it looks after merge". Why I need to make some stupid workaround to get normal behaviour of merge? If you change floating points to integer, problem still remains. How about to check it before posting this answer? That's why I said, that it's not the problem. Or I need to make a video to prove it? I'm really tired of explaining why this is a bug and not my imagination How can I avoid getting decimals in my image anyway? I can't because I use resize and rotation tools all the time. Or maybe I shouldn't ever resize anything so it won't corrupt after merge, lol? Come on, it's easy to fix (I already found a solution: just rasterize lowest layer before merging) – why do you make it so hard for us to enjoy the product and customer support? PLEASE, fix this already and stop making exuses. Software should be easy and pleasant in use, but we are frustrated instead (because of a bug and because of not wanting developers to fix it) Corrupted Merge with Integers.afphoto
  13. I started a new topic, since this one is pretty old and being ignored for a long time by Affinity Developers. If you have something to add, you are welcome. I also found an easy solution for Developers and one of the reasons, why this happens
  14. Hello, this bug is being discussed in another thread, but since it's being ignored by Developers for pretty long time, I decided to refresh it by creating a new topic with some new facts and a solution. "Merge Down Layers" (Ctrl+Shift+E) is very common and frequently used command, that we use to merge layers. Although it can corrupt your image in a lot of random cases by blurring you layers after merge. You can see what happens to layers if that occurs on attached image. After 1 merge you are losing sharpness, and after 2 or 3 merges you will start to notice that image got blurred, but it will be too late – your file is already corrupted. I attached *.afphoto file, so you can reproduce bug and see why this happens. I already found a workaround in the past, which is super annoying, but better then nothing – Create Empty Layer (Ctl+Shift+N) and merge down to this new layer. But today I found an ultimate solution for Affinity Developers, which is super easy to implement, and I hope they will do it ASAP: If you rastirize lowest layer before merge, nothing will be corrupted. So before Merge we should automatically rasterize lowest layer, and then we will never corrupt our image again. Some important facts for Affinity Developers: I attached *.afphoto file, you can reproduce the bug I reproduced bug in Beta too It's not because of "Force Pixel Allignment" or "Floating point coordinates" This is critical bug, that corrupts our work (I corrupted my images without noticing, other guys from previous thread also corrupted 4+ hours of work) This is not intended behaviour, please pay attention to this one and put yourself in our place This never happened in Photoshop with similar actions To get "bugged" layer you can resize existing normal layer and it becomes corrupted for future merges To fix this bug you just need to automatically Rasterize lower layer before "Merge Down" operation Thanks, hope you fix this asap and notify us! Corrupted Merge.afphoto
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.