If you want to test if the latency is in the software of Wayland itself, you can just create a software emulated HID input device that generates the motion, and a script that registers movement and click. The control being the emulated HID device, and the variable being the different compositor. Start a script that moves for a predetermined amount of time and click, and just record the difference. It should perform the same way each and every time, unless something is slowing it down, no?
You went way too HAM on this lol.
If you want to test if the latency is in the software of Wayland itself, you can just create a software emulated HID input device that generates the motion, and a script that registers movement and click. The control being the emulated HID device, and the variable being the different compositor. Start a script that moves for a predetermined amount of time and click, and just record the difference. It should perform the same way each and every time, unless something is slowing it down, no?
deleted by creator