wrc04

Thank you Walt.farrell, that did the trick. You saved my bacon. I used your extra hints too and they were a big help and time saver. It use to take me forever to reinstall my assets. 

Thanks Walt. Worked great. I'll have to keep this written down somewhere for future use.

Before starting the application, press and hold the Ctrl key. Release it when you get the dialog. Note: on Windows, you may need to watch the Taskbar and click on the app icon there when it shows up (while still holding the Ctrl key).

You're welcome

You may need to do a Reset operation. I would try it this way:
Shutdown and restart your iPad. Start one Affinity V2 application. I suggest Publisher 2. Leave the others stopped. As the application starts, it will display a Splash Screen. With 1 finger, double-tap on the Splash Screen. This will give you a Clear User Data dialog. In that dialog, turn off the first option (Reset User Defaults), turn on the second option (Reset Assets), and turn on the 2nd from the end option (Reset Account Data (inc. Synced Content)). Press the Clear button. Open Account, select everything you want to install, and wait until it has finished downloading and installing. Then you can manually install your other Assets. Two more hints:
If you want to have your manually installed content in all 3 apps, there's a Preference, in General, to Link New Content Categories. Turn it on. Then you'll only have to install it once. If you tap the Publisher icon at the top left of the app's Home Screen, you'll find an Import Content action. This should allow you to select and import multiple .afassets files at one time (or any other kind of content, such as .afbrushes).

I had most of my assets installed on my iPad Designer V2, and Photo and Publisher. I accidentally installed one asset category twice so I attempted to delete the copy. I chose to delete on all apps. The app seemed to freeze or was taking a while so I closed Designer. When I reopened all my assets were gone. I have since tried to re-install my assets but they won’t install. When I go to my account panel to download the assets I purchased from the Affinity Store, they will download but when it tries to install I get a Red Circle with an ‘X’ in the middle every time. I tried deactivating and reactivating my device; I deleted and reinstalled all three apps, I rebooted my iPad…. Nothing works. I get the same red circle every time. Thank God my desktop still has all my assets installed but as of currently I can’t access any of my assets for any of the iPad apps. I have a third gen iPad Pro 12.9 and I have the latest OS update 16.1.1 installed as well. Not sure how else to approach this problem since reinstalling the apps doesn’t work or reactivating my account doesn’t work either. Thanks in advance for any suggestions or ideas.

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

That depends on what you want to do:
 
With Resample checked you will change the image pixel dimensions. That means adding or removing pixel to/from the image. This will decrease image quality no matter if you are enlarging or reducing the number of pixels in the image (although enlarging is more problematic).
 
With Resample unchecked, you can only change the physical dimensions of the image when printed without changing the image pixels (the pixels dimensions input fields are greyed out when you uncheck Resample). You can only change the dpi. Assuming that your image has 96 dpi, reducing this value to 72 dpi for example will increase the physical dimensions of the printed image because you are using less dots per inch and thus able to fill a bigger area; increasing it to 300 will decrease the size of the printed image because you are now using more dots per inch and thus only able to fill a smaller area. Note that the pixel image information has not changed in any way - you are simply printing it with different densities (placing the dots closer or farther from each other).
 
[EDITED] You can also change both image pixel dimensions and dpi at the same time for more flexibility when printing, but again since you are adding new pixels to the image you are again sacrificing image quality too as explained above.