Jump to content
You must now use your email address to sign in [click for more info] ×

Matterdor

Members
  • Posts

    13
  • Joined

Posts posted by Matterdor

  1. On 11/28/2022 at 10:00 AM, walt.farrell said:

    The Affinity Suite has never provided backward compatibility. Even in V1,

    • 1.8 could not open files saved by 1.9
    • 1.7 could not open files saved by 1.8
    • 1.6 could not open files saved by 1.7
    • etc.

    V2 simply carries on that behavior, and 1.x cannot open 2.x files.

    I just got bitten by this while testing and I am only a casual user. I have bought one V2 upgrade while I wait for the full installer. My wife has V1 on her computer. I fixed up a photo and sent the file to her and she can't open it.

    V1 version upgrades are a very different situation compared to V1 to V2. Anyone sharing files has to make sure they are all on the same version. With V1 and the generous upgrade model, that wasn't an issue because people could just tell the other person to upgrade to the latest version. Now that upgrade involves a payment.

  2. 12 minutes ago, Dangerous said:

    I can't understand why people are so against it as an app.

    You don't understand because everyone is different. For example, I have different drives and different folders on my system. I have all of my general utilities under D:\Tools and my development tools under D:\DevTools. I have general purpose software in C:\GeneralApps. This helps me with backups and management of the stuff that I work with. It's easy for me to configure the various applications when I need them to integrate with each other. It's the way that I am comfortable working and fits in my workflow and processes. Affinity is the first serious application that insists on being a Windows App. Can I work around it? Sure, and I have, but that's not the point. You aren't seeing something as a problem for you and are extrapolating that onto everyone else. Sure, it's possible to work around these issues but people shouldn't need to.

    For me, I really appreciate what Serif has done by providing a very good non-subscription alternative to Adobe. I also appreciate their extremely fair upgrade policy. I have no problem paying for an upgrade. I am going to get 1 license of V2 to support them and hold off on the other 3 until I see what happens with the installations.

  3. 4 hours ago, Mark Ingram said:

    This is a common statistic from Microsoft across all MSI installations. This is just one of many reasons why Microsoft want application developers to migrate to MSIX.

    I understand your desire to move to MSIX for the reasons you listed but would you consider a MSI under "advanced downloads" for people who want more control over their installations.

  4. 1 hour ago, myclay said:

    I just wanted to make sure that you (a fresh account with no name (yet) to it) are not trying to steal my and other peoples bank data.

    Using an EXE file would be a big risk even if the account was an old one with plenty of posts and a name. There is no guarantee that the person who build the EXE file didn't have a virus on their computer. Software from Serif is different because they have a build and signing process and we are already trusting that process by running their software.

  5. 49 minutes ago, s.auler said:

    The msix install files are digitally signed, so you can be sure that they come from serif and aren't manipulated by anyone. That's a major security advantage.

    That is the case with the V1 installations too. No reputable software developer should be releasing unsigned installations.

  6. 4 hours ago, myclay said:

    I narrowed the issue down a bit, I got it working via : renaming the msix to zip, unzipping it and using the path to that unzipped exe.

    As long as the properly installed and original msix Version is open and running, The I/O  will go now straight to the msix program.
    3DCoat will now sent the files as it did before in V1 now with V2.

    Thanks. This got me working in a way that I can test properly. Note, you don't need to run the original one for this to work.

  7. For anyone battling to get this working. You can find the real location of the exe file by starting Affinity Photo and then going to task manager. If you right click on "Affinity Photo" in the task manage and choose "Properties", a dialog window will pop up that gives the exe file location next to the "Location:" text. This should work with the other applications too. You may need permission to access this folder but in my case, it worked without any permission changes.

  8. Add me to the list of people not happy with this change. I have 4 licenses and was about to purchase the new version when I noticed this change. I have put my purchase on hold. I don't like the App Store system as I store my applications in different folders based on their purpose. Please give us a regular installation.

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.