CasperH2O

DS4 IMU timestamp has been replaced with the same timestamp used for GamePadMotionHelpers, to be restested.

Initial fix and rework done in EA branch, to be tested in practice.

Unable to reproduce, fix holds.

No response from original issue creator. Unable to reproduce myself on ROG Ally.

Included this in the Inno Setup improvement spec to be done.

It seems that even when stopping the 3 RTSS related process that can be found in the Task Manager, this problem still occurs. Tested with RTSS 7.3.5.

Has been fixed by using a fork of WPF with newer features and bugfixes. Leaving this open for now until we can use the formal WPF library again.

This has been fixed with WPF fork we are now using. I have subscribed to the original ticket so that we can remove the workaround once it has been fixed...

User reported having this issue with 0.20.5.4, right after waking from hibernate (or sleep?) on a Legion Go. Error: ``` 2024-04-03 14:08:19.567 +02:00 [FTL] The calling thread cannot access this...

Should be worthwhile to retest with the updating UI PR currently in EA. Pretty sure I've seen this issue myself also.