17 Commits

Author	SHA1	Message	Date
cathery	a4c6008ce7	Increase controller threads again	2020-03-26 06:12:04 +03:00
cathery	7cab2e1e89	Update libnx and libstratosphere	2020-03-21 00:29:53 +03:00
cathery	c91bcd9e26	Remove old code	2020-03-13 13:46:12 +03:00
cathery	4cd616570f	Roll back some safety checks	2020-03-13 13:38:32 +03:00
cathery	2042d65935	Increase the controller threads' priority	2020-03-12 17:47:41 +03:00
cathery	393263eb7c	update thread priorities	2020-03-11 02:22:36 +03:00
cathery	37179d3d02	Remove redundant CancelSynchronization calls	2020-03-11 01:17:14 +03:00
cathery	b7d6da217a	Update libstratosphere and use master libnx	2020-03-10 21:22:21 +03:00
cathery	6898d056d4	while {} -> do {} while ... It makes more sense that all threads check if they can still run after they've completed their cycle, not before it	2020-03-02 18:21:40 +03:00
cathery	efaa2a6791	Use ams::StaticThread instead of SwitchThread in SwitchVirtualGamepadHandler	2020-02-20 03:27:19 +03:00
cathery	0efde144e5	Fix the static assertion check	2020-01-25 01:43:10 +03:00
cathery	f59352bee3	Add a static assertion for correct joystick values	2020-01-25 01:41:11 +03:00
cathery	bde2cfa2b0	Fixed another joystick value edge case ... Joystick values of -32768 and lower cause Resident Evil 4 to crash	2020-01-25 01:17:20 +03:00
cathery	033b9abece	Remove unnecessary bound checks since this was a one-off error ... Thanks libnx	2020-01-24 02:03:52 +03:00
cathery	bbed9abf55	Clamp joystick values when dpad and lstick are swapped ... They will now fit inside the circle like regular sticks	2020-01-24 01:39:36 +03:00
cathery	c7c5c42ae8	Fix joystick values going out of bounds ... Joystick value of 32768 (0x8000) causes games like Xenoblade 2 to crash under failed assertions. Even though it should be within range of acceptable joystick values.	2020-01-24 01:38:10 +03:00
cathery	60c861c0a2	Re-organize the project	2020-01-12 05:01:44 +03:00