TonyB

If you can send us a file that shows the problem then we will be able to fix it. We need the file in 1.6 format so we can compare. If you have something that takes 5 seconds to move an object then that would be ideal.

The website should be working again now. Sorry for an inconvenience.

Unfortunately converting Mac AppStore sales into external store sales is against Apple rules and we would be thrown off the Mac AppStore if we did it. Sketch did let you convert and hence they came off the App Store.

Your best bet is to use the 1.7 beta.

I have put it on the official list. Cheers, TonyB.

This will be a graphics card related issue. Can you post your MacBook Pro specs and what version of macOS you are running please.

The betas of Designer and Photo 1.7 updates should start in a couple of weeks.

We have confirmed that switching off "Parallel Processing" will workaround your batch issues on Mojave. We should hopefully have a beta of 1.7 available soon.

Earlio, did you try switching off "Parallel Processing" in the batch panel?

To be fair to Apple they are usually better than Microsoft as they break our Apps regularly. Fixing up applications after OS updates with workarounds is something we all in the industry except and companies that charge for updates also make a lot of money from it. We don't charge for updates or support and I hope we don't need to. On the Windows store we get 1 star reviews for the store not working correctly and that is completely out of our control and causes us great pain. As for your ongoing batch problems then please try adding the Global permission as I still can't reproduce the problem here.

Earlio, one simple thing to try with batch convert is to rule out any permissions problems that may be new to Mojave. If you could go to preferences->Photoshop Plugins and click the Authorise Global and pick the drive you have you files on then that would be a good test. Giving permission for Plugins also gives Affinity general access for opening files for other operations.

We found about about the Metal bug when they released iOS 12 as it has the same bug. We did issue a patch for that as there isn't a workaround as you can't switch Metal off. We were hoping Apple would fix the issue before Mojave shipped just like they do with many other bugs/issues that get introduced in a new OS. As we had a simple workaround for Mojave we thought that would work around the bug and also release 1.7 with many other fixes as soon as we can. It takes so much time for us to release an update and didn't want to push 1.7 even further away because of it. A beta of 1.7 is only few weeks away so you could enable Metal when that comes out. I'm sorry about your batch problem but I haven't received any information from our QA department about it yet but hopefully we can find a solution when we get more information.

The same valid Metal kernel compiled fine before Mojave but doesn't with Mojave. We can work around the bug by rewriting the Metal kernel but that won't ship until Affinity 1.7. You can workaround the problem by switching Metal Compute off. Assuming you have switched Metal compute off and restated the App then any issues you are having with batch will not be related. Can anyone else replicate your batch issues?

This is due to a bug in the Apple LLVM GPU compiler shipped with Mojave. There is a code workaround so it's very unlikely they will fix it.

Hyperlinks are on our internal roadmap, unfortunately like most of the other great suggestions we just don't have a date for when it will be implemented.