yuzu - Nintendo Switch emulator archive

	Commit message (Collapse)	Author	Age	Files	Lines
*	UI: Relocate tas menu and add brief description	german77	2021-09-18	1	-32/+56
\|
*	input_common/tas: Document the main class	german77	2021-09-18	1	-1/+2
\|
*	input_common/tas: Add swap controller	german77	2021-09-18	1	-7/+56
\|
*	input_common/tas: overwrite file dialog	german77	2021-09-18	1	-16/+3
\|
*	input_common/tas: Fallback to simple update	MonsterDruide1	2021-09-18	1	-23/+24
\|
*	config: Move TAS options to it's own menu	german77	2021-09-18	1	-84/+105
\|
*	core: Hacky TAS syncing & load pausing	MonsterDruide1	2021-09-18	1	-55/+87
\| \| \| \| \| \| \| \|	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.
*	input_common/tas: Base playback & recording system	MonsterDruide1	2021-09-18	1	-0/+340
	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>