c4760489a0
input_common: Fix SDL controller with inverted axis
4 years ago
42949738f2
kraken: Address comments from review
Fix compiler bug
4 years ago
f4e5f89e6f
core/hid: Improve accuary of mouse implementation
4 years ago
654d76e79e
core/hid: Fully implement native mouse
4 years ago
bca299e8e0
input_common: Allow keyboard to be backwards compatible
4 years ago
b673857d7d
core/hid: Improve accuracy of the keyboard implementation
4 years ago
c35af8d1c0
input_common: Fix motion from 3 axis
4 years ago
157e0b85fd
core/hid: Prevent Emulated controller from flapping with multiple inputs devices
4 years ago
136eb9c4c2
core/hid: Fully emulate motion from button
4 years ago
77fa4d4bf6
second commit lion review
4 years ago
730f078302
settings: Fix Debug controller type options
4 years ago
2b1b0c2a30
kraken: Address comments from review
start lion review
4 years ago
61d9eb9f69
input_common: Revert deleted TAS functions
4 years ago
d8e3f2b10b
input_common: Fix GC adapter initialization
Fix GC controller
4 years ago
1d71d4b874
input_common: Fix UDP uuid
4 years ago
7348e205d9
input_common: Add multiple vibration curves
4 years ago
064ddacf49
core/hid: Rework battery mappings
4 years ago
c6c32daf40
input_common: Add manual update options to input devices
4 years ago
464c4d26ac
settings: Fix mouse and keyboard mappings
4 years ago
b5e72de753
kraken: Address comments from review
review fixes
4 years ago
85052b8662
service/hid: Fix gesture input
4 years ago
af55dd1935
configuration: Migrate controller settings to emulated controller
4 years ago
c3ff0a8ac0
core/hid: Fix rumble too strong at 1%
4 years ago
601ac43495
core/hid: Only signal when needed
4 years ago
e0da5c1bbc
kraken: Fix errors from rebase and format files
4 years ago
06a5ef5874
core/hid: Add output devices
4 years ago
29ae42f3e2
input_common: Rewrite main and add the new drivers
4 years ago
6d108f0dcb
input_common: Remove obsolete files
4 years ago
59b995a9e5
input_common: Rewrite SDL
4 years ago
10241886dd
input_common: Rewrite udp client
4 years ago
dc3ab9e110
input_common: Rewrite tas input
4 years ago
395e9a449d
input_common: Rewrite gc_adapter
4 years ago
fa8e23b842
input_common: Rewrite touch
4 years ago
00834b84dd
input_common: Rewrite mouse
4 years ago
5a785ed794
input_common: Rewrite keyboard
4 years ago
4c6f2c2547
input_common: Move touch and analog from button. Move udp protocol
4 years ago
854c933716
input_common: Create input poller and mapping
4 years ago
ea7b1fbc67
input_common: Create input_engine
4 years ago
33e92c15eb
Revert "input_common: Fix data race on GC implementation"
4 years ago
b01aa721ff
input_common: Fix VS2022 compilation errors
4 years ago
8212a864ca
input_common/sdl: Fix joystick range
4 years ago
73666fb262
general: Update style to clang-format-12
4 years ago
75d8ec1e9f
UI: Relocate tas menu and add brief description
4 years ago
33a1d790e8
input_common/tas: Document the main class
5 years ago
e6c4bf52f0
input_common/tas: Add swap controller
5 years ago
9bb6580d89
input_common/tas: overwrite file dialog
5 years ago
f078b15565
input_common/tas: Fallback to simple update
5 years ago
c01a872c8e
config: Move TAS options to it's own menu
5 years ago
4297d2fea2
core: Hacky TAS syncing & load pausing
To keep the TAS inputs synced to the game speed even through lag spikes and loading zones, deeper access is required.
First, the `TAS::UpdateThread` has to be executed exactly once per frame. This is done by connecting it to the service method the game calls to pass parameters to the GPU: `Service::VI::QueueBuffer`.
Second, the loading time of new subareas and/or kingdoms (SMO) can vary. To counteract that, the `CPU_BOOST_MODE` can be detected: In the `APM`-interface, the call to enabling/disabling the boost mode can be caught and forwarded to the TASing system, which can pause the script execution if neccessary and enabled in the settings.
5 years ago
b42c3ce21d
input_common/tas: Base playback & recording system
The base playback system supports up to 8 controllers (specified by `PLAYER_NUMBER` in `tas_input.h`), which all change their inputs simulataneously when `TAS::UpdateThread` is called.
The recording system uses the controller debugger to read the state of the first controller and forwards that data to the TASing system for recording. Currently, this process sadly is not frame-perfect and pixel-accurate.
Co-authored-by: Naii-the-Baf <sfabian200@gmail.com>
Co-authored-by: Narr-the-Reg <juangerman-13@hotmail.com>
5 years ago
german77