Brush stroke spacing changes when lagging

Hi, the stroke spacing in my brush strokes becomes too separated sometimes, when there are many polys and my strokes are too quick is more obvious… I get app is going to lag sometimes with the brush strokes, but wouldn’t be better if the strokes appear delayed behind my stroke instead of the spacing changing so much the strokes get uglier and even “squarey” (instead of a smooth curved line)? I used the smooth stroke feature but even if that helps a little the same happens, that depending of the velocity of the stroke the spacing of the stroke appears as if it is longer that it is set.

I’ve encountered this - if I understand what you’re describing. I’ve taught myself to pause a bit in between strokes, generally find that applying strokes too quickly when it’s lagging from high RAM/GPU use can cause an adverse affect. Pausing for a second in between each one mitigates this. It’s my work around.

1 Like

Yeah that’s what I do too but sometimes it makes sense to make quick strokes but then I see some ugliness. If able I reduce the multi resolution and it happens less, but the behavior is still there (variable spacing according to load).

Strokes can be quick, it’s the frequency they’re applied at that has an affect when hardware is stressed. Quick stroke after quick in this state produces wry effects - I’ve even had the red dot wander off and start responding to input miles away from where the stylus is on the screen. Sometimes the software just needs that additional second or so to finish its calculations from the lag before it’ll reasonably react to a new input.

I find that a high poly model combined with post process effects can cause problems with fast strokes - you could also try using a matcap to keep your model clarity, as that’s much less resource hungry.

Friends, how old are you?
Lagging is there since the invention of painting on a computer.

It is not a bug, it‘s a ongoing dance between what you expect from real life and what your specific machine and app can handle.
Drawing in Photoshop 4.0 on my 386 PC with 90MHz and 4MB Ram was a nightmare and a wonder at same time. What people call “lagging” today is a luxury problem.

Anyway, I could imagine, regarding lagging one would see a clear difference between an older iPad and the new M1 I.e.

That said, it’s all about performance.
What is your tablet able to, and how much performance can the app realise out of it.

Bla bla bla….But understanding the background, it’s getting obvious what you can do against:

Outside Nomad

  1. Close all other apps, everything, except Nomad.
  2. Check the net on which services you can switch off to save some extra memory and speed. By default a bunch of things are going on in the background, maybe you don’t need all of them.

Inside Nomad
Make a fast stroke with your problem brush to see what you are fighting against.
Do not undo, keep it to compare.

Now do following:

  1. Switch to Matcap
  2. Switch off “smooth shading”
  3. Switch “post processing” off completely.
  4. Watch out for polycount. Do you really need 384 trillion verts for an eye sphere? :rofl:

And please, don’t be surprised if lagging is there when working with dynamic topology and small radius while density is set to watch radius. This is the grandmother of all performance coolprits. Switch it off if not needed.

Now do second test stroke to compare.
This will have an impact already.

Now you could do some more things.

Try to change “spacing” in stroke settings. After you have saved so much performance with above steps, maybe you can try decreasing spacing for a better result.
These are my workarounds if there is no money for the latest, fastest and hippiest machine. Anyway, one will bring also these new wonders at it’s performance border quickly, if not taking care of at least some of above said points.
And finally:
Also stroke smoothing and lazy will help, but sure, this is against nature of fast natural stroke.
Just try.

Have fun with the never, ever ending bug. :vulcan_salute:

1 Like

Disable postprocess, select matcap and try to use “partial drawing” in the Settings.


That was my solution, apart from the partial drawing option - I’ve never even tried it due to your little warning in the tool tip :joy:


Man, you wanna talk lag. I used to work on 3DS Max on Windows ME. Hewlett Packard desktop with Pentium clocked at like 400MHZ, 128MB of RAM. Naff graphics card that I can’t even remember but couldn’t even run MDK II game without spluttering to death. Coupled with a dial up modem where 20MB downloads literally took an 40minutes to an hour. Ugh. By today’s contrast on my iPad, it’s not even lag. It’s a minor visual delay.


I’m not talking about lagging but about separation of stroke points that make the trajectory of the strokes… I would prefer a little bit of lag if the line could keep a good shape.

It seems the word “lag” is a trigger in your heads, people… I was talking about the line “breaking” when the app starts to lag, but not about the lag.
Just to clarify, I would love if the line could keep actual trajectory of the stroke even if that means having to wait for the stroke to be complete. I try to do a curve and end up with a curved formed of a few straight lines. Yeah in Digital art I have seen that in the past but not in all apps, I guess it depends of how it is programmed.
Yeah, for now the best is to try to keep the memory load low and do strokes slower.

Mmm ah… I forgot about testing Partial Drawing option as I didn’t quite understand what it does. I have to try that.

The current power in iPads is pretty great. I enjoy Nomad Sculpt a lot.
Though I wasn’t really complaining about any lag in Nomad (it actually seems to work a lot better than a computer/computer 3D apps), but about the stroke curvature breaking when there is lag/high demand in processing.

I know; the topic just adapted from there from the original response I gave lol.

Adding pictures increases correct answers. Are we talking about this?

Did you try any of those tips above?
A bunch of people spent a part of their life time to help you.
They will help to avoid your issue, however you call it.
And yes, you are talking about lag in most cases.

My example above is not a result of a lag of performance though. Using the crease on a sphere is resulting in dots on the sphere outer sides.
It’s corresponding to the way brush machines usually are working.
Spacing defines the distance between each stamp of brush head.

The smaller the spacing the closer the stamps. If the spacing gets bigger even though it is set small, mostly a lag of computation is the reason. The computer can’t calculate fast enough each single brush head stamp, as the user moves the brush. The result are dotted lines, due to a lag of computation.

In rare cases the dotted lines are appearing even though the computer is fast enough, like in my example. When reaching the side of the sphere, the distance on object surface increases, while the stamping rate per moved distance on screen is static, the result are dots.

But as said, a rare case. But it is always about the rate of stamps compared to the distance the pencil is moved.
And mostly the computer lags to execute enough stamps compared to the distance the pencil is moved.
If you do very fast strokes, it is worse. The number of stamps is same but the time to calculate is getting very short compared to slow moves.

I don’t know exactly how each app is doing that. In old days you did a fast stroke in Photoshop with a brush in 1000px size, you sit up, you went to the coffee machine, cleaned it, bought some coffee in the supermarket, had a nice chat with some people, came back, fed the pet, made the coffee and bing!
There it was. A complete stroke!!

Believe me, you don’t want this behaviour in this millennium!

So I guess that some stamps are dropped when there is a calculation overload. The result are dotted lines caused by computation lag.

We tried to give you tools to reduce as much background calculation as possible to reduce the number of skipped stamps. :vulcan_salute:

I guess I got your point now.

This is a fast round stroke on a 6million poly sphere.
Anyway the reason is same, I would say.
When doing a stroke, the computer checks the position of the pencil in a specific rate. Too much to calculate will decrease this rate, in my example drastically. Instead of a curve consisting of lots of position points, only a few position points are executed and straight connected.


ARM has fewer instructions sets and centred toward power conservation and efficiency, wonder if this has anything to do with it versus x86 that would compute this all directly at expense of power gobbling and more numerous instructions running at once.

Yeah this. Not lag… lag it’s about the “mild delay” but I meant about the quality of the line not if it takes longer to be executed, going from curved to straight. I checked and at first I talked about the separation of the stamps in the line, I thought that was being affected at first but no, just the trajectory of the line, separation of the key points that make the line (though yeah, those are actually filled correctly with stamps).

I don’t know exactly how the tracking of the pencil (or finger) is technically recorded, if the amount of processing makes the tracking of the pencil to decrease I guess there is no way to avoid the straight line drawing curves, but I was guessing the problem was in another point in the app. I’ve seen apps (PC) where a line can really lag but maintains trajectory or where this happens… maybe even if the tracking of the stroke is inevitably broken some kind of line stabilization can be implemented?… though we already have 2 of those already :sweat_smile:.

I would actually might want that behavior sometimes… in old days, between a laggy app that made a nice curve and another app making a quicker but inaccurate stroke, I just might prefer the first option, the second being kind of a deal breaker of my evaluation of the quality of the app for drawing. Not really the case of nomad as it just happens when asking too much from the app, but the stroke breaking reminds me of that “low quality drawing apps”.

It never happened to me before and will never happen here again.
It is easy to avoid.

Interesting fact: smaller stroke spacing value produces more segmented line. Bigger values gives more curvy line but more visible “points”, but those can be corrected with the pinch tool pass.

1 Like