Nox

Guys, seriously? What the hell? I can't watch this anymore. Here are extracted repo patches:
Wine-git_patches.tar.xz
Clone standard Wine mainline repository, apply patches (git am or git apply), build wine and proceed as usual. I myself have here wine 8.10 from Git working just fine. There is no need for:
Containers rum, bottles,idkwhatsandbox technically not even winetricks if you know how to install dotNET4.8 Keep it as simple and vanilla as possible. There is no trick. And preferably use you distribution method for creating binary packages (patches can be applied almost to anything) or simply follow Building Wine guide. Don't use containers.
My previous intention was to create binary packages for Ubuntu (and clones) but i just grew aggravated (by Ubuntu) more and more. I can't bear Ubuntu. Not anymore.
So, I decided to switch this task on Debian (I guess it's your lucky day). Right know I'm facing some issues and I don't have enough time, but my intention is to create packages for Debian and run Affinity and Wine on Debian. Wish me luck.

Since a few peoples were interested in a "guide" to get Affinity v2 working on Linux here it is,
Before asking for help or sending logs here try and troubleshoot issues yourself with WineHQ's documentation :
https://wiki.winehq.org/Wine_User's_Guide
https://wiki.winehq.org/Building_Wine
Before anything else I'd like to state that this does NOT deliver a stable nor 1:1 experience to what Windows10/11 will give you but i believe it to be an important step for Serif to witness Affinity's potential on the Linux ecosystem.
And that yes peoples like us, going to this hacky extent to get your products working on our OS of choice is meaningful so please consider your marketing impact if a native version were to exist.
An other note to Serif, Affinity's devs and managers :

I'm one of those engineers that you're insulting, and I'm also the only engineer to reply to the posts on this thread, trying to help out the community. My time is valuable, and I don't want to waste it reading comments like that.

We are pleased to announce an update for the Windows release of Affinity Photo 2, version 2.0.4
This build is available as a (sandboxed) MSIX application installer and as an (unsandboxed) MSI/EXE traditional installer.
Please see this FAQ thread for instructions on how to access the unsandboxed MSI/EXE version.
The changes in Affinity Photo 2 for Windows 2.0.4 (those made since the last release Affinity Photo 2 for Windows 2.0.3) are as follows:
Fixes & Improvements:  (since the last release 2.0.3)
Develop Persona: Enabling White Balance on non RAW files crashes Affinity Photo or was not functioning correctly. [AFP-5803] Fixed tint value in CR3 files[AFP-4617] Improved timezone handling in Metadata panel StudioLink incompatible with licensing used for businesses. Fixed non-ASCII characters not being accepted in license usernames Fix New Document sometimes showing Letter* instead of A4 Cannot set stroke width if units not set to points. [AFD-6276] Saving files may reduce file size in some circumstances (example was a 2gb file with no embedded data) Some image resources are being replaced by others from the same document when copy/paste was used to insert them. [AFB-7053] Assorted stability fixes Help and Localisation updates. Assorted other Licensing and Registration improvements To get notified when any new releases are made please follow the latest releases thread by clicking here
UPDATING TO THIS VERSION (which is free for all V2 users)
The software version can be seen on the splash screen and the About dialog (in Help > About Affinity Photo).
If you’ve purchased from the Affinity Store — each time you start the Affinity Store software it will check for updates and offer any available update. The latest update will install over the top of any earlier version, with no need to uninstall. 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, this new release (and previous versions of Affinity Photo for Windows) can be downloaded from this link. (that installer is NOT for Windows Store purchases and needs a product key).
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.

The Unsandboxed (MSI/EXE) Windows installs are now available to all. Sorry this took longer than we expected.
More information here
 

With the roll out of Affinity Designer/Photo/Publisher for Windows version 2.0.4, Serif are making available Unsandboxed installers (also known here as MSI/EXE installers). These installers will be made for all future V2 release builds going forward and will autoupdate from within the application (checking for updates on each run, like the sandboxed version does)
Serif do not recommend or support mixtures of MSIX and MSI on the same computer. You should only use either all sandboxed or all unsandboxed,  particularly if you have more than one Affinity V2 application installed.
You can now download (and install) Windows unsandboxed MSI/EXE installer files (as well as Windows sandboxed MSIX installer files) from these store pages.
1. From the  V2 Universal Download page
 

Click on the words "Looking for Windows MSI installers?"
 

2. Individual V2 application Download pages, found here
Affinity Designer 2
Affinity Photo 2
Affinity Publisher 2
Click on "Also available EXE (size MB)" 

3. LICENCES AND DOWNLOADS pages in your account
 

Click on the words "Looking for Windows MSI installers?"

Unsandboxed MSI Installers are now available for Version 2 on Windows as well as sandboxed MSIX ones
 

I have just posted about these installs here.
Please follow that thread for news of the release. 

Having purchased V2 not realising it was just msix installer only at this stage, was quite disappointed as we use a very specific version of 21H1 win10 not working with msix/appx, so the news of upcoming exe/msi release is the only that stopped us from refunding to be honest. Hopefully its coming very soon! sticking to V1 till then. Thanks for updates Serif.

The Affinity apps crash my AMD display driver a lot and very random. Most of the times they happen when I move/pan or zoom the view.
The screen where the App is running then will turn black, the system is still a little bit responsible (for example: media buttons still work) but not the display, the secondary display is frozen and it takes around half a minute for AMD to restore the graphics driver (I use the appearing crash report every time), in 99% of the cases the Affinity App has crashed too then. Sometimes (rarely) the graphic driver isn't able to restore itself, then I have to reset the PC, this will result in no crash reports on both sides.
It is more likely to happen when I have Live Effect layers in the document. But sometimes the driver also crashes when I edit vector curves or for example change letter kerning/tracking on Artistic text.
This problem is present in Affinity Photo, Affinity Designer, Affinity Publisher in Version 2 and 1.
Enabling or disabling OpenCL hardware acceleration also has no effect on this issue.
I have this issue for quite a while now and I've waited to report this issue for the OpenCL bug to be fixed, because I thought this might fix the issue. But no luck as it seems.
Just for clarification before the blame is put on AMD again: Adobe Products, DaVinci Resolve, Krita, Blender, Inkscape do not have any issues on my hardware nor did the graphics driver ever crash once while I was using these Apps. In fact Affinity Apps (and Valheim in Vulkan) are the only source of display driver crashes on my PC.
 
My PC configuration for reference:
CPU: AMD Ryzen 7 3700X
GPU: AMD Radeon RX 6800 XT (Driver: AMD Software: Adrenalin Edition Version 22.11.2)
RAM: 32GB @ 3200MHz
Display: 2x 1080p (144Hz + 72Hz)
OS: Windows 11 Version 22H2 (OS Build 22623.1020)
 
Crash Reports are attached
49f1e9ca-17cc-4679-931a-835f091b3c53.dmp attachment_Log.txt

Sounds amazing, thank you so much for listening to your community and customers!

There might be people interested in how to ignore a particular user. For anyone who is looking for a way to do it: click on your own profile, then Ignored Users and add the username of the member that you think is not and will not be contributing anything worthwhile.

The Affinity apps crash my AMD display driver a lot and very random. Most of the times they happen when I move/pan or zoom the view.
The screen where the App is running then will turn black, the system is still a little bit responsible (for example: media buttons still work) but not the display, the secondary display is frozen and it takes around half a minute for AMD to restore the graphics driver (I use the appearing crash report every time), in 99% of the cases the Affinity App has crashed too then. Sometimes (rarely) the graphic driver isn't able to restore itself, then I have to reset the PC, this will result in no crash reports on both sides.
It is more likely to happen when I have Live Effect layers in the document. But sometimes the driver also crashes when I edit vector curves or for example change letter kerning/tracking on Artistic text.
This problem is present in Affinity Photo, Affinity Designer, Affinity Publisher in Version 2 and 1.
Enabling or disabling OpenCL hardware acceleration also has no effect on this issue.
I have this issue for quite a while now and I've waited to report this issue for the OpenCL bug to be fixed, because I thought this might fix the issue. But no luck as it seems.
Just for clarification before the blame is put on AMD again: Adobe Products, DaVinci Resolve, Krita, Blender, Inkscape do not have any issues on my hardware nor did the graphics driver ever crash once while I was using these Apps. In fact Affinity Apps (and Valheim in Vulkan) are the only source of display driver crashes on my PC.
 
My PC configuration for reference:
CPU: AMD Ryzen 7 3700X
GPU: AMD Radeon RX 6800 XT (Driver: AMD Software: Adrenalin Edition Version 22.11.2)
RAM: 32GB @ 3200MHz
Display: 2x 1080p (144Hz + 72Hz)
OS: Windows 11 Version 22H2 (OS Build 22623.1020)
 
Crash Reports are attached
49f1e9ca-17cc-4679-931a-835f091b3c53.dmp attachment_Log.txt

Having a warning that the product hasn't been tested on the OS and will be unsupported is completely fine. But unless doing the installation would actually damage the system, please allow the installation to proceed, at the user's own risk.
The core problem with the software business is that once the product works well, it (with one exception) never really needs to be updated or upgraded. A company's revenue stream dries up unless it can innovate to a degree to prompt users to purchase the next version. Serif is still in the early stages of its products so they have nothing to worry about on that front, for a very long while.
But Microsoft is a different story, and that's where the exception lies: security. For the vast majority of users, the only reason to pay for a new version of Windows (or Microsoft Office) is security. If not for malware, I'd still be on Windows XP, and perfectly happy as long as companies like Serif produced applications that ran on XP.
Back to reality -- Microsoft forces OS changes down our throats (because of security), which forces developers to shift to the new OS, which prompts them to abandon support for older OSs for market reasons. Still, I try to cling to whatever works for as long as possible, and it's discouraging (if economically understandable) when Microsoft supports an OS for a longer time period than developers support their applications which run on top of it.
So if Serif doesn't have the capability of testing and supporting on older OSs, okay, whatever, but please don't preclude users from trying to make it work.

Just FYI, you don't need to post in a topic to follow it. Just click the Follow button at the top or bottom of the page (depending on the size of browser screen you have).

We clearly originally did not plan to distribute the MSI generically so there is quite a lot of testing & fixing required. We are likely to release MSI installers when we do the first patch, so hopefully before Christmas. At the moment some functionality like StudioLink and Edit in are non functional. Sorry this is far from straightforward given the way the applications share downloaded content and created assets/brushes.
We need to address these and anything else we find before MSI installers are made available more generally, or we will just be introducing more problems than it resolves.

To be honest, grab the discount now and be patient, its worth the wait and I believe Serif is gonna try to fix the issue asap. 
As Affinity v1 was supported +/- 8 years now, I am sure you wont regret and will have a longlasting grafic suite with a couple of years of updates and new functions. 
 
@Patrick Connoryou should work somehow on your announcing and communication to avoid mistakes or not offering what the users want in the future. What about periodically request some „user requests and feedbacks“ with multiple choice questions?

I really hope that it will be for the sake of many interested customers. I'll push hard for it

I agree, delivering the suite as "Windows Apps" and not normal ".exe"-applications is extremely customer and user unfriendly. Not even Adobe dared to take this tainted path.
It rips off all the control the user have about their PC and the programs and makes things unnecessarily complicated.
I'm very disappointed.

I'm not sure why you defend this behaviour, these are lame excuses. Of course it is a bit more work but that this will benefit the customer. The applications are self containing (apart from the user settings which are generated by the application itself), there is no cumbersome work to do to package them.
 
it is as simple as that. They already have the tools and infrastructure for creating their MSI/EXE-installers from Version 1.
Modifying this toolchain to work with V2 isn't an undoable task. Considering how much more customer and user friendly this approach is make the little bit of extra work worth to do.
I have a software development background myself and for my projects I take extra steps to make the user experience pleasant and convenient.
 
I don't want to attack you but I'm not sure if you are trolling, have no clue or think too complicated. I honestly don't know what you are talking about.
This was already part of Version 1. And from my experience fetching update information on the client side isn't complicated and serving the release info via an API (or even just a normal string) on the server is also not a big deal. The testing of these features maybe takes a few hours up to a day for one person.
 
They make a product and they want people to buy it, there is no defending in anti costumer practices because it's a little more comfy for the developers.
 

I agree, delivering the suite as "Windows Apps" and not normal ".exe"-applications is extremely customer and user unfriendly. Not even Adobe dared to take this tainted path.
It rips off all the control the user have about their PC and the programs and makes things unnecessarily complicated.
I'm very disappointed.

I'm not sure why you defend this behaviour, these are lame excuses. Of course it is a bit more work but that this will benefit the customer. The applications are self containing (apart from the user settings which are generated by the application itself), there is no cumbersome work to do to package them.
 
it is as simple as that. They already have the tools and infrastructure for creating their MSI/EXE-installers from Version 1.
Modifying this toolchain to work with V2 isn't an undoable task. Considering how much more customer and user friendly this approach is make the little bit of extra work worth to do.
I have a software development background myself and for my projects I take extra steps to make the user experience pleasant and convenient.
 
I don't want to attack you but I'm not sure if you are trolling, have no clue or think too complicated. I honestly don't know what you are talking about.
This was already part of Version 1. And from my experience fetching update information on the client side isn't complicated and serving the release info via an API (or even just a normal string) on the server is also not a big deal. The testing of these features maybe takes a few hours up to a day for one person.
 
They make a product and they want people to buy it, there is no defending in anti costumer practices because it's a little more comfy for the developers.
 

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

Sounds amazing, thank you so much for listening to your community and customers!

People who can download the MSIX for V2 (owners of a publisher 2 license on Windows or owners of a universal license) will be able to download and use the MSI instead. No extra cost over your V2 purchase