Jump to content

Recommended Posts

Posted

Hi!

Since I switched my graphics cards to RTX 5090 FE Affinity Photo is not working properly anymore. If I try to export an image the result is showing some weird offset and if I move the window after the export the image shown in AD will be fragmented and looks way off. This is happening for AD 2.59 and also in AD 2.60.

affinity_1.pngaffinity_2.pngaffinity_3.png

 

  • Staff
Posted

Hi @LetoAtrell,

This is an issue relating to hardware acceleration/OpenGL affecting the 50 series cards currently logged with the developers for further investigation. If you disable Hardware Acceleration under Edit -> Settings -> Performance and then restart the app when prompted to this should resolve the issue for all further exports.

Just so I can pass this info along, can you confirm your running the latest game-ready Nvidia driver version (572.47)?

  • Staff
Posted

Thanks, try updating to the 572.60 game ready driver, rebooting and then toggle H/A back on and see if the issue is still present, appears to be a potential driver issue fixed by Nvidia.

Posted
13 minutes ago, LetoAtrell said:

572.60 Studio driver did not resolve this issue!

Did you also try the 572.60 game ready driver, as advised

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

  • 4 weeks later...
Posted

I'm also having similar problems on a 5070 with driver version 572.83. Looking at Log.txt I see a LOT of lines like the following:

[OpenCL] Error -9999 (430): Could not wait for event!
[OpenCL] Error -9999 (430): Could not wait for event!
[OpenCL] Error -9999 (430): Could not wait for event!
[OpenCL] Error -9999 (430): Could not wait for event!
[OpenCL] Error -9999 (442): Could not flush!
[OpenCL] Error: Unknown error executing clFlush on NVIDIA GeForce RTX 5070 (Device 0).

  • 2 weeks later...
Posted

Same issue on my MSI 5070ti / Win 10 / Studio Drivers up to date. Solution disabling hardware acceleration help but have hope that this will be temporal thing. Sometimes i have same problem on my RTX 3080 but now it was permanent in every time when i try open new project.  

  • 2 weeks later...
Posted

Installed new 576.02 game ready driver today for my ASUS TUF Gaming RTX 5070 ti.

The new nvidia driver didn't fix the issue. Attached an image I have compressed to lower .jpg resolution with affinity photo 2.6.2 / hardware acceleration = ON.

Needless to say that the orginal image wasn't just a photograph of grey blocks.     

pixel mud.jpg

Posted

NathanC posted something here about trying the new driver then deleted it. It seems like Affinity is expecting the fix to happen on Nvidia's side as opposed to on Affinity's side. I'm not familiar enough with OpenCL to know if that's reasonable or not.

 

Or maybe they're struggling to root cause the issue and just hip-fire hoped that Nvidia's new driver would fix it without having to make any changes on the Affinity side - which might not be unreasonable either, but clearly it didn't fix it :(

Posted

After reading a bit more about at least the set of OpenCL errors I'm seeing in the logs, it does seem likely to be a GPU driver issue. Perhaps a local Affinity-based fix is possible with some significant effort but it might be a safer bet to hedge that Nvidia will fix this eventually. I'd be curious to know if Nvidia is tracking this OpenCL issue from their side at all.

  • 3 weeks later...
Posted

Installed new 576.28 game ready driver today for ASUS TUF Gaming RTX 5070 ti.

Same issue as before with affinity photo 2.6.2 when hardware acceleration is ON.

Since they don't talk to us, we can only guess it .. it seems that both nvidia and serif wait for the other to fix it.  

 

  • 2 weeks later...
Posted

Just wanted to add my 5090 issue to this:

I can't start a new document in any Affinity apps with my 5090 selected for Renderer. I have to select WARP to let me do that. It just hangs the application completely.

Nvidia driver 576.40 here.

Posted

I am looking into solution for soooo many months, they still didn't fix it

I am so disappointed, that they just don't give a F.
Affinity seemed like great promise of photoshop without being harvested, but the way they don't care is hilarious, you really think nobody uses rtx 5xxx? Or is it just calculation, that it's not worth to care about this small amount of users? 

Posted

It's a little strange. My machine is fast enough, i dont really care but i did waste 20 minutes trying to figure out why i couldnt use any of the tools.

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.