SpiffinJay
-
Posts
8 -
Joined
-
Last visited
Posts posted by SpiffinJay
-
-
V2 needs windows 10 build 2004 or newer no windows 7 support
-
You need to link it to C:\Users\<your user>\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe instead
replace <your user> with your windows user name in your case i see from the first image it is marcb so C:\Users\marcb\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe
I hope this helps you.
-
23 minutes ago, Corgi said:
I concur. I was about to purchase v2 and then discovered threads like these. I won't have anything to do with the Microsoft store or Windows Apps. Waiting to see if a regular .exe or .msi will become available.
I can tell you that many developers are starting to use MSIX even when Microsoft wont allow the installer to ask for a drive/location to install to because you need to change that for all new apps in windows settings which is stupid that microsoft did it this way but that way they can make sure you dont install the application to a directory (or multiple directories) where the windows "sandboxing" would break and cause security issues or worse you causing your whole user directory be sandboxed breaking the user account completely.
I dont like the MSIX format because its a Microsoft Store format and may break at any point due to changes Microsoft makes to windows or their store software so a "legacy exe/msi" would be great for installing in these cases and for installing to a different directory and for the Enterprise users with high security limits on their systems also offline activation would be great but i understand that it is a piracy prevention thing to have one time online activation (unlimited activations but only needed to be done once per install). (I will use the V2.0 software but i hate that i had to enable the dreaded windows store to install the software eww)
-
3 minutes ago, debraspicher said:
I still remember when I was bummed about Clip Studio Paint announcing sub plans for 2.0. This was around the time of the Serif survey that had the question about potential subscriptions. Celsys faced massive backlash over their 2.0 announcement. What ended up being announced was that their 2.0 upgrade for current users would be $20 said and done for 2.0. Feature updates in 2.x family after that point beyond maintenance fixes would be $10/YEAR. I thought OK that's not unreasonable, yes I hate subs, but that's something I can justify. 3.0 would eventually include those updates and be one-time as well. I see the meltdowns people are having here over the fact the pricing doesn't make them feel special enough and I can't help but feel embarrassed for them when we don't even have to worry about the slippery slope of a sub. It's also literally 6-7 extra programs for people who only bought v1 on one platform. They're literally throwing money away to fawn over their base and yet they're scamming users somehow? We can't have nice things, apparently.
People are overreacting.
Serif has always done it this way.
All non subscription software at one point did it this way.
The launch discount is the discount you get as a loyal customer and new customers get the same discount at the same time because they are new customers.
People seem to hate the idea that everyone gets the software at the same price but in reality this is good as more users mean more bugs are found and fixed and more of other creative software adds support for the affinity suite.
- NewInBoston, jmwellborn and PaulEC
-
3
-
48 minutes ago, adbosch said:
Does anybody have experience running the affinity suite on a Microsoft Surface Laptop Go 2 i5 / 8GB / 256GB? In theory there should be no problem, but how about in practice?
I have not used any surface devices but you can try with the trial version for 30 days and if the suite works on that device you can then buy the full license and activate the software there is no limits on the trial other than the 30 day limit.
-
4 minutes ago, Mark Ingram said:
Windows creates these aliases on our behalf, so I believe the issues are with the applications attempting to launch them. RawTherapee, for example, works fine with the aliases, along with many other applications that we tried.
that makes sense if they try to do something unexpected with the alias which they shouldnt do so propably their implementations are done in a non compliant way or they look at the alias and go directly to what is aliased which the sandboxing wont allow to be executed. just a hunch
-
22 minutes ago, Mark Ingram said:
We already have app execution aliases installed to:
C:\Users\<username>\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe
C:\Users\<username>\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe
C:\Users\<username>\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe
You can call those from the command line or from other applications.
Isnt there currently some sort of issues with those aliases. I hope you can fix those issues some people seem to be having with those aliases currently.

Problem to create a link to Affinity Photo 2 in XnView MP
in Affinity on Desktop Questions (macOS and Windows)
Posted
you could try the workaround by walt farrel posted here: