Patreon 0.28.1.4 - Wake & Play

ver. 0.28.1.4 On the Legion Go 2, the program cannot be configured from the start because it shows a message saying that no physical controller can be found. (The program was newly installed on this device with no previous settings saved, and both controllers are attached to the main body.)

ver. 0.28.1.4 (Issue) Gyro Control : Gyro aiming behaves inversely (fast rotations cause less movement instead of more) ⸻ ** Issue Summary ** When aiming with the gyro, the cursor movement depends on rotation speed — fast rotations result in less movement, while slow rotations cause the cursor to travel farther. This behavior is inverted and inconsistent with normal gyro aiming or mouse input. (For example, in an FPS game, when you try to quickly aim at an enemy using the gyro, the faster you rotate, the slower the aiming becomes — causing the crosshair to lag behind and fail to reach the target in time. In extreme cases, when rotating very quickly, the crosshair barely moves at all and remains almost stationary.) ⸻ ** Expected Behavior ** Gyro aiming should behave like a mouse with zero acceleration — cursor movement should depend only on the total rotation angle, not rotation speed. In other words: • Fast rotation → same angular distance → same cursor movement • Slow rotation → same angular distance → same cursor movement Just like mouse movement with acceleration disabled (acceleration = 0), gyro input should maintain a consistent 1:1 relationship between physical rotation and cursor displacement, regardless of motion speed. ⸻ ** Possible Causes ** • Excessive smoothing or filtering applied to gyro input • Frame-rate dependent sampling (missed samples during fast motion) • Over-aggressive drift compensation treating high-speed motion as noise ⸻ ** Suggested Actions ** Please check whether: • Gyro input is being excessively smoothed or filtered • Rotation delta (angular change) is being applied frame-rate independently • High angular velocities are being clamped, capped, or ignored ⸻ ** Proposed Solution ** The gyro aiming system should behave like a mouse with acceleration disabled (acceleration = 0) — cursor movement must depend solely on rotation angle, not rotation speed. In other words, the system should maintain a consistent, linear 1:1 response, where the same rotation always results in the same cursor movement, just as a non-accelerated mouse does regardless of how fast it moves. This is the standard across all major gyro implementations — Nintendo Switch, PS5 DualSense, Steam Input, and DS4Windows — all of which integrate angular motion uniformly over time, independent of frame rate or motion speed. (All major gyro systems follow the same principle as stated in their official documentation: gyro sensors output angular velocity (deg/s), and developers integrate this value over time (gyro * deltaTime) to calculate the rotation angle change. In other words, while the input is velocity-based, the resulting motion is frame-rate independent and provides a consistent angular displacement.)

ver. 0.28.1.2 (issue) GPD WIN MINI 2025 I haven’t confirmed yet whether this issue is specific to the WIN Mini or a common issue across other devices. * (Intermittent) After resuming from hibernation, the custom fan curve settings are not applied and the system runs with the default hardware fan curve instead. reapplying the custom fan curve in Handheld Companion does not fix it — I need to close and restart Handheld Companion for it to take effect.

0.28.1.4 fixes endless loading on initialization.

hello i tried to install it on lego2, after reboot i tried to launch it i stay stuck on hc splash loading screen , any idea ? thanks