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

bildbaendiger

Members
  • Posts

    16
  • Joined

  • Last visited

Posts posted by bildbaendiger

  1. 58 minutes ago, Mark Ingram said:

    I've mentioned elsewhere that we use "App Execution Alias" to enable this scenario. You can find the aliases in the following location:

    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

    Please replace username with your Windows username. Also, those paths are already in your %PATH% variable so you can launch them without even specifying the full path, e.g. AffinityPhoto2.exe.

    @Mark Ingram

    These "App Execution Alias" do not work for many. They get the error message: "The system cannot access this file." It seems like it's a Windows permission issue.

    The following workaround from Camera Bits was the first one that worked for me:

    Forum Camera Bits

    You bypass the problem with the permissions via a shortcut of the running program.

    Maybe this will help others as well.

    Thomas

     

  2. 44 minutes ago, Mark Ingram said:

    For anyone that would like to work around issues with launching our apps from third-party applications (e.g. DxO, ACDSee, etc), I have written a launcher utility that you can place anywhere on your system, and it will take care of calling our apps, with any required arguments.

    Usage: aflaunch -a name -b build [args]
    
    -a name    : One of the following
        Designer2
        Photo2 [Default]
        Publisher2
    
    -b build   : One of the following
        Retail [Default]
        Beta
        MSStore
    
    args       : [Optional] All remaining arguments to be passed onto the target application (must be last)

     

    The -a and -b arguments are optional, so you can ignore them unless you want to launch a different app, or the beta or MS Store versions.

    I have signed the exe as well, so it will have a valid digital signature.

    Please let me know how you get on with this.

    aflaunch.zip 9.56 kB · 2 downloads  

    I get with every program the error: Failed to launch Photo2 (Designer2 or Publisher2). Check that the requestet App is installed.

    All Apps are installed. What is wrong?

  3. Hi,

    on a relatively fast Windows 11 machine (i7, 32 GB RAM, Nvidia 1060) I have the following times for the opening of a 70Mb RAW File (Nikon nef):

    Affinity Photo V1:     3-4s

    Affinity Photo V2:  12-15s

    On my old Mac (OS 11.7.1, i5, 8 GB) the difference becomes very clear:

    Affinity Photo V1:    8s

    Affinity PhotoV2:  > 40s

    And yes, hardware acceleration is on, when it is turned off, it takes much longer (over a minute) as expected.

     

    The new version is therefore no longer usable on a slow computer, while one could certainly work with the old version. On a fast computer, the process is noticeably slowed down. Are there any similar experiences?

  4. 27 minutes ago, Mark Ingram said:

    Which app is showing that error? 

    - camerabits Photo Mechanic Plus,

    - DxO Photolab 5

    show the Error "System can´t access that file"

     

    Capture One (version 21) shows all the V2 Affinity Apps correct, but does not send any file to the app.

     

     

  5. 26 minutes ago, Sangoma said:

    Try the one I posted above, for me it eliminated that error.

    C:\Users\[username]\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe

    I did not recognized, that there is another .exe file, but it does not work for me, the same error: "The system cannot access the file". Maybe the problem is, that I am working on a local account, not on a administrator account. This was also a big problem during the installation (the Serif packages could only be installed as administrator, not as local user).

  6. 13 hours ago, walt.farrell said:

    Apparently an additional issue is that some applications (such as the one Phil is using) don't allow the user to specify a .bat file, only a .exe file.

    Yes, Programms like Photo Mechanics Plus only accepts a .exe file.

    When I point direct to the AffinityPhoto2.exe file (I found under the hidden Folder AppData/Local/WindowsApps/SerifEuropeLtd.AffinityPhoto2_...) I got the Error: "The system cannot access the file".

  7. I imagine there were maybe advantages to switching to the Microsoft App Installer (.msix files).
    However, for the user, the problems have increased:
    There are many who have problems being able to install the packages. For example, it took me hours because the packages from Serif did not run for me. Only after downloading them directly from the Microsoft Store was I able to install them.
    The next problem is the integration of the new programs in others. Now you can't find an .exe file which is accepted by other programs.

  8. Unfortunately the .bat file does not work with programms like Photo Mechanic Plus. Photo Mechanic Plus only accepts .exe files to invoke a programm.

    When I point direct to the AffinityPhoto2.exe file (I found under the hidden Folder AppData/Local/WindowsApps/SerifEuropeLtd.AffinityPhoto2_...) I got the Error: "The system cannot access the file".

  9. I had the same problem:

    On a Windows 11 computer I was only able to install the App Package under the Administrator account. (The programs were then also only usable for the administrator account.) On any local account I got the error message: "App Package could not start."

    I was able to solve it: I have downloaded the packages again from the official Microsoft Store. These Package I could install and activate without a problem on a local account.

     

×
×
  • 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.