Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by altae

  1. I will try these workarounds in the future...
  2. The screenshot I tried to upload is 117 KB in size and the resolution is 1918 x 1156 pixel. How can this be too large?
  3. But it's in their best interest to fix it (or get it fixed).
  4. Ah, now I've got it. Silly me 😉 Thanks for clarifying. The thread can be closed. P.S. Please fix the forum, not being able to upload screenshots is less than ideal if one is trying to document issues in a beta version.
  5. Today I tried to import a few macros into the stable version which I created with the above mentioned beta version. When I opened the dialogue to import the macros none of them where showing up even though I was in the correct folder to which the macros were exported. I took a closer look and realized that both versions (beta and stable) export macros with the file extension .afmacro while for importing macros they expect files with the extension .afmacros (with "s" at the end). Is this behavior on purpose? Or is it a bug/ an oversight? It gets even worse: Renaming the files to .afmacros
  6. Makes sense since I've got a Nvidia 2080 Ti in my system. Thanks for looking into it, I use that filter quite often.
  7. I uploaded 3 files: Two screenshots to document the issue and one afphoto file. To reproduce the error simply open the file with the latest beta, add a legacy 1.6 shadows & highlights filter and play with the sliders. Make sure that OpenCL hardware acceleration is active.
  8. The current beta (in fact the last one suffered from the same issue) shows artifacts when using the Shadows & Highlights filter (legacy 1.6, live filter as well as normal filter) while OpenCL hardware acceleration is active. Deactivating hardware acceleration fixes the issue. Btw: It's only the legacy version of the filter that shows these artifacts, the standard version seems to be fine. P.S. I'd love to upload a screenshot but unfortunately I cannot upload my .jpg files (an error message saying "-200" appears). I'd love to document this error message with another screenshot but:
  9. Here are the results for my Laptop (MSI Creator 15M): Intel Core i7-10750H Nvidia Gforce RTX 2060 (6 GB Vram) 32 GB Ram
  10. Looks like it has something to do with OpenCL hardware acceleration. As soon as I disable it the distortions are gone (when merging layers as well as when exporting). And it seems I'm not the only one who has been experiencing such issues with OpenCL: https://forum.affinity.serif.com/index.php?/topic/129141-random-squares-at-export/ Btw I changed the title as the issue is still present in the latest beta.
  11. I wanted to use the High Pass Live Filter to apply High Pass Sharpening to a photograph. Unfortunately there seems to be something wrong with this Live Filter as it introduces distortions when merged to a new layer or when exported. The attached screenshots as well as an exported image should clarify what I mean. There are no distortions introduced with the standard High Pass Filter.
  12. Because this means I have to use two different tools and as a result I get something that is way less convenient and intuitive than a simple overlay function for layer masks.
  13. Yes but that's not what I meant. What I mean is being able to draw the mask as a red overlay (at least that's how it works in other image editors) while the image layer still shines through. The refining feature is fine for corrections but it's not practical to draw a entire masks. The closest thing to what I would like to see is in fact the Quick Mask feature but sadly with this feature the mask cannot be altered once it has been drawn. Or rather it can be altered but not as a (red) overlay anymore.
  14. One more thing I've been missing for a long time: A decent preview mode for editing layer masks. Sort of like the quick mask where it's possible to show the mask as a red overlay. This is very helpful when you want to mask something and need to work exactly.
  15. Proper support for luminosity masks. Blend ranges are nice but no real replacement as they cannot be altered manually whereas with luminosity masks I can always correct a certain area and brush something in or out.
  16. Sorry, I thought that's the name of the pen. Apparently it's dependent on the tablet model. With my tablet switching to the eraser (and back to the previous tool) is the only thing that does not work, everything else is fine. I realized that the switch for high precision tablet input in the settings is gone, maybe it has something to do with this change. Well, it's a beta after all...
  17. Nope, my table is also concerned. In my case switching to the eraser by turning the stylus upside down does not work in the beta (it does work in the stable version). The rest of the functions work though (at least the ones I use).
  18. What tablet you've got? With my tablet (Wacom Intuos Pro Small, standard pen that came with it) it does not work. But as soon as I switch back to the stable version it works again as expected.
  19. In the latest Beta turning the Wacom pen upside down in order to switch to the eraser does not work anymore. In the stable version it still works as expected.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.