Jump to content


  • Content count

  • Joined

  • Last visited

  1. I've moved over to my Mac for the time being as the performance on Windows isn't really up to scratch just yet. Is the dev team aware of the performance differences between platforms?
  2. Ok, tried the renderer settings as follows: Radeon RX Vega M GL (Default): Sluggish with tearing Intel HD Graphics 630: Sluggish with tearing Warp: Worst rendering - almost unusable All video drivers are up-to-date, the OS is the latest Windows 10 May 2019 update. Setup in Radeon control panel to use high-performance (the setting makes no difference to Designer anyway its set).
  3. Hi all, I use Designer on both Mac and PC and have just updated both to 1.7. My Mac is: 2012 Retina Macbook Pro i7 2.6ghz, 16gb RAM, nVidia 650M (2gb) and 700gb built-in SSD - currently running 10.14.5 My PC is: 2019 Dell XPS 15 9575, i7 8705G, 4k display, 16gb RAM, Radeon Vega GL M (4gb) and 512gb built-in SSD - currently running Windows 10 May 2019 update Both apps start-up very quickly - quicker than the previous version. Here's where its weird. You know how Inkscape generally isn't optimised and you get that slow object / screen-tearing when moving objects etc? That's exactly what's happening on the Windows version. On the ancient Macbook Pro, it's silky smooth. I understand the fundamental differences between the low level GPU access (DX vs Metal) but I was wondering if Serif were taking steps to try to match the performance between these two platforms? At this rate, a seven year old laptop wastes a brand new Kaby Lake monster Dell!
  4. eighteentee


    Is there a technical reason for this? It seems quite a narrow selection of graphics cards to work with...
  5. Hi all, A quick question... I'm running Affinity Designer & Affinity Photo on a Mac Pro 2010 with nVidia Quadro 4000 2gb GFX card on High Sierra 10.13.2 and cannot seem to get the 'metal' option under Performance to work - it's greyed-out. I've checked System Profiler and the report states Metal is supported. Interestingly, it works fine on my Macbook Pro Retina 15in (2012). Is this a bug?