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. On 9/21/2022 at 9:48 PM, Mikołaj Wójcicki said:

    Will try, I have used DDU many times, but thanks for help anyway

    @Mikołaj WójcickiLooks like AMD released some new drivers a few days ago: Adrenalin 22.9.1 Optional. Might be worth using DDU to remove all existing drivers and try the new ones. If that doesn't improve things, you could also try the Adrenalin 22.5.1 Recommended (WHQL) drivers

  2. If for some reason you need to deactivate a device and remove your licence details from an Affinity V2 application, select Account on the Toolbar and click Deactivate this device. You will be prompted with a warning that states:

    "Deactivating this device with sign you out, remove all your licence data and require a licence activation the next time any Affinity application starts. Do you want to continue?"

    Clicking Yes will deactivate the device and remove your licence details. Clicking No will take you back to the Account screen.

  3. If you would like to reset an Affinity V2 app back to its default settings, please following the below steps:

    macOS & Windows:

    • To reset an Affinity V2 desktop app back to its defaults, open the app with the CTRL key held down. 

    iPad:

    • To reset an Affinity V2 iPad app back to its defaults, open the app and double tap the Affinity V2 splash screen when it appears.


    When the Clear User Data window appears, click Select All then Clear. However, Instead of resetting everything in the app you can selectively tick and untick options you would like to be reset or preserved. For example, if you only want to reset the Studio back to default you can just tick Reset Studio and leave everything else unselected.

    Please Note: Selecting All will completely reset the app back to the default settings and all imported or created brushes, macros presets etc... will be lost.

  4. Before going any further, please make sure that you're using a supported operating system. Affinity V2 WILL ONLY INSTALL AND RUN on Windows 11 & Windows 10 May 2020 Update (2004, 20H1, build 19041) or later. To find out which version of Windows you're running, please read this from Microsoft.

    Affinity V2 & .MSIX

    If you've purchased Affinity V2 for Windows directly from the Affinity Store, you will have downloaded an MSIX package. MSIX packages are a modern and reliable installation package which means install and uninstall issues are rare. You can read more about our decision to use MSIX here. However, if you run into issues when trying to install or uninstall Affinity V2, please try the below suggestions:


    Check you're not getting one of the below install errors:

    App Installer Download:

    If you don't have an app installed to open the .MSIX file you may need to download and install App Installer from the Microsoft Store here.


    Use PowerShell Instead:

    You can also install MSIX packages via PowerShell by opening PowerShell as Admin and then using the following command, presuming you have downloaded the MSIX to your Downloads folder:

    Add-AppxPackage -Path "C:\Users\MyUserName\Downloads\affinity-designer-2.0.3.msix" -DependencyPath "https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx"


    Log Files

    If you're still having issues installing our apps and you're not getting one of the errors listed above, you can check the MSIX installation logs in Event Viewer by going to:

    Application and Services Logs > Microsoft > Windows > AppxDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational


    App Fail to Uninstall

    Apps can be uninstall via Settings > Apps > Apps & Features but if that fails for whatever reason, you can try uninstalling via PowerShell using the following command:

    Remove-AppxPackage -Package "SerifEuropeLtd.AffinityPhoto2_2.0.0_x64__v5ap6qg21y3cg"

    You can use  AppxPackage –AllUsers -Name *Affinity* Cmdlet in PowerShell to find the correct Package Name before running the above command.

  5. If you're looking to access Affinity V2 from another app on Windows - for example, using Affinity Photo V2 as an External Editor in Raw Therapee, you will need to point to the app's execution alias. They can be found here (assuming default installation location):

    • Affinity Photo V2:
      C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe
       
    • Affinity Designer V2:
      C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe
       
    • Affinity Publisher V2:
      C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe
  6. If you've purchased Affinity V2 for Windows directly from the Affinity Store, you will have downloaded an MSIX package. You will notice when installing Affinity V2 you will not be offered the ability to change the installation path. This is expected and is down to how MSIX packages work. All Windows Apps are installed to the default drive set in Settings > System > Storage.

    There are two options to change where Affinity V2 is installed to:

    1. Temporarily change "Where new content is saved" by going to Settings > System > Storage > More / Advanced Storage Settings > Change where new contact is saved and select the required drive from the New apps will save to: dropdown menu. Once you've installed the app to the new drive, you can revert this setting back to Local Disk (C:) 
       
    2. Move the app to a different drive once installed by going to Settings > Apps > Apps & Features selecting the Affinity App and clicking Move

    Please note: It's only possible to pick the drive where you want the app installed to but not the full location. Unfortunately, this is handled by Windows and cannot be changed by the user.

  7. If you purchased Affinity V2 for Windows directly from the Affinity Store, you will have downloaded an MSIX package. You will notice when installing Affinity V2 you will not be offered the ability to create a Desktop shortcut. This is expected and is down to how MSIX packages work.

    However, you can manually create a desktop shortcut after installation. Go to Start > Run and enter Shell:AppsFolder and press OK - This will take you to a folder where you can drag and drop a copy of the Affinity V2 shortcut to your desktop.

  8. We're aware of an issue related to Intel's range of Arc GPUs and our apps crashing on launch due to OpenCL. This particular issue is currently logged with our developers for further investigation.

    You will need to disable OpenCL for our apps to launch without crashing. To do this you can turn off  OpenCL Hardware Acceleration by following the steps described in [FAQ] How can I disable OpenCL compute acceleration on Windows? or can you use @v_kyr's Affinity OpenCL Disabler tool from here.

  9. 4 hours ago, nickbatz said:

    New Mac Studio here (M1 Max, 32-core graphics, 64GB). I just did a search hoping to find the recommended settings for my machine, and this thread came up.

    Same lagging behavior, especially copying and pasting - which is what I'm doing here.

    Well, this report isn't providing any new information.

    Is the macOS version due next month any better?

    Is performance improved if you go to System Preferences > Displays and disable "Automatically adjust brightness"?

  10. 20 hours ago, Mikołaj Wójcicki said:

    Adding to this. Just to avoid any confusion. I'm running Windows 10 and I am still getting occasional black screens.

    Ok. With both Ben and Komatös running the the latest drivers without any issue, it might be worth trying DDU to remove all GPU drivers from the your system and try again with the latest version. Here's a tutorial on the process: https://www.wagnardsoft.com/content/ddu-guide-tutorial

  11. 21 hours ago, Ben Weston said:

    I'm afraid I've now reverted to Windows 10 so can't provide this. However, on the same drivers now on Windows 10, I'm no longer getting any crashes with Designer! It still tells me my system isn't "modern" enough to enable OpenCL but I've not had a single crash since reverting to 10.

    Thanks for replying. This thread explains why you can't enable Hardware Acceleration but it doesn't explain why the app crashing. It's great to hear the app is no longer crashing but if you run into these issues again, please let us know👍

  12. On 9/17/2022 at 11:44 AM, gencris said:

    Hello,
    I have been having the same color wheel problem for several weeks. Over the past few days it has been coming up repeatedly. unable to work properly.
    I tested without believing the brightness adjustment in the parameters and miraculously it is much better. great.

    However I still have a memory management problem with photo and designer.
    I load a small file of 40mb, vector and bitmap, Aphoto displays 2.5gb on the activity monitor. I work for a few minutes. photo take at once 12gb of memory!!! slowdown but without the wheel.
    I click "modify in designer": Aphoto 2.34go, Adesigner 4.65go.....! 🤪

    It's painful. I don't really want to go back to Photoshop, but I'm starting to think about it... 🤔

    I work with MacbookAir M1 16gb ram.

    Thanks for the information. Regarding the memory issues, were these "small" files originally created on the M1 Macbook or are they from an Intel Mac?

  13. On 9/13/2022 at 11:35 AM, Ben Weston said:

    @Ben WestonThanks for this. Unfortunately, it's not giving much information apart from stating it's crashing in DirectX. Can you have a look in Event Viewer and see if you have anything listed in there for the app when it fails to launch: https://forum.affinity.serif.com/index.php?/topic/101455-faq-how-to-save-a-copy-of-application-logs-from-event-viewer/

     

  14. 17 minutes ago, GarryP said:

    Even though this is a slightly different issue, it might have been better if, rather than creating a new thread, you continued the other thread.

    As it is, you now have the first part of the conversation in another thread which people will have to look for as you didn’t add a link to it, and the second part of the conversation in this thread where what you are doing and the reasons for what you have done already are ‘hidden’ in the other thread.

    Some people coming to this thread, without seeing the other thread or even knowing of its existence, will simply be confused about what you are trying to do and why.

    And, anyone with the same sort of issues as yourself may see your other thread and not see this one, meaning that they will only see the first part of the ‘answer’.

    A moderator may join the two threads together so they present one single issue.

    They have now been merged 👍

  15. On 9/9/2022 at 10:44 PM, Mikołaj Wójcicki said:

    Sure can do
     

    [DXCore] Found 2 adapters
    AMD Radeon RX 5700
    	Version: 31.0.12019.9007
    	IsHardware: Yes
    	Supports D3D12 Feature Level 12.0: Yes
    	HardwareID: PCI\VEN_1002&DEV_731F&SUBSYS_38110000&REV_C4
    	LUID: 0xC101
    Microsoft Basic Render Driver
    	Version: 10.0.19041.546
    	IsHardware: No
    	Supports D3D12 Feature Level 12.0: Yes
    	HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00
    	LUID: 0xD733
    [DXGI] Enumerating adapters
    AMD Radeon RX 5700
    	HardwareID: PCI\VEN_1002&DEV_731F&SUBSYS_381114620000&REV_C4
    	LUID: 0xC101
    Microsoft Basic Render Driver
    	HardwareID: PCI\VEN_1414&DEV_008C&SUBSYS_00000000&REV_00
    	LUID: 0xD733
    [OpenCL] Found 1 platforms:
    Name: AMD Accelerated Parallel Processing
    	Vendor: Advanced Micro Devices, Inc.
    	Version: OpenCL 2.1 AMD-APP (3444.0)
    [OpenCL] Found 1 devices for platform AMD Accelerated Parallel Processing:
    AMD Radeon RX 5700
    	Vendor: Advanced Micro Devices, Inc.
    	Version: OpenCL 2.0 AMD-APP (3444.0)
    	Integrated: false
    	Detachable: false
    (Skipping unsupported device)
    [OpenCL] Found 1 devices for platform AMD Accelerated Parallel Processing:
    AMD Radeon RX 5700
    	Vendor: Advanced Micro Devices, Inc.
    	Version: OpenCL 2.0 AMD-APP (3444.0)
    	Integrated: false
    	Detachable: false
    (Skipping unsupported device)
    	Installed
    TabletContext::Create: original queue size is 0
    Wintab: Failed to set queue size
    Exit

    On the side note these black screens aren't like standard crashes I can basically press Win+Ctrl+Shift+B to reload GPU drivers and the screen becomes functional again

    Thanks for this information @Mikołaj Wójcicki. Have you always had this issue or did it only start happening recently?

    @Ben Weston Are you able to send me any crash reports? https://forum.affinity.serif.com/index.php?/topic/98904-where-to-find-crash-reports/

     

  16. On 9/5/2022 at 10:31 PM, Timothy Butler said:

    Any further news two months later? It's pretty discouraging since it has been going on for nearly a year. As much as I prefer Affinity Photo, I've taken to using Pixelmator Pro most of the time for simple jobs so that I don't have to go turn automatic brightness control off just to make a few photo edits. (And even with it off, Pixelmator Pro seems surprisingly sluggish on an M1 Max compared to older Intel Macs or an original M1 -- something just seems wrong.)

    I'd gladly pay for an update if it would just fix these performance bugs with Affinity on M1 Pro/Max.

    I have nothing new to report, sorry. I can only repeat what Patrick states is the following thread:

    Quote

    We are focussing our efforts on a major release (new features and fixes) and consequently have not done any minor patches for a long time, as you say. But no not dead.

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