Jump to content


  • Content Count

  • Joined

  • Last visited

About matterender

  • Rank

Profile Information

  • Gender
  • Location
    Milan, Italy

Recent Profile Visitors

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

  1. I spent the whole day trying to find a solution to this until now, You solved my problem !! Thanks a lot !!
  2. I agree, it is a bug, no other explanation possible. My workaround for it : 1) Group together the layers you want to merge (layers selected + ctrl +G) 2) Rasterize the group of layers That produces a merged layer without any blurring. I will never use ctrl +E (merge down) again until this bug won't be solved.
  3. Very very nice and useful ! Thank you so much for sharing! Matteo
  4. Hey it worked!, Thanks a lot ! But, to be honest I don't quite get what is the general rule to follow for the future... How do I know when a layer contains negative values ? Just because the same problem will show up again? Or that happens inevitably with certain layer types ? And, above all, where do I have to place the black fill layer generally ? Under the upmost layer with negative values in the stack, is that right?
  5. I think I figured out what it might be... or at least a workaround. The strange artifacts disappear either converting the file from 32bit to 16bit (with unacceptable loss in terms of colour depth,) or exporting it to HDR with the option "don't export layers hidden by Export persona" flagged (true). After that the file can be opened again in a new window (it will be flattened), modified and exported as jpeg or any other format without problems. The initial file was an .EXR, I opened it in AP and started working on it straight away without reducing the color format to 16bit, maybe there lies the origin of the problem? Anyway it seems quite clear to me that the issue is related to color format and color depth.
  6. No in that case I don't. see anything wrong. And if I save the file as jpeg the picture looks ok. It seems a problem with the shape tools. Both two first pixel layers are rasterized versions of a superimposed rectangle with gaussian blur FX.
  7. Hey MEB and R C-R, thanks for your help. Now at least I know it is not a malfunctioning GPU issue, and probably it has something to do with Windows
  8. ok R C-R, what do you see in the navigator? Is it looking good also there ? Because on both my PC at home and the one at the office (with different specs and AMD GPU), when I open the file it may look ok in the main window (if I don't do anything, like zooming in and out for example) but it looks with artifacts in the navigator. And, I see now, if I switch off the only one pixel layer with FX to it, the problem seems to disappear...
  9. ok firstdefence, here is the file that got corrupted. In the meanwhile I tried working on the initial clean copy of the file and after a while, adding a rectangle shape with gaussian blur and layer mode set on "reflect" it started giving the same problems... I will post both files, so you can experiment with them, thanks corrupted file.afphoto initial file.afphoto
  10. Hi there, I have problems with Affinity Photo files. When I zoom in and out, or when I use shape tools etc. I start getting artifacts like those you see in the picture I posted, and the worst is that the is still there when I save the file to jpeg format.. it looks to me like it could be a compatibility issue with my video card... my video card is: NVIDIA QUADRO K2200 OS win 10 PRO 64bit CPU intel i7-7700K 4.20 GHz 32 GB RAM Has anyone had this problem before or knows a possible solution to it ?
  • 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.