We are live, and thank you!!!

[78deluxe]

6 hours ago, Grunt said:

Is there any roadmap/feature plan for what is planned next or when will be Affinity Suite v3 released? Is there even any future plan?

if you want to give Serif more money I'm sure you can buy a few extra licenses and hand them out as gifts, or put them in a drawer as un-used.  As for me, I'm hoping we see years worth of updates on the v2 platform we all just paid for after the upgrade from v1.  

The competition made some revolutionary changes in their products in the last year, and AI is taking hold on virtually all other platforms than Affinity (and Capture One)  so I'm expecting Serif to continue the update path to remain relevant as the price went up substantially over time.  

[StuartRc]

Many thanks for the new 2.2 update. A very impressive and extensive bug fixture list combined with some new fantastic features.. and undoubtedly a lot of work!
I really like the new 'Object Creation Data Entry' and 'Move Data Entry' ...features 
I for one really appreciate what you have achieved and will achieve in future updates...keep it up! 

 

[Capitaine Pongo]

Thank you for your state of mind which is so pleasant in the world of software. We really have the impression that users are being listened to and working with you. Attached is my first creation with designer and "El Malo" add on.

[debraspicher]

28 minutes ago, tzvi20 said:

Hi @Ash In how many weeks will 2.3 start in? Really looking forward to a blend tool.🙂

I wonder if they will call it something else

[debraspicher]

3 minutes ago, tzvi20 said:

what do you mean?

 I was referring to the Blend functionality.

[v_kyr]

15 hours ago, tzvi20 said:

In how many weeks will 2.3 start in? Really looking forward to a blend tool.

Don't put unnecessary & indirect time pressure on the dev team, the latest releases again introduced a bunch of new bugs & issues (...not to name old so far still unfixed things, which can also trigger unwanted side effects for new features), which IMO would be more essiential to fix first at all, in order to get overall more stable and well behaving apps. - Also AFAI can see, somehow the software quality assurance has overall deteriorated since the beginning of the version 2 cycle. As many bugs & issues here are only discovered/detected after the major releases and not during the beta test phases. - Looks like we (the community) also have to do a better assistent job in testing the Affinity apps more carefully.

Otherwise, to also express some praise for the Serif Affinity team here, I know how difficult and time-consuming it can be to work on large and complex software projects and then always have to react promptly to new, constant OS substructures and all other influential software changes around. Add to that all the internal administrative work... etc. So keep on rolling, it can only get better and don't let yourself get too much stressed and burn out.

[Grunt]

On 9/21/2023 at 8:07 PM, BobMoyer said:

Why worry about v3 when v2 is currently being developed, improved and released?  Lets give the developers a break.

It is a normal thing to draw when you're developing anything. I'm used to it from OSS development. Sorry if I asked for something secretive. That didn't occur to me.

[v_kyr]

28 minutes ago, anto said:

Part of the reason I disagree with you is that some of the issues I reported early on were ignored, and after the release, users started writing about them as well.
It turns out that it is better: to fix the errors, or to rush the release and face criticism, because if the errors that were found by, say, 100 beta testers are not fixed, what will be said when the program will start to be used by millions of users. Of course, the quality will deteriorate, and hundreds of new ones will be added to these errors.

(Re)read what I wrote and reinterpret it again in a more general fashion and of course you can expand/include what I've said above about unfixed errors/issues back to v1 times here. - Which BTW is something a bunch of people (including me) had already often said long time ago, during early v1 times and even before you participated in this forum. - As a result, I personally see something like this (fixing errors first) as a general matter of course.

[PaulEC]

19 hours ago, debraspicher said:

 I was referring to the Blend functionality.

I think there’s a very good chance, as they seem to prefer using different names to equivalent tools and functions used in Adobe!

[v_kyr]

2 hours ago, anto said:

I meant that even the bugs that were discovered during beta testing were not fixed.

Sadly! - I can only guess/assume here that the team wanted to throw out a release, as it was somehow under time pressure since some people here in the forum are always pushing for new releases and features. The consequences and effects of this pushing are currently apparent. - I can only advise users to be a little bit more patient in general while waiting for new releases and so giving the dev team overall more time, because the more essential bugs are fixed beforehand, the more stable and usable the applications will generally be.

[Puck]

Thanks a lot! Great job!  

[PaulEC]

14 hours ago, v_kyr said:

some people here in the forum are always pushing for new releases and features.

I fully agree! I've never understood the mania that some people have for getting endless updates, as fast as possible, whether they are ready or not –  "Never mind the quality, feel the width!"

[Old Bruce]

On 9/24/2023 at 2:07 AM, PaulEC said:

... I've never understood the mania that some people have for getting endless updates, as fast as possible, whether they are ready or not ...

Back in the day it was "If it compiles; Ship it!"

[HCl]

.

[HCl]

.

[v_kyr]

1 hour ago, Return said:

Maybe because what get's released is so underwhelming and decades behind compared to other software and not thoroughly tested by real users.
That's why it is never going to be what those users expected and that's why they are pushing.

Maybe, but then those users wouldn't be always so exicited afterwards about every new released version and also express more their displeasure in apps behavior, instead of asking after the next release date with coming new features.

1 hour ago, Return said:

Don't come with that same ...

It's more a matter of good testing & bug tracking, bug prioritization and the overall handling/organization of error processing and bug fixing.

[HCl]

.

[debraspicher]

I can list a few bugs that still impact my machine. In my case, it means running my DPI scaling lower on my primary monitor which means that across my system I have to deal with text/UI being smaller. (I have a larger screen on a monitor arm and good enough eyes, but it's not a tenable solution for some).

I raised my DPI back up to 150% and immediately checking pixel mode, I get this. One of the bugs I have reported and since forgotten about:



Pixel/Retena Mode scales incorrectly when Windows 10 DPI scaling >= 150%:

Garbled behavior Zoom Levels 201% ~ 399% in Pixel Mode:

Oh, and Coverage Map is still broken:

[iuli]

Very late to the party as I had limited internet and couldn’t install anything substantial for weeks. Congrats for the public release.

[HCl]

.

[v_kyr]

On 9/26/2023 at 1:30 AM, Return said:

And they aren't.

What happened between beta 2005 and the release version that went so wrong?

icc issues,shortcut issues,ui issues,text box issues just to name few.

If they can't get a few shortcuts in the code, how are they ever going to find a bug

This sounds like those things worked in the beta version, but then no longer worked in the final build, which I somehow doubt as the latest release version is AFAI can see based on that version. Though of course I don't know how their build processes are overall setup & organized, so if they use something like Jenkins etc. in order to build betas & releases.

[HCl]

.

[v_kyr]

1 hour ago, anto said:

Why not make the patching process more flexible? Every 2-3 days, for example, instead of weeks, they don't need to be tested.

Adding periodically patches (...and I mean just smaller patches and not always a whole build here) might be a way to try out, especially for getting rid of some important & essiential bugs quickly. But testing before what you distribute to the world is always essential too here!

Edited September 27, 2023 by v_kyr

[HCl]

.

[v_kyr]

6 minutes ago, Return said:

If you put it out there it would surface right away.

Where to the public aka world? - Sure, but then you would also risk to maybe distribute patches, which might make an app completely unusable, for those who use them business wise. Though such real world test usage scenarios on the other hand, of course would very quickly show up any possible app problems then.