Jump to content

Affinity Photo - Export JPGs & PNGs - Weird Artifacts


Recommended Posts

Does it only happen on exports? - Otherwise I would say it's probably Affinity preferences GPU performance settings related, aka on Win due to OpenCL usage via the GPU driver, or under MacOS due to Metal vs. OpenGL usage.

You can try to alter/change the app's performance settings ...

... in order to see, if it afterwards (after an app restart) may behaves different and more graceful here for PNG & JPG exports.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

4 minutes ago, v_kyr said:

Does it only happen on exports? - Otherwise I would say it's probably Affinity preferences GPU performance settings related, aka on Win due to OpenCL usage via the GPU driver, or under MacOS due to Metal vs. OpenGL usage.

You can try to alter/change the app's performance settings ...

... in order to see, if it afterwards (after an app restart) may behaves different and more graceful here for PNG & JPG exports.

Only on exports.

Link to comment
Share on other sites

Just now, Nita Reed said:

Only on exports.

Strange. - Under what platform (Win PC or Mac), OS version and Affinity app version does this happen?

You may also want to look through the FAQ and Bug Reporting forum sections, if maybe some related bugs are known and have been published in this regard for your system & Affinity app.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

22 minutes ago, Nita Reed said:

I'm still 1.10.8 (I love it and haven't braved the change).  I'm on Windows 11.

It's possible that some Win 11 update has also actualized your sytems GPU driver, or that the update of Affinity v1.10.7 to v1.10.8 has overwritten previous available Affinity app settings etc. - Thus I would check and try out, if the actual hardware acceleration settings may do have some sort of possible impact here ...

Other than that it's also possible, that the recently updated Affinity v1 (v1.10.8 build), may on accident transports some newly introduced exporting bug(s) here.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

41 minutes ago, Nita Reed said:

Ugh....  THANK YOU!

I had unchecked that ages ago.  How did it get checked again?

I believe it probably got checked again due to the Affinity version update and/or fresh installation (... as I mentioned above).

However, the threads I referenced above to do already tell you how to disable that again (aka disabling OpenCL hardware acceleration), if you look & read through them.

Quote

...

To disable this, please navigate to Affinity Photo > Preferences > Performance and untick Hardware Acceleration at the bottom of this dialog.

Restart the app as prompted and try exporting once again - does this resolve the issue for you
...

OR

Quote

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.

Quote

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.

 

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

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