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

Search the Community

Showing results for tags 'hardware acceleration'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 14 results

  1. We've had several reports of RAW files having Artefacts or Green Lines after updating to 2.4 on Windows. This is a known issue and appears to be related to OpenCL. Turning off OpenCL should resolve this issue for now. To do this, go to Edit > Settings > Performance and untick Enable OpenCL This has been logged with our developers to be fixed.
  2. Seems to me, that it 1709 crashes much more than previous beta. Reason hardware acceleration? See attachment please. 1c98764c-2207-4c63-ad34-cda3e4f79093.dmp 8cf143ef-ca7b-4c0f-b5a8-169d8f41095d.dmp 87bbf555-ab31-49b9-8e94-8fc06cf9a550.dmp d7a418ca-3e3f-4768-92ca-6ad13b30f76b.dmp
  3. Hello: On Windows 7 when I try to check the Hardware Acceleration option under Performance in Preferences, it tell me, Unsupported Machine Configuration, with the following msg: Well, I upgrade to Windows 10, to be able to use this option, I updated every single driver, and still don't letting me mark this option. As u can see, it require "Windows 10.0.19042" the same Windows version I have, I updated the direct X, openGL, everything, and still don't let me mark the option. My video card is "Nvidia GeForce GTX 760" with Adapter RAM of "20488 MB (2GB)". Here is more info: Idk if there any another thing I have to do... Thanks ahead!!
  4. Split from here by moderator funny but the kepler range has always had OpenCL vulkan and Cuda support in the past. It just seems for some reason that 700 series variants and some M mobile variants have just been dropped by nvidia in the drivers package, and thus for no reason, devs and affinity also no longer allows cuda and openCL hardware improvements - even on win 11. Rendering your system useless if its a AIO unit or a m variant not in the list for 500 onwards drivers. shame - why can't we just force hardware acceleration?? its a tick in a box. There must be a way. I have cuda, i have vulkan and i have openCL. i mean the clue is n the 'open' bit!!! its opensource!! My current error (reason for suddenly no longer supporting my mobile variant of a GPU since v2 came out) in Affinity photo is that i'm running an old operating system so I cant use GPU acceleration. I'm on windows 11 won't be getting v2 until this is fixed or we can just enforce it. There is no valid reason for not supporting even a 7 series card when it clearly has over 1300 cuda cores, more than capable of accelerating the suite. if only i could just tick the box that thinks win 11 is older than win 10.
  5. In order to enable Hardware Acceleration in Affinity V2 apps, your graphics card will need to have Direct3D 12 Feature Level 12.0. To find out if your graphics card(s) has Direct3D 12 Feature Level 12.0 please follow the below steps: Press the Windows Key + R Type dxdiag into the Run dialog and press OK This will bring up the DirectX Diagnostic Tool. Click the Display tab and look at the Feature Levels under the Drivers section - this will show you the feature levels your graphics card supports: Please Note: If you have multiple displays connected to your machine you will have multiple Display tabs listed. You need to make sure that you have the correct Display tab selected to show the correct details for any dedicated graphics card you have installed or connected.
  6. 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. 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.
  7. With metal hardware acceleration activated on an Apple Silicon Mac with Retina display, using a masked gradation curve inside a layer containing transparent areas, the transparency seems to be reduced on parts of that layer, even if the gradation curves mask doesn't should alter anything in that area. This problem only appears, if an image is present in the background. Without having a background image, the wrong transparency alteration does not happen. This seems to be a bug in metal hardware acceleration, because deactivating it solves the problem.
  8. Hi everyone, When i activate Hardwre Acceleration, when i create a new empty canevas everytime Affinity crash. retouching a photo randomly affinity crash. my version 1.9.2.1035 My video card : Nvidia Geforce GTX1660 TI 9.73 Go free on C:\ executing the following report made it crash. attachment_Log.txt 80a96e18-5c2a-491a-aa02-d9c9facf3dcf.dmp
  9. Our developers have identified an issue where our apps can crash on startup when OpenCL Hardware Acceleration is Enabled and you're using an Intel Graphics Card. This issue is related to having traces of an old driver installed alongside a newer driver. Intel have suggested that users remove all traces of Intel Graphics Card drivers using Display Driver Uninstaller (DDU) and then reinstall the latest drivers using the Intel Driver & Support Assistant tool. For more information on how to use the Display Driver Uninstaller (DDU) tool, please read their tutorial but please use this tool at your own risk. Alternatively, 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.
  10. We don't maintain a list of compatible Graphics Cards but in order to enable Hardware Acceleration in Affinity V1 products on Windows, your system must meet the following requirements: Operating System: Windows 10.0.19041 (May 2020) GPU: Any GPU capable of Direct3D12 Feature Level 12.0 Intel Earliest Supported GPUs - Skylake Microarchitecture HD Graphics 510 NVIDIA Earliest Supported GPUs - Maxwell Microarchitecture GeForce 900/Titan series AMD Earliest Supported GPUs - GCN2 Microarchitecture HD 7790/8770 Rx 260/290 Please note: AMD Radeon RX 5000 series and later cards are currently incompatible.
  11. Due to performance related issues with AMD GPU drivers, our developers decided to disable Hardware Acceleration for AMD Radeon RX 5000 series and later cards in the 1.9.1 update. We've notified AMD of the issue and we're awaiting their response. More information can be found in the below thread - Update -
  12. Won't let me tick the box to use software acceleration. Instead I get the following message. Seems to be the right version but possibly it won't work with pro.... or possibly a bug?
  13. Can someone confirm whether that is possible? It seems to be possible in Affinity Designer, but not in Affinity Photo, which is weird. I thought the apps were pretty similar. First screenshot is Affinity Photo, second is Affinity Designer.
×
×
  • 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.