Jump to content
You must now use your email address to sign in [click for more info] ×

Mark Ingram

(Ex) Staff
  • Posts

    5,358
  • Joined

  • Last visited

Everything posted by Mark Ingram

  1. Is there any difference between Windows Zoom on your two computers Matt? I'm wondering if it's broken at 100%, but working at 200% (that's what I use, and don't notice a problem)?
  2. This is because you have only changed the size of the export, your document is still huge. As such, when you load the export dialog, it tries to calculate the file size of your export, by writing the file to a temporary location. We do cancel the operation when the dialog closes, but it can still take some time to complete. The real solution here is to change the size of your document by going to Document Setup. If you want to export at a certain pixel resolution, change your setup to use pixels, and resize to your required size. Edit: It looks like the temporary export (to calculate the file size) isn't cancelled, so I've logged this issue.
  3. It doesn't matter what the size of the Affinity file is, as it's a vector document. And as it's a vector document you don't need it to be over 3 metres wide. It doesn't matter what the quality is on export, you're still trying to export a *massive* image.
  4. I have a feeling it doesn't actually export the image. It looks like it's done it (instantly), but it shouldn't be instant, and you should see a progress bar. I think it's writing a corrupt image (we should definitely fix this).
  5. Hi, we do a two-pass draw so the first blurry lines are from the low-quality draw. However, I think there is a problem with non-even zoom scales, where it can make the result not smooth.
  6. When I just went to export your document, it defaulted to a size of 38,284 wide by 40,890 high. You get a warning saying this is bigger than the allowable size for PNG. Your document is 3.241metres by 3.462metres at 300DPI. So I'm not surprised it's slow! It will succeed, but it will take some time. Try creating a smaller document, resizing your existing document, or exporting at a smaller size.
  7. Open TaskManager (CTRL+SHIFT+ESC) and watch it when you are exporting. What is the CPU, Memory and Disk Usage percentages? Are there any other applications which report high CPU, Memory or disk usage at the same time?
  8. It does work. Like the dialog says, you need the Platform Update for Windows 7 SP1 installed first. If you click the link it will take you to a page with more information.
  9. OK, I've just checked the cursors for these tools, and the white outline isn't actually white! At 100%, it's only 30% opaque, and at 200% it's 60% opaque! I'll see about getting these changed to improve visibility.
  10. This is how it should work! If you don't fully use the CPU, it means you aren't working as efficiently as possible. If we used less CPU, then the application would be slower!
  11. The white outline appears OK on my screen... What OS are you on Matt?
  12. Feel free to make a feature request and we can look at it :) https://forum.affinity.serif.com/index.php?/forum/6-feature-requests/
  13. I think MEB was a little confused there, as this is actually a bug in the Windows product (was, it is now fixed and will be available in the next build).
  14. What Wacom device are you using? What OS are you on?
  15. Can you record another video for me, showing raster brush strokes in Designer and then brush strokes in Photoshop, using the same style brush, same size brush, and same document size please? I'm interested to know the performance difference, as on my machines, we're always faster.
  16. This should have been fixed in build 28 I think. What version are you on?
  17. Thanks, I'll have a read of those links. Needless to say, Google is incorrect.
  18. OK, then that is nothing to do with Affinity Designer, as we don't run any code at startup / logon etc. We only run code when you open the executable (clicking the shortcut, opening a file etc). I can only assume it's a coincidence that you installed Affinity Designer and started receiving these errors around the same time. I thought you were referring to a crash that occurred inside our application after you had run it.
  19. Yes, it should probably be added alongside the existing shortcut. Chrome and many other tabbed applications all recognise CTRL+W too.
×
×
  • Create New...

Important Information

Terms of Use | 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.