| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| | |
Port #3353 from Citra: "citra-qt: Add customizable speed limit target "
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
| |
25us is far too small, and would result in std::this_thread::sleep_for
being called with this as a maximum value. This means that a guest
application that produces frames instantly would only be limited to
40 kHz.
25ms is a more appropriate value, as it allows for a 60 Hz refresh
rate while providing enough slack in the negative region.
|
| |
|
|
|
| |
ms is shorthand for milliseconds, not microseconds, and given there's no
comment indicating that this was intentional, it probably wasn't.
|
| |
|
|
|
| |
Enforces the time unit being returned and also allows using the standard
time utilities to manipulate it.
|
| |
|
|
|
| |
C++17 adds clamp() to the standard library, so we can remove ours in
favor of it.
|
| |
|
|
| |
Adds in a missing EndGameFrame when nvdrv swaps buffers
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Now based on std::chrono, and also works in terms of emulated time
instead of frames, so we can in the future frame-limit even when the
display is disabled, etc.
The frame limiter can also be enabled along with v-sync now, which
should be useful for those with displays running at more than 60 Hz.
|
| |
|
|
| |
More ergonomic to use and will be required for upcoming changes.
|
| | |
|
| |
|
