We encountered a Touch(Devices Windows) bug several times on different devices (Surface Pro, Acer Touchmonitor, Dell All-in-One) which is really hard to pinpoint and reproduce…but its there. And its fatal.
At some point, some touches just hang and will never be deleted. sometimes the node can’t cope with that and crashes completely.
In comparison the WindowsTouch plugin never does this on the same hardware.
Ok, i had a look at the touch devices code and hell, there is so much stuff going on, saving touch events to lists etc. Probably hard to fix this…
I’ll keep using the windowstouch plugin for now since i don’t want some more teamviewer remote fixing.
guess: sort of reliable way of crashing the node was cleaning the screen with a towel ;). what if the window api send rubbish for one frame and giving your node with all the var’s and lists a headache. more touches than possible hardware touches results in windows api hickup and takes the touch node to hell ? i dunno.