Jump to content

Recommended Posts

Posted

Hi
just thought I would report this one....Been working on a large file this morning (1000 x 500mm 300Dpi) which is multi-layered and consists of a mix of raster and vector elements. It was working | workable fine until the update this morning; where every-time I zoomed/panned across screen I was confronted with large blocks of flashing white shapes!

Added a video below showing the issue.. Hardware Acceleration is off!

NB
An earlier file with same size configuration and less layers is not causing this issue

I fixed it I think! by:
1. Setting up an new file with same dimensions and dpi.
2. Simplify the layer structure
3. Copy Artboard to holding file

bit strange I think!...I have seen this before but not for a long time!

 

 

Affinity Version 1 (10.6) Affinity Version 2.6.0  All (Designer | Photo | Publisher)   Beta; 2.6.2.3187
OS:Windows 10 Pro 22H2 OS Build 19045.5371+ Windows Feature Experience Pack 1000.19060.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

  • Staff
Posted

Hey StuartRc,

To me, it looks like the render tiles are lagging a bit behind—possibly due to the fact you have OpenCL off as you're getting no support from the GPU to help render the document in an acceptable time.

What happens if you turn OpenCL on?

Also, try going to Settings > Performance and change Retina Rendering to High Quality.

Posted
On 10/20/2023 at 9:26 AM, Chris B said:

Hey StuartRc,

To me, it looks like the render tiles are lagging a bit behind—possibly due to the fact you have OpenCL off as you're getting no support from the GPU to help render the document in an acceptable time.

What happens if you turn OpenCL on?

Also, try going to Settings > Performance and change Retina Rendering to High Quality.

Hi 

I tend to work without it as when I have it active I had a lot of trouble using the brushes. and organising the brush panel...Sometimes it gets re-activated with updates.. but it is the first thing I switch off

NB was just looking for just looking for a set of Geometry icons (Merge Curves | Separate Curves | Fill holes | Remove Inner Curves | Cut Curves with Key object) in the 'Customise Toolbar' that appear to be missing in latest live version but present in last beta...Cannot really create a bug thread as you appear to be about to go to 2.3!

 

Affinity Version 1 (10.6) Affinity Version 2.6.0  All (Designer | Photo | Publisher)   Beta; 2.6.2.3187
OS:Windows 10 Pro 22H2 OS Build 19045.5371+ Windows Feature Experience Pack 1000.19060.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

  • Staff
Posted

Have you tried working with OpenCL enabled in the beta? Some work was done on AMD support so I wonder if you're still having issues. We have a new AMD CPU and GPU machine I'd be happy to do some testing on brushes with.

I can see those options in 2.1 but they are in a different position to the 2.3 beta.

Posted
15 hours ago, StuartRc said:

Hi 

I tend to work without it as when I have it active I had a lot of trouble using the brushes. and organising the brush panel...Sometimes it gets re-activated with updates.. but it is the first thing I switch off

NB was just looking for just looking for a set of Geometry icons (Merge Curves | Separate Curves | Fill holes | Remove Inner Curves | Cut Curves with Key object) in the 'Customise Toolbar' that appear to be missing in latest live version but present in last beta...Cannot really create a bug thread as you appear to be about to go to 2.3!

I do the same. OpenCL just doesn't work well with brushes at all, even with an Nvidia GPU. There are several brush related bugs tied to OpenCL and it overall runs worse than on the CPU with only a few exceptions, most of which are filters related.

  • Staff
Posted

I genuinely don't see much of a difference for brushing with OpenCL on or off:

 

I know you use the Paint Brush Tool extensively, Frozen Death Knight so I am not trying to dispute what you say but for me there's no noticeable difference. This is using an RTX 3050Ti. I do not have a G-Sync monitor at work so can you tell me if you are using this and I can test further at home.

Posted

Hi

I think it was more to do with the organisation and manipulation in the brushes panel that caused me issues!... Re-organisation was flagging lots...The app in this regard worked much better with Open GL off. I will investigate with 2.3 and see if it has improved....

I will also check the Toolbar buttons...I used quite a bit (Useful feature!)... But thanks for adding the Greyscale | FX omit button toggles (I had not noticed those being added).. must have one of those worms in my skull!😀

 

Affinity Version 1 (10.6) Affinity Version 2.6.0  All (Designer | Photo | Publisher)   Beta; 2.6.2.3187
OS:Windows 10 Pro 22H2 OS Build 19045.5371+ Windows Feature Experience Pack 1000.19060.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

Posted
On 10/25/2023 at 11:17 AM, Chris B said:

I genuinely don't see much of a difference for brushing with OpenCL on or off:

I know you use the Paint Brush Tool extensively, Frozen Death Knight so I am not trying to dispute what you say but for me there's no noticeable difference. This is using an RTX 3050Ti. I do not have a G-Sync monitor at work so can you tell me if you are using this and I can test further at home.

This is my average experience using OpenCL:

OpenCLBrushPerformance.thumb.gif.09462c165321d6eb4247af7f6a6c894c.gif
 

Been like that since it was added. I did make several reports about multiple bugs. Some have been fixed, but others are still there, like the severe brush lag. I also have compared GPU acceleration between Affinity, Photoshop, and Krita. Affinity performs the worst and I have tried the feature on at least 4-5 different computers with vastly different specs, this one in particular is running a 3060 card.

I'll check the G-Sync thing and see if it improves anything.

Edit: I had it on already. Shutting it off didn't help. :(

Posted

Hi

I just activated Open GL and used the offending file (As above) with 2.3 beta and 2.2 live versions just to compare!
There appears to be no difference... or no difference I can see. The squares still appear. It is is a complex file and large. reducing the file size | Number of layers (such as merging the Raster sections) helped a lot. Do you want the file? (its 47mb zipped)

I have seen myself the brush lagging with Open GL. not sure whether  I reported it but I do remember it causing lots of issues with the brushes

 

When active
There is also a noticeable delay when selecting | toggling between Personas (Designer > Px)
There can be a long delay when you switch between brush categories in the panel
There can be a lag on the brushes as outlined above 

 

 

Affinity Version 1 (10.6) Affinity Version 2.6.0  All (Designer | Photo | Publisher)   Beta; 2.6.2.3187
OS:Windows 10 Pro 22H2 OS Build 19045.5371+ Windows Feature Experience Pack 1000.19060.1000.0
Rig:AMD FX 8350 and AMD Radeon (R9 380 Series) Settings Version 21.04.01 
Radeon Settings Version 2020
20.1.03) + Wacom Intuous 4M with driver 6.3.41-1

 

 

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.