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

Leigh

Staff
  • Posts

    3,203
  • Joined

Posts posted by Leigh

  1. If you had Affinity V1 installed when running Affinity V2 for the first time you would have been given the option to import your custom content from Affinity V1 into Affinity V2.

    Along with the automatic migration option, Affinity V2 can now link custom content such as Adjustments, Assets, Brushes etc... between all Affinity V2 apps on the same device. For example, brushes imported into Affinity Photo 2 can now be linked to appear in the Pixel Persona in Affinity Designer 2 and the Photo Persona in Affinity Publisher 2.

    Unfortunately, due to this new content linking feature you will notice that any custom content you have in the Designer and Photo personas in Affinity Publisher will not automatically migrate to the Designer and Photo personas in Affinity Publisher 2. You will have to manually migrate this content by Exporting from the Designer and Photo Personas in Affinity Publisher and importing into the relevant Affinity V2 app.

  2. On 10/10/2022 at 7:20 PM, Renx-78 said:

    In %APPDATA% I have no Affinity folder.

    In fact with the suggestions above it didn't find anything, so I did a search in the file manager with the name of the set of studio settings I had saved and found it in that path.

    If you run the app as an Administrator, does the folder then get generated in %APPDATA%\Affinity\Photo\1.0 (Store)?

  3. Sometimes when our apps fail to install or crash it's possible to get additional information to help diagnose the issue from Event Viewer within Windows. If you've been asked by our support team to provide your Application Logs from Event Viewer or you're trying to find out why the app failed to install or crash for yourself, please follow the instructions provided on Microsoft's TechNet article: How to save a copy of the Event Viewer Application and System logs

  4. You can download the latest and previous versions of Affinity V2 desktop apps from the below links:

    Windows

    macOS


    Unfortunately, it's not possible to download previous versions of our apps through the App Store, Mac App Store and Windows Store. However, if your Affinity Store account contains a licence entitlement for the relevant app, you can remove your current Affinity V2 app downloaded from an App Store, install a version from above and sign into your Affinity Store account to activate the licence.

  5. You may have been asked to provide a crash report when speaking with our support team. This will help them look into your issue further and hopefully allow our developers to figure out what caused the crash. Below are instructions explaining where the Crash Reports are stored on Windows, MacOS and iPadOS:

    Windows (2.1 onwards)

    Press the Windows Key + R to launch the Run dialog and enter the relevant app path:

    • Affinity Store (MSIX) & Windows Store:
      • Photo - 
        %USERPROFILE%\.affinity\Photo\2.0\CrashReports\reports
      • Designer - 
        %USERPROFILE%\.affinity\Designer\2.0\CrashReports\reports
      • Publisher - 
        %USERPROFILE%\.affinity\Publisher\2.0\CrashReports\reports
         
    • Affinity Store (EXE) :
      • Photo - 
        %appdata%\Affinity\Photo\2.0\CrashReports\reports
      • Designer - 
        %appdata%\Affinity\Designer\2.0\CrashReports\reports
      • Publisher - 
        %appdata%\Affinity\Publisher\2.0\CrashReports\reports

    Our crash reports will have a filename that's made up of random alphanumeric characters and will have a .dmp extension. Please send us this file. 

    macOS

    Open the Console app from Applications > Utilities. In the left hand panel click Crash Reports - you will see a list of Crash Reports. Find the relevant crash report - it should display the app's name in the Process Name column. Right click and select Reveal in Finder. Please send us the .crash file.

    iPadOS

    Go to Settings > Privacy > Analytics > Analytics Data

    You will see an alphabetical list showing all crash reports on your iPad. Find and open the one that corresponds to the Affinity app that's crashing. Click Share to save to an .ips file and save it to a cloud service.

  6. You can find out the recommended system specifications for our V2 apps on macOS, Windows and iPadOS on our website using the links below:

    Affinity Designer: https://affinity.serif.com/designer/full-feature-list/ 

    Affinity Photo: https://affinity.serif.com/photo/full-feature-list/ 

    Affinity Publisher: https://affinity.serif.com/publisher/full-feature-list/ 

  7. Using the OpenCL Flag (MS Store)

    It's also possible to use the --no-ocl flag to launch the app with OpenCL disabled. This flag will also edit the PerformancePreferences.xml to update <UseHardwareAcceleration> to False meaning subsequent launches of the app will continue to have OpenCL disabled and the --no-ocl flag is no longer necessary.

    To use the flag, press the Windows Key + R on your keyboard to open the Run dialog and then type CMD and press Enter. This will launch Command Prompt.

    • Affinity Photo: Type in start shell:AppsFolder\SerifEuropeLtd.AffinityPhoto_844sdzfcmm7k0!SerifEuropeLtd.AffinityPhoto --no-ocl and press Enter - the app will now launch.
       
    • Affinity Designer: Type in start shell:AppsFolder\SerifEuropeLtd.AffinityDesigner_844sdzfcmm7k0!SerifEuropeLtd.AffinityDesigner --no-ocl and press Enter - the app will now launch.
       
    • Affinity Publisher: Type in start shell:AppsFolder\SerifEuropeLtd.AffinityPublisher_844sdzfcmm7k0!SerifEuropeLtd.AffinityPublisher --no-ocl and press Enter - the app will now launch.
  8. On 10/1/2022 at 4:12 PM, Renx-78 said:

    In my case in the latest app versions the 1.10.5.1342 from the Microsoft Store on Windows 11, the path is as follows:

    C:\Users\"USERNAME"\AppData\Local\Packages\SerifEuropeLtd.AffinityPhoto_844sdzfcmm7k0\LocalCache\Roaming\Affinity\Photo\1.0 (Store)\Workspaces\Custom\

    For the other apps, in the path only change the long name folder that will contain Designer and Publischer in the name (and of course the folders with just the app name).

    The folders that appear immediately indicate the various workspaces/person.

    @Renx-78Our MS Store apps have always used e.g %APPDATA%\Affinity\Photo\1.0 (Store). This is the same on both Windows 10 & 11.

    Looking around, it looks like data can be copied to this "virtualized directory" %LOCALAPPDATA%\Packages\........\LocalCache\Roaming\ if the app is unable to access %APPDATA%. Are you able to access %APPDATA% and do you have an Affinity folder?

  9. Using the OpenCL Flag (Affinity Store)

    It's also possible to use the --no-ocl flag to launch the app with OpenCL disabled. This flag will also edit the PerformancePreferences.xml to update <UseHardwareAcceleration> to False meaning subsequent launches of the app will continue to have OpenCL disabled and the --no-ocl flag is no longer necessary.

    To use the flag, press the Windows Key + R on your keyboard to open the Run dialog and then type CMD and press Enter. This will launch Command Prompt.

    *Presuming you have the app installed in the default location, type in cd "C:\Program Files\Affinity\Photo\" and press Enter. Now type Photo --no-ocl and press Enter - the app will now launch.

    *If you installed the app to a different location or you're using Affinity Publisher or Designer, please update the location to point to correct folder.

  10. If you're having issues launching Affinity V2 and you suspect that OpenCL compute acceleration is causing the issue. you can force the app to disable OpenCL on launch.
     

    1. Clear User Data Method

    Launch the app with the CTRL key held down. When the Clear User Data window appears, make sure the only option selected is Disable Hardware Acceleration and click Clear. The app will now launch without Hardware Acceleration enabled.

    image.png



    2. No OCL Flag Method

    Using the --no-ocl flag will disable OpenCL for this and subsequent launches meaning you only have to use --no-ocl once and is not necessary for subsequent launches.

    MSIX / MS Store 

    To use the flag, press the Windows Key + R on your keyboard to open the Run dialog and then type CMD and press Enter. This will launch Command Prompt.

    • Affinity Photo: Type in %LocalAppData%\Microsoft\WindowsApps\AffinityPhoto2.exe --no-ocl and press Enter - the app will now launch.
       
    • Affinity Designer: Type in %LocalAppData%\Microsoft\WindowsApps\AffinityDesigner2.exe --no-ocl and press Enter - the app will now launch.
       
    • Affinity Publisher: Type in %LocalAppData%\Microsoft\WindowsApps\AffinityPublisher2.exe --no-ocl and press Enter - the app will now launch.


    EXE/MSI

    To use the flag, press the Windows Key + R on your keyboard to open the Run dialog and then type CMD and press Enter. This will launch Command Prompt.

    *Presuming you have the app installed in the default location, type in cd "C:\Program Files\Affinity\Photo 2\" and press Enter. Now type Photo --no-ocl and press Enter - the app will now launch.

    *If you installed the app to a different location or you're using Affinity Publisher or Designer, please update the location to point to correct folder.

  11. On 9/16/2022 at 1:31 PM, Blake_S said:

    Using "Update" button in the Data Merge Manager seems to fix this issue,

    after that the merge takes <5 seconds, nothing is written to disk.

    If I don't save this afpub file, re-open it, and attempt to do the merge, then 2 minute processing time + 30GB of data written returns, unless I click "Update" again.

    Only manually clicking the button works.

    If I first click Generate, then Publisher presents an option to update data sources before merging, and I confirm the update, this does not work - then it does the slow 2 minute merge.

     

    Thanks for the update on this.

    We're still investigating but I wanted to give you an update - Lee is currently out of the office.

    I've been able to replicate the issue with the files you sent to Lee via Dropbox. I'm pretty sure it's related to the PDF on the Master Page - when I delete the first group containing the clipped curve layer and the cut marks it appears to merge without using excessive memory and doesn't page to disk.

    I've tried the steps you mention above but that didn't resolve the issue for me. Would it be possible to send a screen recording of you doing the steps? Also, were you using the same linked PDF which was sent to Lee or a different PDF?

  12. 13 hours ago, nickbatz said:

    Just to follow up after more time - Leigh's solution (turning off Metal) is the answer. Big difference.

    Thanks again.

    Oh, a suggestion: it might be a good idea to include a "Preferred Settings for Apple Silicon Users" Read Me with the installation.

    That is, unless you did and I missed it - which I certainly wouldn't put past myself. 

    That's good to hear. You shouldn't have to disable Metal on Macs with Apple Silicon but for some users, like yourself, they have to for the app to work. We believe this issue was linked to the automatic brightness setting but some users don't have this option enabled and are still having to disable Metal.

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