Jump to content

maxsteenbergen

Members
 View Profile  See their activity

  • Content Count

    30

  • Joined

  • Last visited

Community Reputation

11 Neutral

See reputation activity

About maxsteenbergen

  • Rank
    Member

Recent Profile Visitors

377 profile views
  • MEB

    MEB

  1.    ModernGeek reacted to a post in a topic: Artboard export as SVG includes a <rect> named Artboard
  2.    ronnyb reacted to a post in a topic: Memory leaks and slow performance: zooming causes 1GB jump in RAM usage
  3. maxsteenbergen
    Using OpenGL instead of Metal and increasing the RAM usage Limit makes AD usable again.
  4. maxsteenbergen
    @ronnyb I have 16GB of RAM available. The 2GB is the graphics card’s memory, enough to adequately render some moderate 3D work. Besides, the 1.7 beta and earlier ran like a dream.
  5. maxsteenbergen
    You’d think 16GB for just AD and no other apps running would suffice....
  6. maxsteenbergen
    As mentioned here, I have a document with 115 artboards (all 99x99 icons) that gets very slow to work with. Specifically, I found the RAM usage to be fairly huge right from the start, with large jumps when opening and editing docs. Opening AD: 1.11 GB Opening the document: 1.8 GB Zooming in the document just 1 step: 2.5 GB Additionally, it seems like macOS's WindowServer process is affected as well, rising up to 1.2 GB. Affinity Designer 1.7.1 (MAS version) iMac (Retina 5K, 27-inch, Late 2014) 4 GHz Intel Core i7 16 GB 1600 MHz DDR3 AMD Radeon R9 M290X 2 GB
  7. maxsteenbergen started following File crashes AD on opening (again), Designer 1.7 fast & Responsive 1.7.1 sluggish and Shared brushes between AD & AP
  8. maxsteenbergen
    I'm finding 1.7.1 to be slow as heck too. I've got a document with 115 artboards (all 99x99 icons) and after a short while simply selecting and editing paths gets tedious. Also, it sends my fan flying. AD uses 1.05 GB of RAM immediately after startup, rising to 2.25GB after opening the document. Switching between Metal and OpenGL doesn't seem to make much of a difference. iMac (Retina 5K, 27-inch, Late 2014) 4 GHz Intel Core i7 16 GB 1600 MHz DDR3 AMD Radeon R9 M290X 2 GB
  9.    Leafdancing reacted to a post in a topic: Sneak peeks for 1.7
  10. maxsteenbergen
    I noticed Illustrator's Blend tool is one the Roadmap a well. Is that planned for 1.7 as well, and will it allow us to have gradients follow an arbitrary path?
  11. maxsteenbergen
    Is there a way for Affinity Designer and Affinity Photo to sync their brushes? Now I had to import one brush set to each application separately.
  12.    warente reacted to a post in a topic: Affinity Designer Customer Beta (1.6.1 - Beta 4)
  13.    ronnyb reacted to a post in a topic: Affinity Designer Customer Beta (1.6.1 - Beta 4)
  14.    MattP reacted to a post in a topic: Affinity Designer Customer Beta (1.6.1 - Beta 4)
  15.    A_B_C reacted to a post in a topic: Affinity Designer Customer Beta (1.6.1 - Beta 4)
  16.    Alfred reacted to a post in a topic: Affinity Designer Customer Beta (1.6.1 - Beta 4)
  17. maxsteenbergen
    NINJA EDIT: Just downloaded Beta 3 and that does open the file. Can the devs indicate what the problem was/is so we may avoid it for the time being?
  18. maxsteenbergen
    I have yet again a file that won't open anymore. I noticed some elements didn't align like they should, so I save the file, restarted AD and opened the file. Unfortunately, it immediately crashes. I've had this happen before when working with a fairly large bitmap embedded in the file (see the linked topic). This time around, even though there's a bitmap in the file, I wan't editing that layer specifically and it isn't all that large. @MEB Could you work your magic again and ask one of the devs to repair the attached file? I'd hate to start over. concept3.afdesign
  19. maxsteenbergen
    I'd say those chances are negligible. I run all my machines in the English localization, and the crash occurred after copy/pasting a rather large image embedded in the document.
  20. maxsteenbergen
    Hi Miguel, Thanks so much for the fixed file. Do you know what might have caused this?
  21. maxsteenbergen
    Not that it matters, but yes.
  22. maxsteenbergen
    Sorry to keep bugging, but I really need an answer on this. This is client work so having to stall any longer is not really an option.
  23. maxsteenbergen
    Any news on this?
  24. maxsteenbergen
    Hey MEB, I totally get that you're understaffed these weeks and that the file may not be recoverable, but just for my planning, are you talking hours, days or weeks?
×
×
  • 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.

  I accept