Jump to content


  • Content Count

  • Joined

  • Last visited

About kumarab123

  • Rank

Recent Profile Visitors

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

  1. Thanks for clearing that up. Yes, it seems to plateau at around 2.0 to 2.3 Gigs for me, for a few simple RAW develop/JPEG exports. Regards
  2. I had made an earlier thread regarding performance issues here, and I don't know what's happening with that. I've been using Affinity in 1minute short bursts since then if really necessary, and Capture One for most other things. I'm hoping 1.7.2 brings some good news. Anyway, I've noticed something odd by chance. I've no idea if this is intended or a bug, but Affinity Photo seems to have issues with releasing/flushing RAM. You fire it up, it takes about 130-135MB. You open a RAW it takes up around 1.4 GB. You develop the RAW and do some Photo Persona editing, and it takes around 1.5 to 2.0 GB
  3. I made a similar topic. Mine doesn't happen at random though. It takes a few minutes of working on a RAW (maybe it happens with other things too, but that's my usual workflow), and then Affinity just starts crawling/freezing, taking the entire system performance down with it. Don't know what's up.
  4. Nothing is running that didn't before. The task manager itself takes about a minute to populate after that. If I leave it be for like 3-4 minutes, then the laptop starts responding normally again. As I said, it never happens immediately. It builds up over time. I have reinstalled Affinity to no avail. Happens with only the latest release version. 1.6.5 ran for hours without a single hitch. Everything else runs fine, Capture One, DaVinci Resolve, you name it. As it stands, it's pretty much unusable for anything but 30 second casual edits. I have tried to narrow it down to a specific e
  5. Recently updated to the 1.7.1 official release. This doesn't seem to happen with jpegs, but if I develop a RAW (this is also much slower than before) and then maybe work for more than 3-4 minutes in the Photo persona, then the system starts crawling. It almost feels like a memory leak or something. Even if I manage to somehow close Affinity, the problem doesn't go away. The entire system crawls. I have to restart. 1.6.5 was snappy, really snappy. For clarity, by crawl I mean...click on a tab and wait 30 sec for the pull down, wait about 2 minutes for a simple curves merge. Should I just r
  6. I'm not sure it's a graphic driver bug. I have the latest Nvidia drivers as well, and no issues. There was no such issue on the earlier driver version too. There's an AMD user with the same issue in this very thread thread. Then there are users who developed this issue only after the update. There was also a .NET quality rollup update in September that introduced graphical problems with WPF applications. I'm guessing that's most probably the culprit here.
  7. Works the same as before here. Although I've found the non-edge aware brush to be pretty aware since I started using AP. If you don't stroke too fast that is (no pun intended).
  8. Sorry to hear that man. Must be frustrating. Hope you get this issue resolved asap. Good luck!
  9. They work fine here. They will be greyed out if your active selection is an adjustment/filter or image layer.
  10. @vstrava It's probably not your issue. But you could try redownloading the installer. Remote possibility, but maybe it's a corrupt download?
  11. Checked again. Yeah, takes between 45 to 50 seconds. This is very odd indeed. Why is 1.5 so many orders of magnitude faster than the latest release?
  12. THis is quite strange. I didn't wait for that long. THese are 18.2 MP files. Also, it doesn't matter if it's a linear function or not, when the 1.5 release does it in 3-4 seconds flat on the same files.
  13. Depth of Field, both Elliptical and Tilt Shift? They haven't worked here for the last three betas and the current public release. Another poster mentioned this one of the beta threads.
  14. As with the beta, it persists in the official version, The filter loops. CPU usage goes up to 80% and touches 100 at times. Even if you ESC out and close the program altogether, the exe still stays in memory. You have to kill it from the task manager.
  15. Thanks for the response. That's understandable. I just found it surprising that a bug introduced by a beta hasn't been addressed for three straight releases. Good luck with ironing the bugs out. Eagerly awaiting the 1.6 release. Cheers.
  • 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.