search

r57zone / DualShock4-emulator

DualShock4 emulation for Xbox controllers or keyboard and mouse / Эмуляция DualShock4 для Xbox контроллеров или клавиатуры и мыши
https://youtu.be/17hY1zTqoYQ
The Unlicense
189 stars 30 forks source link

[Feature Request] Extracting gyroscope data via android Phone #26

Closed hypostock closed 2 years ago

hypostock commented 2 years ago

I was wondering if gyroscope support can be added like how cemu does it

https://cemuhook.sshnuke.net/padudpserver.html

r57zone commented 2 years ago

Hi, interesting idea, I'll study it.

hypostock commented 2 years ago

Thanks. Any updates so far?

r57zone commented 2 years ago

I'll try in next release.

r57zone commented 2 years ago

Added in the new version for Android phones https://github.com/r57zone/DualShock4-emulator/releases

hypostock commented 2 years ago

ah nice.. i will test this out and let you know as soon as possible...

hypostock commented 2 years ago

Just tested this out and boy ... worked like a charm , sixaxis might be a bit too sensitive but that is adjustable.. congratulations. you may have made the best fully functional DS4 out there.

r57zone commented 2 years ago

Which game did you test this in? Are the phone axes correct?

hypostock commented 2 years ago

Ar Tonelico 3 for now, what happened there was that the phone reading changes were so sensitive... the moment i press one of the keys to initiate the purge sequence, it rapidly activates it. I didn't even had to press the button T to shake it artificically. i will test the axes on DS4windows to emulate and see the sixaxis and let you know.

hypostock commented 2 years ago

So, I tested the gyroscope sixaxis from both pressing the T button and the android phone. Two cases are occurring here.

1) On pressing the T button: the mouse would oscillate left and right... which is fine for shaking purposes. 2) However, for the android raw data. even when I am not turning the phone (it just lied there flat), the slight changes in the raw data(mostly because extreme precision) changes the entire sixaxis position.Also, the sixaxis coverage seems to be restricted to the 2nd quadrant only (ie from 0 to -x and 0 to +y).

This is what I have observed so far. So phone axes might need some expansion to the remaining quadrants and a range expansion(divide by n) by having the option to divide the values even further so that slight changes does not drastically affect the sixaxis postion. Then I would be able to make a good observation for the phone axes.

r57zone commented 2 years ago

Added sensitivity changes in the latest release https://github.com/r57zone/DualShock4-emulator/releases