Patrick Connor

Once purchased and registered/licensed. Affinity V2 applications can be used indefinitely offline

I think this may be the "reason" yours is checking much more than any of the forum regulars here. I understand that Affinity V2 software will check to see what the functionality should be and I suspect that it is trying to see if you have registered a universal license (via another application) since the last time it checked (for functions in the menu like "Edit in Photo" or StudioLink. Our Privacy Policy explains We only transmit anonymous data outside of the My Account feature (clearly My Account needs to know who you are). The licensing data is kept to facilitate the software functionality, and communicated anonymously using tokens. You have to sign it to use the 30 day trial, so if my suspicions are correct, I think we would just have to not keep checking while the application is running (checking repeatedly in case the licensing position has changed during the time you are using the software). Many users have benefitted from the applications checking for the registration of a V2 Universal license in your account in a different application or on another device, and I think it is checked repeatedly/dynamically during software use. However I think this makes the software look like it it checking too often so I will bring this up with the developers in case it can be improved (called less).

Welcome to the Serif Affinity forums No, as R C-R said, you may install it without deactivating the license on the first computer

Text From Google Lens

@Andy L Welcome to the Serif Affinity forums Sorry for the delayed reply. Did you ever get your licensing sorted?

@Andrew Carter Did you ever solve your problem and get the Affinity V2 software started?

https://affinity.help now has all the other languages on iPad. The language selection is made in the bottom left area of the screen. These translations of the English help will be included in the next update. Sorry for the initial delay.

@ashf I have spoken to the developers about this and we think it will be possible to add both WebP and JPEG XL into the Export Persona on iPad to match Desktop, as well as being available in Export (already) . This is unlikely to be in 2.0.3 whose fixes are reasonably settled, but it is likely to appear in a subsequent 2.x update on iPad

Your 2 purchases in late May do not qualify you for further discount, sorry, but you could try emailing AffinityOrders@serif.com and seeing if they are feeling generous. This is not an appropriate way to post here

Yes, sorry this is not a release candidate and the translations are, as you say, incomplete

@Pyanepsion Thank you Je suis vraiment désolé. Ce n'est vraiment pas assez bon @Pauls please make a report

@Zero1 Please can you report problems using the beta builds in new threads (in this forum if they are newly broken in the beta), or this announcement will quickly get confusing, thank you

@Zen22 Your reply was deleted because it didn't substantially respond to the OP's issues in a nice manner. Your post breaks a number of the forum guidelines. You are welcome to express how you feel, which was overall positive about the MSIX installs, but you are not welcome to say what you think of others expressing their opinions, particularly not using the language you did.

Although this post feels a little passive/aggressive, it is good advice to anyone here finding the trolling of threads to be a problem to them, and I approve this method of ignoring anyone you wish (who is not staff who cannot be ignored) . We rarely mute accounts because they are customers and we should listen, but individually each of you can do that if you wish.

We are pleased to announce Affinity Designer for iPad and Affinity Photo for iPad are now updated to version 1.10.7 (for all existing customers). Here are links to the release notes Affinity Designer 1.10.7 for iOS ( Apple iPad Store ) Affinity Photo 1.10.7 for iOS ( Apple iPad Store ) Please follow this thread here to get notified when any new releases are made

Affinity Photo in iOS and Affinity Designer on iOS have had an additional minor update from 1.10.6 to 1.10.7 because the "My Account" option was non-functional in many locales, which has now been resolved. 09/12/22 Note: Affinity Designer for iPad displays this 1.10.7 build as 1.10.24 and Affinity Photo for iPad displays this 1.10.7 build as 1.10.7.317

The only way to present them in these forums is one thread per problem, anything else doesn't work.

@JürgenHeise Your post is not beta specific so has been moved

Well now I feel awful.... probably rightly so. We have built up to this release for soooo long and tried to have all bases covered about the launch. In so many meetings I would say things like "don't forget our forum regulars, they are doing an enormous amount of work on our behalf. We must think about the information that they have and how any changes to our processes will be perceived, and understood". I am extremely aware of how much time and effort are given "for free" by those who come here week in and week out just to share information and help others. We could not do any of this without them/you and these forums would not work without customer participation. .......and now to have it (correctly) pointed out that we haven't really said that out loud really struck home. We in no way take you for granted, and my comment above was really just trying to calm things down in every thread like this, rather than criticizing those participating in this specific one, and I likely failed to say enough about how everything else done by the regulars is very much appreciated. This thread is really not the place for that (not completely sure where is), but I wanted to respond to your post with a mea culpa.

They are not yet supported, no. Only footnotes imported from Word files have been implemented so far. The purpose of 2.0.3 is to fix a number of issues affecting the 2.0.0 release. New features and improvements will come in future more major releases like 2.1, 2.2 etc , and I hope for your sake this is one of those

Sorry but no, the betas are for licensed customers, not trial users

All the Ventura fixes in 1.10.6 macOS builds are in the new 2.0.3 macOS betas and the Windows and iPad 1.10.6 fixes were already in 2.0.0 releases

I am not involved in pricing decisions, but as a Serif representative I thought it went without saying that that my Serif badge means collective responsibility, so I agree, and I have edited my post. Also it was to underline that the previous responses in the thread were not from Serif

That is not completely fair. AMD drivers were terrible and buggy. They were 50 times slower than other manufacturers so we blocked you being able to turn it on for AMD in Windows V1 because it had already led to lots of support contacts complaining about the performance. Since about May '22 the AMD drivers have been improved and are now only about 3 times slower than other makers. Consequently during the internal V2 early beta we re-allowed AMD chips to have hardware acceleration on and made further changes to the code accordingly. So although it appears as though we could technically now "allow" AMD to turn on hardware acceleration in a Version 1 patch, it is not that straightforward. Other changes made during the the V2 development cycle have also facilitated AMD drivers, and it is not a simple matter to port any of those back into the V1 codebase. The recent patch for critical OS issues is the only change we can make given our resources here. As it happens there are lots of "fixes" in 2.0 that were a problem in 1.10 but we are trying hard not to sell the software based on those so much as the many improvements and new features that you get. I think it is better that some things got fixed as well as the improvements and new features, than that 2.0 would have all the same restrictions as 1.10.x So yes if this was the ONLY change in 2.0 over 1.10 I would agree we had put this "behind a paywall" but it is not how I would describe the development cycle where things change over time and occasionally we will ask for more money. tldr; New AMD drivers mean that enabling AMD in 1.10 might now work better, but would likely lead to unforseen problems making it still unusable.

I have decided to hide most of the posts above attempting to justify Serif's position, and do not expect those users to post them again. Please concentrate on supporting customers with the software use and NOT with marketing feedback