Fill lag when using Logitech G305 on macOS

[Customer Feedback]

One more for you, Serif Support:

We also just posted a related issue in Publisher (but the issue is NOT the same):

 We have experienced some very annoying lag on macOS M1 machines (Monterey 12.3.1, 16GB, 1TB) when dragging even basic shapes using this mouse, that is very popular:

Logitech G305

The problem is very bad in Publisher with any combination of these settings (notice that in Publisher we cannot turn Metal on and off - we can in Designer), so we have tried it all, and we don't believe we can resolve the issue using configuration - and we shouldn't have to:

Here you see it:

If I then use a more humble mouse, the very popular (for travel) M187 Mini Mouse:

We believe it is the High DPI nature of this mouse that Designer struggles with - but we only see these lag issues in Serifs software (Designer struggles the most)

Quote

"HERO sensor delivers exceptionally accurate and consistent performance with zero smoothing, filtering or acceleration from 200 to 12,000 DPI. G305 can save up to 5 profiles with up to 5 DPI levels each on the onboard memory."

We see the lag issue using any of the DPI modes the mouse has to offer in Affinity Designer on macOS. We tried on a Windows equipped computer as well using the same mouse with no issues.

The mouse is configured in macOS with Tracking speed set to FAST (max) - and Scrolling speed a step above default settings.

We never experienced this issue in any other design program or elsewhere - so please look into it, Serif. 

Regards,

Eddie

Edited May 7, 2022 by Customer Feedback

[EmT]

Hi @Customer Feedback

This is something we are aware of and it has been passed over to our developers for further investigation. 

If you follow the 'News and Information' thread on our Forum, it will advise you when an update is available.  

https://forum.affinity.serif.com/index.php?/forum/4-news-and-information/

[Customer Feedback]

13 hours ago, EmT said:

Hi @Customer Feedback

This is something we are aware of and it has been passed over to our developers for further investigation. 

If you follow the 'News and Information' thread on our Forum, it will advise you when an update is available.  

https://forum.affinity.serif.com/index.php?/forum/4-news-and-information/

Hi

Thank you for an informative reply.

We're hoping for a fix soon, as we're having a hard time persuading employees to choose Affinity as long as the problem exists.

/Eddie

[Customer Feedback]

On 5/9/2022 at 10:22 AM, EmT said:

Hi @Customer Feedback

This is something we are aware of and it has been passed over to our developers for further investigation. 

If you follow the 'News and Information' thread on our Forum, it will advise you when an update is available.  

https://forum.affinity.serif.com/index.php?/forum/4-news-and-information/

If the next update fixes the problem. I'm starting to doubt that. Time is money both for us and Affinity and the rest of the world. If you assume one just sits and waits, the world will surprise you.

I/we simply cannot understand why such a clear bug has not been fixed long ago in a hotfix.

It's not a bug you experience in special cases. We experience it in Affinity in almost every workflow and in every single adjustment adjustment. If we choose to invest in Affinity licenses! After all, we never ever choose the alternative of purchasing devices that are "compatible with Affinity".

That's why these fixes are typically called service releases. It's a mundane service to customers when a product suffers a significant defect that causes customers to lose money or lose productivity.

And from the professional part of your customers, I can only say that this kind of thing is quite central to a risk assessment before investing in a product and switching to it; does the manufacturer provide support and bug fixes within an acceptable timeframe and here one year is simply not good enough.

Doing some research in the forum I can also see other bugs and clear shortcomings reported in many, many times by customers that either take years to fix or have not yet been fixed/remedied.

This is very worrying. And blocking, to be precise.

/Eddie