Jump to content

dev4press

Members
  • Content Count

    11
  • Joined

About dev4press

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Yeah, OpenCL, and, I will keep it disabled for now. Hopefully, this will be sorted in one of the future releases. Thanks.
  2. I found another thread here about OpenGL causing performance issues in 1.9. I had OpenGL enabled, and when I disable it, crop works fine. Again, I had OpenGL active before 1.9, and it was fine. Whatever the issue is with OpenGL in Affinity Photo it is caused by 1.9 update.
  3. I use Crop tool often, and before 1.9 update, it was fine. But, since upgrade to 1.9 (and still present in 1.9.1), when I select region to crop, click on Apply button, and there is clear delay until the crop is done (approx. 2 seconds), and for a brief time, cropped image is wrong (showing top left part of the image), and then it renders properly. When this happens, CPU usage jumps to 100% on all 8 logical cores. Before 1.9, all was OK, crop was instant. Also, this doesn't happen always, but it it happens very often to be annoying, especially, if I use crop often. I use Windows 10 20H2 64
  4. Latest RC2, for me preview export doesn't work. Preview window is open and empty, and loader icon is spinning and it does nothing. Tried it with PNG, JPEG and GIF export. And, when I open Export Preview, memory usage skyrockets, from about 1GB to 4GB. The export preview starts working, if I close and reopen Designer few times. But, with any preview, memory usage is very high.
  5. All the issues I had with 1.7.3 are fixed in 1.8 Beta. Hopefully, 1.8 Stable will be released soon. 1.7.3 is way too buggy for any serious (or any other for that matter) use.
  6. I created the new Publisher document, set an image placement policy to 'Prefer Linked', worked on it, and placed 60 images inside, all images are in the Affinity Photo format, taking a total of 2GB. Saved Publisher document is now 2GB, so all images are placed embedded and not linked. I tried saving a new document, again, a new file is 2GB in size. Is there are way to force the Linked policy and have files loaded from disk not embedded in the document?
  7. Whatever the problem was, it is fixed in 1.7.1 version.
  8. Only save as is a problem (not save, that works fine), only with files made with an older version of the Designer, and when the save as is on the same drive. I use Avira Antivirus, but I tried with Avira disabled, doesn't have any effect on Save As.
  9. It is the same when using Admin privileges. One more thing I forgot to mention, the program actually creates a new file with the name I specified in save as, but that file has 0 bytes size. And, I am using the Affinity Store version. Also, I did some more testing. The problem happens if I save on the same partition, if I try Save As to another partition or external drive it works fine. If I open fine on partition E, saving works on all, except for E, if I open from D, it works on all except D. I installed back old Designer, it works fine.
  10. Hi, It happens with all documents created with the previous version of Designer, there are no problems with documents created in 1.7 version, it happens no matter where I save it (and D is a normal partition on the SSD drive inside the laptop), and Save As in the dialogue does the same. Also, note that dialogue displays the original file name, not the new file name I attempt to save to. Milan
  11. Using Affinity Designer 1.7.0.367, on Windows 10 x64 version 1809. Save As option is broken for any document I try to open and save. I have attached GIF with the recording of the error. Milan Petrovic
×
×
  • 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.