I think I'm probably on 2.6.3 because I don't reflexively update, and so many of the 2.x updates have had regressions.

2.6.x seems to have especially problematic, sadly.

Good to see you here, Matt. Thanks for joining my merry little band.

Is there some particular reason why you’re using 2.6.3 instead of 2.6.4, or was that a typo?

Thanks for providing it

I think I'm probably on 2.6.3 because I don't reflexively update, and so many of the 2.x updates have had regressions.

Can anyone who had upgraded to 2.6.5 still access their online account?

The update does not affect your access to your account, which is via the Affinity website, not via the software. I logged into my account only this morning and everything is still there as it should be.

Paolo

JAmedia wrote:

This says you can't create an account on affinity any more.   So whilst it fixes a few bugs (on macOS)  I am reluctant to install if if it cuts me off from my Affinity account.

It only says you can’t create a new account, it doesn’t say anything about being cut off from an existing one. If you don’t already have any Affinity software products or add-ons, the only reason to create an account would be to make purchases (which is clearly not an option at present).

Point taken,

Can anyone who had upgraded to 2.6.5 still access their online account?

I don't think I will install 2.6.5 until after the announcement tomorrow.  I have downloaded the updates anyway.  Paranoia has kept me alive, pretty and witty this far so... :-)

This says you can't create an account on affinity any more.   So whilst it fixes a few bugs (on macOS)  I am reluctant to install if if it cuts me off from my Affinity account.

It only says you can’t create a new account, it doesn’t say anything about being cut off from an existing one. If you don’t already have any Affinity software products or add-ons, the only reason to create an account would be to make purchases (which is clearly not an option at present).

Patrick Connor: This post covers most of the changes that are included in 2.6.5.
https://forum.affinity.serif.com/index. … nt-1410218

We have released a build to try and address a couple of issues found in 2.6.4 and also to make changes to stop the application offering any way to create an account or starting a trial or suggesting that the software can be bought at the end of the trial. Now that version 2.6 is no longer available to buy, the software has stopped offering any way purchase from within the trial.
The build also fixes a number of minor bugs including some for macOS Tahoe regarding regressions that are specific to that environment.

    [macOS Tahoe] Crash linking text frames [AF-8379]
    [macOS Tahoe] Crash placing PDF file in document [AF-7867]

------------------------------------
This says you can't create an account on affinity any more.   So whilst it fixes a few bugs (on macOS)  I am reluctant to install if if it cuts me off from my Affinity account.  Though, if the ditch the web site the update may be required so the program doesn't become unstable if it phones home to an unused number.

Very much hoping the numerous Publisher issues I encounter are fixed I still don't think Affinity have delivered a merchantable product, as of 2.6.3.

Good to see you here, Matt. Thanks for joining my merry little band.

Is there some particular reason why you’re using 2.6.3 instead of 2.6.4, or was that a typo?

If bugs have been fixed, then yes, of course, and I have updated (it's an update, not an upgrade - subtle difference).

Sorry (update not upgrade);
Thanks for the reply...

When I opened Affinity Photo, I saw that it's possible to update to version 2.6.5.
I also looked at Connor's post to see what fixes and improvements there are, but it doesn't mention anything specific; it only mentions minor bugs and a couple of fixes for MacOS Tahoe.

Based on this, I'm wondering, and asking you: do you think it's worth upgrading?
Thank you for your cooperation...

The 2.6.5 update is now available when you launch your Affinity apps. It's a bug-fix update (don't know if it's the last) for V2.

From this post to the Release Notes thread: