Motion controls mainly for Windows handhelds #610
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "SomeoneIsWorking/feat/sdl3-handheld-gyro"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What is this: Motion input for devices such as ASUS ROG Ally without emulating another type of controller.
How it works: Using SDL3 device sensors instead of relying on controller sensors.
Does it work: Well... It's not perfect. The aiming is a bit off but for example for games that use flick motions (ie: hat throwing), it should cover all your needs.
Alternatively I was in the process of making a separate software using SDL3 that works as a CemuHook emitter but it's not done.
I failed the first time then decided to borrow CemuHook code from Ryujinx to handle the protocols but never got around to finishing it.
The "previous" Ryujinx staff decided against merging this because this makes the project use both SDL2 and SDL3 which is not ideal and also SDL3 wasn't fully released yet.
I decided to open this PR not with the goal of getting it merged but if there is anyone interested in it then they will know there is some work towards this and they can download this, play around, maybe got it working better, not sure.
Download the artifacts for this pull request:
Only for Developers
I'd prefer if this is delayed until we properly support only SDL3.
Much like the original team, I am very much against relying on 2 different versions of the same library; especially when it's not needed and one of the SDLs is used for a niche purpose (such as allowing motion on handhelds)
2 different SDLs, as a result, 2 SDL DLLs (or .SO or .dylib) exist in the result app folder; one of which for an insanely niche use, is not great.
Checkout
From your project repository, check out a new branch and test the changes.