Blobs at the beginning of each stroke, when will this be fixed???

[PJJ]

Hi Affinity Design Team,

You really have a great piece of software here but this is a debilitating bug that really needs to be fixed. It's unusable in its current state because of this problem.

Could you please tell us an approximate date when we all might expect this bug to be fixed?

 

Thank you very much

 

Paul

 

 

[DM1]

Paul I’m not seeing this in designer 1.8 with vector brushes. Can you provide more details?

[Leigh]

Are you referring to the issue described in the following thread? If so, it's still with our developers to be looked at.

 

[PJJ]

Yes this is exactly the problem I'm referring to, thank you!!!

[ml1]

This is apple's fault, and I encourage you to pressure them, not affinity, here: http://feedbackassistant.apple.com

As a developer myself, and a former apple employee from the Steve Jobs era, it is really tiresome talking to them because they no longer have truly competent programmers and are constantly breaking core OS functions and never fixing them. The current apple team needs to be heavily pressured by submitting many bug reports by many people. Even for trivial things that can be solved in one day and even when the exact code fix is provided to them, there are trivial problems like this that last for years across OS releases. I assure you, even though this sounds extreme, it is truly the situation. As developers, we need the users to vocalize the complaints more loudly than is rational, or they just act like it isn't important. They don't hold the same credo as 10 years ago, and they don't care unless we really pressure them. This is something that has gotten worse every year in the last decade, and I can not encourage you enough to submit bug reports to http://feedbackassistant.apple.com

To explain why this happens:

The first data that comes from the stylus through the apple library is hard coded as 0.33

Because of this, if the developer does not deal with that, it will cause the problem we see in affinity photo on the iPad.

To elaborate this further, the real pressure is always coming in later than the position. They will rationalize this by saying that it will be able to give a more accurate reading in the next 8 milliseconds - however, they neglected to write that code and so this doesn't ever happen. The 0.33 hard coded pressure at the start of the stroke is never ever updated. Leaving the developer to come up with their own way of coping with this bad data.

The way I deal with this, and how every other app deals with it, is by not showing the first data as 0.33 - either by making it much smaller or just not showing the first few points at all. Affinity can perform this with a few lines of code as an interim fix, but I still encourage everyone who really cares about drawing on the iPad to flood apple with bug reports. Be sure to also submit reports on the other issues, such as the intermittent stroke disconnects, the intermittent lag, and processor buzzing (which is amplified with a connected cable and certain tablet stand materials). These are not things a third party developer can fix, and they have gotten worse on the latest iPad.

[Leigh]

Thanks for information @ml1 - very useful 👍

[RobRed]

Bullshit! Easy to pass on the responsibility isn’t it when affinity devs don’t do your part!

Ive been in contact with them for months now, and every time I e been told that they are aware of it BUT it is not a priority!

The Affinity team is more interested on ignoring it and working on other new soft so they can make more money instead of fixing what users have already paid for!

i have many emails to them and this issue has just been brushed off as “not a priority” simply ignoring the call from users to be addressed! So blaming Apple and telling users to go deal with it is just more pathetic bullshit from devs who don’t give a shit!

No other vector or pixel art software has this issue, this issue is from Affinity Design and the devs don’t care!

[DM1]

19 hours ago, RobRed said:

Bullshit! Easy to pass on the responsibility isn’t it when affinity devs don’t do your part!

Ranting serves little use. I don't see any mods/devs blaming apple, just a comment regarding a post made by someone who states they are an ex Apple developer and were aware of an issue in iOS. 
 

No other vector or pixel art software has this issue....  maybe they ignore the initial pressure input as suggested by ml1. 
 

I'm happy to put up with the little blob for a while longer if it means Publisher for iPad is released sooner. 😄

[Paul Mudditt]

1 hour ago, DM1 said:

Ranting serves little use. I don't see any mods/devs blaming apple, just a comment regarding a post made by someone who states they are an ex Apple developer and were aware of an issue in iOS. 
 

No other vector or pixel art software has this issue....  maybe they ignore the initial pressure input as suggested by ml1. 
 

I'm happy to put up with the little blob for a while longer if it means Publisher for iPad is released sooner. 😄

I have tried loads of times to replicate this but it doesn’t happen for me, I wonder if something triggers it?

[DM1]

3 hours ago, Paul Mudditt said:

have tried loads of times to replicate this but it doesn’t happen for me, I wonder if something triggers it?

I just spent 5 mins trying to replicate blob with a wide variety of vectors and pixel brushes, no luck. Maybe it’s device specific? 10.5 pro and 1st gen pencil = no issue with current release.

[RobRed]

.

 

 

 

[RobRed]

5 hours ago, DM1 said:

Ranting serves little use. I don't see any mods/devs blaming apple, just a comment regarding a post made by someone who states they are an ex Apple developer and were aware of an issue in iOS. 
 

No other vector or pixel art software has this issue....  maybe they ignore the initial pressure input as suggested by ml1. 
 

I'm happy to put up with the little blob for a while longer if it means Publisher for iPad is released sooner. 😄

As the poster noted, rating is apparently the only thing that get devs to take on their responsibilities to their paid users which they choose to ignore and over look.

Again Affinity devs have been aware of this for over a year and with numerous conversations over this time THEY CHOOSE TO IGNORE IT AS THEY SAY ITS NOT A PRIORITY FOR THEM. This has been there message to me time and again.

And the fact that you “happy to put up with the blob so you get the new release” exactly makes my case, it’s all good when it’s not your problem right! What pathetic input, the same as the dev team

[RobRed]

4 hours ago, Paul Mudditt said:

I have tried loads of times to replicate this but it doesn’t happen for me, I wonder if something triggers it?

The devs have admitted they they are aware of it and have duplicated it. They choose to ignore it, probably thanks to people like DM1 who sends the message that they happy to ignore it because it doesn’t effect him personally and rather have the devs work on new releases rather than fix what they should have seeing users have already paid for this.

[Paul Mudditt]

52 minutes ago, RobRed said:

The devs have admitted they they are aware of it and have duplicated it. They choose to ignore it, probably thanks to people like DM1 who sends the message that they happy to ignore it because it doesn’t effect him personally and rather have the devs work on new releases rather than fix what they should have seeing users have already paid for this.

I think that is harsh when people are trying to help you replicate the problem. I am looking at your ink brushes in your original post, they do not seem to line up with my ink brushes.

Did you make a lot of modifications to the new V1.8 brushes?

Did you try a Forced Restart of your iPad?

Did you try forgetting your Apple Pencil then re-connecting?

[DM1]

2 minutes ago, RobRed said:

They choose to ignore it, p

@RobRed I no longer have this issue so I'm not convinced that devs have ignored it as you claim. Certainly some people may still be experiencing a problem as it’s possible that the issue can be triggered with specific combinations of hardware and brush settings.

Lots of things in life have to be prioritised and not everyone will be happy with the priorities given to bugs. There are several bugs I would like to see resolved and also features requested that I would love to have included. Hasn't happened yet. No point me ranting about it though so I just get over it and focus on those things I am able to control.

5 hours ago, DM1 said:

I'm happy to put up with the little blob for a while longer if it means Publisher for iPad is released sooner. 😄

Many users here are hanging out for the iPad Publisher release. My comment was meant to be lighthearted poke at how long it is taking, hence smiley face.

22 minutes ago, RobRed said:

They choose to ignore it, probably thanks to people like DM1 who sends the message that they happy to ignore it because it doesn’t effect him personally

Lol. I seriously doubt that devs have placed a low priority on addressing your issue simply because they wish to keep me happy! In fact, I doubt the developers even read these posts. They are way too busy developing. But, if they do, come on guys I want Publisher for iPad now!! 😁

[Xanderino]

*update: this only works 50% of the time*

 

A fix for while we wait forever!
change the brush settings/curve to ignore the first touch, see attached.

i know this changes pressure/ drawing style. But it’s a temp fix.

i really wish affinity were more reliable. It’s a super simple fix for them to do.

i would not recommend affinity until this is fixed. This is a demonstration of their poor commitment to updating and testing their product as technology evolves. 

Edited May 28, 2020 by Xanderino

[Paul Mudditt]

Assuming you haven't saved off some weird stroke pressure profile on the drag handles under the stroke studio, out of curiosity have you tried Document --> Defaults --> Factory Reset to see if that fixes your brush behaviours?

[Xanderino]

Hi Paul,

Yes I have, sorry to say. I wish the error was that easy of a fix.

I would say ml1 has the right idea for the problem with the .33 milliseconds. This explains why is doesnt happen with the old apple pencil and seems to be a common error on the ipad pro.

We probably have to wait for a fix from afinity, since apple has 100s of drawing apps that are already calibrated.

For now, i recomend everyone giving Adobe Fresco a go. I dont get the problem on there and it does similar things.

[DM1]

1 hour ago, Xanderino said:

We probably have to wait for a fix from afinity

Have you tried setting up a brush with a rope stabiliser set to 1 or 2 px’s. Been reported to help in some cases.

[Xanderino]

22 hours ago, DM1 said:

Have you tried setting up a brush with a rope stabiliser set to 1 or 2 px’s. Been reported to help in some cases.

Sorry to say, I still have the same issue.

[DM1]

Yes, that a real pain!