myclay

I do not know if the subject will come up in the search function, but this topic of 'road maps/feature plan' has been explained and discussed by the forum moderators 'ad nauseam'.  Why worry about v3 when v2 is currently being developed, improved and released?  Lets give the developers a break.

They won't expire - you can continue using them indefinitely. Of course, especially towards the start of a new beta, it comes with the warning that we may have introduced some instability or other issues to mean we wouldn't recommend you use it for important / production work. Have to say we've not had anything particularly nasty happen in this regard with recent betas, but can't guarantee it won't happen in future...

Hi All,
We have just made 2.2 live across all App Stores and our website. As always, the feedback we have received from you all during this beta has been an incredible help in both shaping the new features as well as squashing many bugs!
The build we have released is the same as RC3 (build 2005), meaning for the time being whether you use the latest beta version or switch to using the release version they are the same. If you anticipate taking part in the next beta you may wish to keep your current beta version installed, as this will be updated on auto update when a new beta is available. This will either be a 2.2 patch if we feel one is needed, or moving straight onto a 2.3 beta.
It would be impossible for us to do what we do without your support, and I just wanted to say a huge thanks for everything you have contributed to this release.
All the best,
Ash

Sadly, not at all.
Thank you for mentioning this, @v_kyr, what a shame you posted this into Feedback section instead of bug section though.
Also, severity of this bug is so serious that Serif should issue an update to the whole V1 line as well...
Honorable mention: @Patrick Connor

First I wanted to place it into the bug section, but then thought Ok it's usually not an Affinity own bug but instead more a Google third-party used library (libwebp) security hole (bug) which can lead to vulnerability attacks.
Also so far didn't recherched, if the yet new released Affinity v2.2 versions do include a more recent (fixed) libwebp version here or not (?). If not they should update that one accordingly!

It's fine being here. I have linked your request to the developer report, which is under consideration already.

I wonder if MSIX sandboxing helps here or not?

Apps: Publisher
Platforms: All
Previously Publisher only gave options to open document file types from File->Open. There have been a number of requests to extend this to allow image files to be opened in that dialog, especially for those who now directly edit images and other graphics work using studio link functionality in Publisher so this has now been added.

https://www.fastcompany.com/90906560/adobe-feels-so-confident-its-firefly-generative-ai-wont-breach-copyright-itll-cover-your-legal-bills
They just say to cover legal bills you might get when using their products or is there a newer article/statment out there?
 
 

And so it begins.
Adobes big marketing claims of "its all legally backed up" are turning to dust.
Question is; will Adobe honor its claims of legally compensating Artists they stole from and compensate them against Adobe?

I do, best are programs which have a UI scaling slider.
Sometimes the UI designs are vastly different and a catch all be all just can´t do justice on homogenizing the UI size throughout a multi program pipeline.
 

your interpretation of the book title is a textbook freudian slip and very fitting especially with Adobes legal/PR fiasco(s).
The correct title of that book is "Who Moved My Cheese?"

And so it begins.
Adobes big marketing claims of "its all legally backed up" are turning to dust.
Question is; will Adobe honor its claims of legally compensating Artists they stole from and compensate them against Adobe?

And so it begins.
Adobes big marketing claims of "its all legally backed up" are turning to dust.
Question is; will Adobe honor its claims of legally compensating Artists they stole from and compensate them against Adobe?

This wrapping stuff around with the help of AI looks interesting.

EDIT; not 100% useful when it needs to be accurate and or truthful to reality but for quickly modifying placeholder images it looks interesting.
 
 

And so it begins.
Adobes big marketing claims of "its all legally backed up" are turning to dust.
Question is; will Adobe honor its claims of legally compensating Artists they stole from and compensate them against Adobe?

https://www.fastcompany.com/90906560/adobe-feels-so-confident-its-firefly-generative-ai-wont-breach-copyright-itll-cover-your-legal-bills
They just say to cover legal bills you might get when using their products or is there a newer article/statment out there?
 
 

And so it begins.
Adobes big marketing claims of "its all legally backed up" are turning to dust.
Question is; will Adobe honor its claims of legally compensating Artists they stole from and compensate them against Adobe?

Assuming you purchased directly from Serif, there is a 14 day return period, so you can get a full refund. (There is also a 30 day trial period, so that people can check that the Affinity software does actually suit their needs before purchasing it.) 

A lot of software really don't support backwards compatibility, which is why people export to other formats instead and then re-import. I can only think of Blender that reliably supports backwards compatibility, but even there stuff break at some point. I heavily doubt that Serif will take the time to create backwards compatible file formats any time soon if at all when development is so focused on the future of the software.

That said, you can actually copy+paste objects from V2 to V1 and vice versa. As long as the feature exists there won't be any crashes going on. Done it a few times when noticing stuff breaking in some Betas and needed to use the retail versions.

This wrapping stuff around with the help of AI looks interesting.

EDIT; not 100% useful when it needs to be accurate and or truthful to reality but for quickly modifying placeholder images it looks interesting.
 
 

Yes, thanks - we have made all supported image file types be available from file-open in the 2.2 beta which is available now.
If you'd like to give it a go you can join our beta program here - be great to get your feedback.

Might be a task for some forensic checking.
https://29a.ch/photo-forensics/#error-level-analysis
Drag and drop the image into the site, its locally edited in your browser.

The sunlight colour seems convincing? The cows are a domestic cattle breed so if this was AI generated, at least some tiny amount of thought went in...
Anyhow if its true that its AI generated(need more convincing proof for that claim), AFP could still lose its entire reputation.

That quote was from the link you provided. 🙂

This wrapping stuff around with the help of AI looks interesting.

EDIT; not 100% useful when it needs to be accurate and or truthful to reality but for quickly modifying placeholder images it looks interesting.