yuzu-mainline/src/yuzu_tester, branch master A backup of the Yuzu mainline repo. Only includes the master branch, nothing else. cmake: Remove yuzu_tester 2021-01-15T06:14:44+00:00 ReinUsesLisp reinuseslisp@airmail.cc 2021-01-15T06:04:37+00:00 af540b00573e8c6b935289873ba624ecf81002ce We never ended up using yuzu_tester. Removing it saves code duplication with yuzu_cmd, and distribution size on prebuilt packages. For unit testing, we can use catch2 from guest code and dump the results to a file. Then execute yuzu from a script on ci if we want this to be automated. 
We never ended up using yuzu_tester.
Removing it saves code duplication with yuzu_cmd, and distribution size on
prebuilt packages.

For unit testing, we can use catch2 from guest code and dump the results
to a file. Then execute yuzu from a script on ci if we want this to be
automated.
config: Enable docked mode by default 2021-01-10T14:37:38+00:00 Morph 39850852+Morph1984@users.noreply.github.com 2021-01-10T14:37:38+00:00 05f58144c93585423d9622e5b71ae4510d0b839a 






general: Fix various spelling errors
2021-01-02T15:23:41+00:00

Morph
39850852+Morph1984@users.noreply.github.com

2021-01-02T14:00:05+00:00

a745d87971b2c9795e1b2c587bfe30b849b522fa












yuzu: Remove gdbstub configuration
2020-12-19T18:19:42+00:00

FearlessTobi
thm.frey@gmail.com

2020-12-19T18:19:42+00:00

10b0ab792681b27664030d53d8e1ff610d0010cf

The gdbstub itself was removed with https://github.com/yuzu-emu/yuzu/pull/5028.
This PR just removes the remaining gdb configuration code from the emulator and the UI.





The gdbstub itself was removed with https://github.com/yuzu-emu/yuzu/pull/5028.
This PR just removes the remaining gdb configuration code from the emulator and the UI.







core: Eliminate remaining usages of the global system instance
2020-11-27T16:40:45+00:00

Lioncash
mathew1800@gmail.com

2020-11-27T15:50:48+00:00

5bc4eabe36b7ef4dcd5ad8db1e944705655be432

Removes all remaining usages of the global system instance. After this,
migration can begin to migrate to being constructed and managed entirely
by the various frontends.





Removes all remaining usages of the global system instance. After this,
migration can begin to migrate to being constructed and managed entirely
by the various frontends.







service: Eliminate usages of the global system instance
2020-11-27T01:03:11+00:00

Lioncash
mathew1800@gmail.com

2020-11-26T20:19:08+00:00

1a954b2a596fdfd4fc4b5feb9b43c8147de4cc7f

Completely removes all usages of the global system instance within the
services code by passing in the using system instance to the services.





Completely removes all usages of the global system instance within the
services code by passing in the using system instance to the services.







Merge pull request #4976 from comex/poll-events
2020-11-25T23:44:53+00:00

Rodrigo Locatti
reinuseslisp@airmail.cc

2020-11-25T23:44:53+00:00

0e15c68f54ae5217e6247603b9e31757515f89e1

Overhaul EmuWindow::PollEvents to fix yuzu-cmd calling SDL_PollEvents off main thread




Overhaul EmuWindow::PollEvents to fix yuzu-cmd calling SDL_PollEvents off main thread






Overhaul EmuWindow::PollEvents to fix yuzu-cmd calling SDL_PollEvents off main thread
2020-11-23T22:58:49+00:00

comex
comexk@gmail.com

2020-11-22T21:05:18+00:00

994f4977810749c0b597e7a7531a02d907967a68

EmuWindow::PollEvents was called from the GPU thread (or the CPU thread
in sync-GPU mode) when swapping buffers.  It had three implementations:

- In GRenderWindow, it didn't actually poll events, just set a flag and
  emit a signal to indicate that a frame was displayed.

- In EmuWindow_SDL2_Hide, it did nothing.

- In EmuWindow_SDL2, it did call SDL_PollEvents, but this is wrong
  because SDL_PollEvents is supposed to be called on the thread that set
  up video - in this case, the main thread, which was sleeping in a
  busyloop (regardless of whether sync-GPU was enabled).  On macOS this
  causes a crash.

To fix this:

- Rename EmuWindow::PollEvents to OnFrameDisplayed, and give it a
  default implementation that does nothing.

- In EmuWindow_SDL2, do not override OnFrameDisplayed, but instead have
  the main thread call SDL_WaitEvent in a loop.





EmuWindow::PollEvents was called from the GPU thread (or the CPU thread
in sync-GPU mode) when swapping buffers.  It had three implementations:

- In GRenderWindow, it didn't actually poll events, just set a flag and
  emit a signal to indicate that a frame was displayed.

- In EmuWindow_SDL2_Hide, it did nothing.

- In EmuWindow_SDL2, it did call SDL_PollEvents, but this is wrong
  because SDL_PollEvents is supposed to be called on the thread that set
  up video - in this case, the main thread, which was sleeping in a
  busyloop (regardless of whether sync-GPU was enabled).  On macOS this
  causes a crash.

To fix this:

- Rename EmuWindow::PollEvents to OnFrameDisplayed, and give it a
  default implementation that does nothing.

- In EmuWindow_SDL2, do not override OnFrameDisplayed, but instead have
  the main thread call SDL_WaitEvent in a loop.







core: Make use of [[nodiscard]] with the System class
2020-11-18T07:06:44+00:00

Lioncash
mathew1800@gmail.com

2020-11-18T07:06:42+00:00

bcaadac22ca8a7320a46644e8199ef333edce8e9

Given this is a central class, we should flag cases where the return
value of some functions not being used is likely a bug.





Given this is a central class, we should flag cases where the return
value of some functions not being used is likely a bug.







configure_input: Add per-player vibration
2020-11-16T04:33:20+00:00

Morph
39850852+Morph1984@users.noreply.github.com

2020-10-17T13:38:12+00:00

38110dd485e329fa39e2e4c02b91a89dfebcbc88

Allows for enabling and modifying vibration and vibration strength per player.
Also adds a toggle for enabling/disabling accurate vibrations.

Co-authored-by: Its-Rei <kupfel@gmail.com>





Allows for enabling and modifying vibration and vibration strength per player.
Also adds a toggle for enabling/disabling accurate vibrations.

Co-authored-by: Its-Rei <kupfel@gmail.com>