ℓurié

Hello all,
unfortunately I have bad news. In recent days I tested the latest release and the lag reappeared (even worse than before), but now it doesn't hit Curves, Shapes and Stroke (a very light latency is still there, but it doesn't impede the work). Now the massive lag affects the paragraph alignment (only Align Left, Centre and Right. With Justify is ok). I don't know if the previous release (1790) was affected, because I tested it less and after I deleted the files for reinstallation. Maybe yes, but it doesn't matter. What matters is realizing that the problem isn't fully resolved, because this delay makes the programs unusable. Now I don't know if it affects other elements, in the next days I will try again the whole Suite and I will update the topic if there will be news.

Alignment.mp4
Switching.mp4

Thanks all for the contribution. Unfortunately I don't have much time, but I tested the latest beta (1790) for about five hours. Maybe I'm dreaming, but the issue seems solved. The whole suite is more responsive and the lag disappeared. This is great news. Now I look forward to working with the 2.1.
Thank you so much, Serif. I really appreciate it.

Thanks all for the contribution. Unfortunately I don't have much time, but I tested the latest beta (1790) for about five hours. Maybe I'm dreaming, but the issue seems solved. The whole suite is more responsive and the lag disappeared. This is great news. Now I look forward to working with the 2.1.
Thank you so much, Serif. I really appreciate it.

Thanks all for the contribution. Unfortunately I don't have much time, but I tested the latest beta (1790) for about five hours. Maybe I'm dreaming, but the issue seems solved. The whole suite is more responsive and the lag disappeared. This is great news. Now I look forward to working with the 2.1.
Thank you so much, Serif. I really appreciate it.

Thank you Sam LaGargouille, this is exactly it. It can be extremely difficult to fix an issue that we cannot reproduce. There are a few threads regarding performance with maybe a dozen customers reporting the issue within them. The sheer amount of Windows configurations, as you say, can really hinder us diagnosing an issue.
Saying that, we have a release candidate that has hopefully made some improvements:
Please see Bugs affecting Windows > General performance improvements in the thread Ash linked to.

Hi All,
Another build has just been made available (2.1.0.1790) including a few more fixes. They are listed in the fix list thread here.
Nearly there!
Thanks,
Ash
 

I’m hoping we have fixed this in the next beta. Thanks all for the feedback and help. Much appreciated.

As you can see, I've experience with a massive lag with the whole Suite, especially with the selection/deselection of any shapes or curves. The lag starts after a short time with any file, and it extends to related tools (Shapes and Pen/Node), Stroke and File menu. The only way to stop it is to restart the apps every time. I used Photo for the videos (you can see them for more details) but the lag also affects Designer and Publisher. I have this lag with any update of V2, and now it also affects the Beta. None of that happens with the V1. It's been more than five months, and I can't work seriously with V2.
I'm really embittered.
 

Lag (Shapes & Curves).mp4 Lag (Stroke).mp4 Lag (Tools).mp4 LAG.afphoto

As you can see, I've experience with a massive lag with the whole Suite, especially with the selection/deselection of any shapes or curves. The lag starts after a short time with any file, and it extends to related tools (Shapes and Pen/Node), Stroke and File menu. The only way to stop it is to restart the apps every time. I used Photo for the videos (you can see them for more details) but the lag also affects Designer and Publisher. I have this lag with any update of V2, and now it also affects the Beta. None of that happens with the V1. It's been more than five months, and I can't work seriously with V2.
I'm really embittered.
 

Lag (Shapes & Curves).mp4 Lag (Stroke).mp4 Lag (Tools).mp4 LAG.afphoto

It seems to work fine in the 2.1 Beta. Excellent work Serif 👌.

Thank you too for your suggestion @SrPx. I tried this workaround and it works. But I noticed that this bug doesn't happen with any Arial text and it also happens with some non-Arial text. But now I'm testing the new Beta 2.1 and the bug seems to be fixed.

Yep, perhaps common issue with the booleans and shapebuilder. For the record, just tested that also works the trick of 'clipboard->copy as svg' activated in preferences, "paste special" as svg (it also treats "holes" as expected, after making such copy).

Workaround is to scale the document to 1 pixel wide, do the operation, then scale the document back to original size.
That should give the devs a clue.

Thanks @NathanC. I didn't notice any issue for now with the new Beta 2.1. Great job Serif 👌.

This is an issue currently logged with the developers, i've bumped the issue with your reports. 

Hello @nezumi,
thank you too for your reply.
It looks like the same bug. As I specified above it only happens when I press SHIFT for straight cut (vertical, horizontal, 45° degree). But in my case it only happens with fonts, even after converting them to curves (only with the straight letters it's ok). With the other shapes I haven't noticed any issue for now.
Look this video:

Correct Cut 2.mp4 Instead, with freehand mode it's ok with all shapes and all fonts.

We are pleased to announce version 1.10.6/7/8 updates for the Affinity Suite on all platforms.
Affinity Designer, Affinity Photo and Affinity Publisher (on macOS, Windows, and iOS) had all recently been affected by recent operating system releases such as the launch of macOS Ventura, iOS 16 and Windows 10 and 11 updates. We have mitigated some of these in the 1.10.6 patches of all applications on all platforms. The changes fix/avoid the problems introduced by operating system changes thus returning earlier functionality.
If you are using Windows 10 or 11, macOS Ventura (13.x) or iOS 16 then we recommend installing these updates. Other supported operating systems can install the update without issue, but they have no specific advantages/fixes over 1.10.5 for your OS.
If you are on macOS Sonoma, the  the 1.10.8 patch has a specific fix we would recommend you get
1.10.8 (on macOS only) is a single fix patch to address this Light UI issue on Sonoma UPDATING TO THIS VERSION (for existing V1 customers)
Updates on macOS for Affinity Store Purchases
The software version can be seen on the splash screen and the About dialog (in application menu, for example Affinity Photo > About...).
If you’ve purchased from the Affinity Store— each time you start the software it will check for updates and offer to download and install any available update, or in the application main menu there is an option Check for Updates. You can download the latest installer by logging into the affinity store here and find the order in your account and use the "download" button in there. 
Alternatively the full Affinity Store installers are also available here:
Affinity Photo on macOS: All Affinity Store builds of Affinity Photo for macOS can be downloaded from this link  Affinity Designer on macOS: All Affinity Store builds of Affinity Designer for macOS can be downloaded from this link Affinity Publisher on macOS: All Affinity Store builds of Affinity Publisher for macOS can be downloaded from this link  =========================================================================
Updates on macOS through the Mac App Store
The software version can be seen on the splash screen and the About dialog (in application menu for example, Affinity Photo > About...).
If you’ve purchased from the Mac App Store— updates are done automatically next time you run your software after it is available in the Mac App Store. If this does not happen for you, open the Mac App Store app and go to the Updates page and then Store > Reload page or press CMD+R. This should hopefully force the update to show. Apple sometimes phase roll outs around the world which can mean it may take up to 72 hours for your update to be available.
=========================================================================
Updates on Windows for Affinity Store Purchases
The software version can be seen on the splash screen and the About dialog (for example in Help > About...).
If you’ve purchased from the Affinity Store— each time you start the software it will check for updates and offer to download and install any available update, or in the application main menu there is an option Check for Updates. You can download the latest installer by logging into the affinity store here and find the order in your account and use the "download" button in there. 
Alternatively the full Affinity Store installers are also available here:
Affinity Photo on Windows: All Affinity Store builds of Affinity Photo for Windows can be downloaded from this link Affinity Designer on Windows: All previous builds of Affinity Designer for Windows can be downloaded from this link Affinity Publisher on Windows: All previous builds of Affinity Publisher for Windows can be downloaded from this link =========================================================================
Updates on Windows through the Microsoft Store
The software version can be seen on the splash screen and the About dialog (for example in Help > About...).
If you’ve purchased from the Microsoft Store— Microsoft Store updates are done automatically by the operating system (each time you start the application). If this does not happen for you, open the Windows Store app and click the three dots in the top right corner of the app and then go to Downloads and Updates. Click Get Updates. This should hopefully force the update to show.
=========================================================================
Updates on iPads
The software version can be seen on the corner of Preferences screen.
Your Affinity iPad apps should update automatically next time you run them. However, you do need to be logged in with the same Apple ID you used to buy them.
If the automatic update does not happen for you, go to the iPad App Store app and go to Updates. Once you’re there, tap near the top of the screen where it states 'Updates' and then hold, pull down and then release. This should manually refresh the updates page. However, don’t contact us if the updates are not available for you yet—Apple sometimes phase roll outs around the world and this can take up to 24 hours.
=========================================================================

Hello @Komatös,
thanks for your reply.
But in your video I can see the same bug. Look carefully and let's analyze it.
The first cut leaves behind some curves. It's the line outside the fonts. The left side of & isn't cut. You can check this with the Node tool (press CTRL+Y to see if you use Windows).

The second cut only works with the left side of B. The right side of B and & aren't cut, despite you have selected all three elements.

A correct cut is this:

Correct Cut.mp4 But I've noticed that it works correctly only with a straight fonts (A in the last video is totally straight). Instead, with the other shapes I haven't see any bugs for now.
Eventually sorry for my english and thanks for your attention.
 

Hi All,
Well, it’s been a pretty crazy week since the launch of V2!
This has been a real labour of love for us over the last year or so, and I can’t even begin to describe how hard the development team have worked on it. Not only getting the V2 apps launched, but also of course finally bringing Publisher to iPad. 
With this being our first paid-for upgrade there has understandably been a lot of feedback / questions around future updates and our pricing policies. I thought it was worth addressing / clarifying our position on some of these personally...
Updates to V2 moving forward
Buying V2 not only gets you all the new features you have seen, but we have various updates planned – including many more new features and improvements – which you will get for free. This will continue until such a time that V3 is released. We’re not sure exactly when V3 will be, but I can confirm we are not going to move to anything as regular as an annual upgrade cycle as has been speculated.
It’s worth saying too that V2 does include many under-the-hood changes to our underlying technology, and we have also been investing in several new areas of research recently. Some of these haven’t manifested themselves into new features yet, but overall V2 does give us a better platform to develop on moving forward and I’m sure you will be pleased with the updates V2 will receive.
Updates to V1 moving forward
While we did say on the FAQ that V1 would no longer receive any updates, I want to clarify that was about new feature updates. We will be updating V1 to fix any critical problems caused by operating system updates in the future. So if the next version of macOS breaks V1 we will endeavour to fix it. There will be a point in time when continuing to maintain V1 in this way will not be tenable, but certainly for the foreseeable future we will continue to patch. In fact, we have an update to V1 queued up for release very shortly with some fixes for Ventura and issues caused by a recent Windows security / quality update. 
We will update our FAQ shortly to make that clearer for everyone.
Offer period
In case you didn’t see, I’m pleased to confirm we have decided to run this initial launch offer until 14th December to give everyone the best chance possible to get it if they wish / have a decent amount of time to trial it. 
Upgrade pricing
It’s been really hard to see some of the comments about us not looking after our existing customers – we’re pretty devasted that anyone feels like that to be honest. But the fact is we felt our hands were tied somewhat with being able to offer upgrade pricing in a fair way. The main reason for this was App Store customers (which make up around 35% of our userbase). The problems with that are two-fold: firstly, we didn’t have a way from within V1 to validate an App Store purchase receipt to reliably ensure customers who were entitled to an upgrade could get one; and secondly, we could not find a good way for people to get that discount via the App Store. Us pushing upgrade customers to go exclusively via our own site (including customers who were previously acquired via the app stores) may also have put us in violation of App Store Ts & Cs which we were obviously concerned about.
I’m not saying that these issues were completely insurmountable, but any solutions we came up with would be messy, and most importantly could have resulted in some bona fide V1 customers struggling to get validated and claim their discount. We certainly don’t have the support resource here if we ended up needing to manually validate tens of thousands of receipts for example.
The only option we felt was safe to move forward with was a general launch offer, which would guarantee that every V1 customer could get the discount, whether they purchased directly through us or the App Stores. We knew a side effect of that would mean some new customers would end up receiving that same discount – but we felt that was a better option than V1 customers missing out. It’s also worth saying that while there has been some good press about V2, all our main marketing has been via email and through social media to our followers. In other words, we felt ok about it because we knew the vast majority of people who would find out about it or take advantage of the offer would be existing customers. I would be surprised if over the offer period customers upgrading from V1 didn’t make up more than 90% of our sales.
Overall I do believe us giving a 40% discount, along with the addition of the new Universal Licence of course, is offering fantastic value for money for those who want to upgrade. 
However, taking on board some of the feedback there is something extra we can do – we will offer a new free bundle of content exclusively for V1 customers upgrading to V2 as an extra thank you for your support. I’ve seen this suggested by a number of customers and it’s a great idea as it does remove the App Store conflict entirely. 
We’ll need a little time to put something together, but all customers who previously registered or purchased V1 and have since upgraded to V2 will receive a voucher code for this via email as soon as we can.
A comment on no subscription
I do want to say that some of the points above are exactly the reason why software companies move to subscription. Whatever you do with upgrade pricing, you still have the issue of customers who bought the previous version 3 months ago vs. those who have had it 2+ years. Offering perpetual licences also gives the additional overhead of needing to maintain the previous version longer than you would if everyone was on subscription / generally always on the latest version.
We are a small team so some of these complications are not ideal — all we really want to do is focus on developing our latest codebase, push out regular updates and continue with our mission to make great creative software accessible to everyone. 
But it does need to be funded somehow. We know you love our no-subscription model, but there also needs to be a level of appreciation that the alternative is having paid-for upgrades from time to time. That unfortunately comes with its own problems.
All of that said, I have to say we have been blown away with the response to V2 - around 3 times as many people have upgraded in the last week than we expected - and we really can't thank you enough for the support you have shown. More than anything the success of this upgrade puts us in a great place to continue investing heavily in development which is ultimately what it's all about, and we’re super excited to crack on with some great updates coming next year!
All the best,
Ash
This is a duplicate post of a thread that is now locked and moved to the questions forum

Hi @ℓurié
We are aware of this issue and I've passed over your example to the devs to help with their investigation.
@Patrick B We've currently only been able to replicate this issue on Windows, could you provide a screen recording of this issue in action on your mac so we can try to recreate it? 

I am using an M1 iMac running macOS 11, and I'm able to replicate the problem on my end. As has been said, the bug seems to only occur when cutting a straight line (holding Shift) across curved paths, seemingly at specific areas. This only happens on curves that were converted from fonts, but not every font and not every glyph has this problem. Hope this gets fixed.

I've had the same issue. So far I've only found it with text -- it doesn't happen with shapes, however complex. (As far as I've been able to find out.)

It works well with Inter:


Best regards!

Hello @Komatös,
thanks for your reply.
But in your video I can see the same bug. Look carefully and let's analyze it.
The first cut leaves behind some curves. It's the line outside the fonts. The left side of & isn't cut. You can check this with the Node tool (press CTRL+Y to see if you use Windows).

The second cut only works with the left side of B. The right side of B and & aren't cut, despite you have selected all three elements.

A correct cut is this:

Correct Cut.mp4 But I've noticed that it works correctly only with a straight fonts (A in the last video is totally straight). Instead, with the other shapes I haven't see any bugs for now.
Eventually sorry for my english and thanks for your attention.
 

Hello,
I've found a bug. The Knife tool doesn't work correctly with fonts, even after converting them to curves. As also reported by another user, the bug only happens when I use Shift for straight line. With freehand mode it's ok.
With the other shapes I haven't noticed any problems for now.
Thanks for your attention.

Knife Bug 1.mp4 Knife Bug 2.mp4 Knife Bug 3.mp4 Knife Bug 1.afdesign Knife Bug 2.afdesign Knife Bug 3.afdesign