NodeBrowser input lag

Noticed this in 5.2 and also in current 5.3 previews …
Intelligent Node Filtering is off.

I was under the suspicion that this happens at arbitrary moments, but when trying to reproduce it and maybe find a pattern, it now was showing always when spawning the NodeBrowser by doubleclicking an existing node.

I also added some typing reference speed in the beginning because the Keyboard/Mouse visualiser wouldn’t show regular keyboard typing.

towards the end, when I go into the “top level” of the node browser and you see just the “r” for a long while, I experienced an extra long lag.

1 Like