fabi/Xenia-Canary
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[UI] Android surface [skip appveyor]

Browse Source
This commit is contained in:
Triang3l
2022-02-01 22:18:04 +03:00
parent c6fc8f706a
commit 413d7ded49
14 changed files with 369 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/xenia/ui/presenter.cc
View File

@@ -26,13 +26,13 @@
// presenting from the thread refreshing the guest output is not absolutely
// necessary, but still may be nice for bypassing the scheduling and the
// message queue.
// On GTK, the frame rate of draw signals is limited to the display refresh rate
// internally, so for the lowest latency especially in case the refresh rates
// differ significantly on the guest and the host (like 30/60 Hz presented to
// 144 Hz), drawing from the guest output refreshing thread is highly desirable.
// Presenting directly from the GPU emulation thread also makes debugging GPU
// emulation easier with external tools, as presenting in most cases happens
// exactly between emulation frames.
// On Android and GTK, the frame rate of draw events is limited to the display
// refresh rate internally, so for the lowest latency especially in case the
// refresh rates differ significantly on the guest and the host (like 30/60 Hz
// presented to 144 Hz), drawing from the guest output refreshing thread is
// highly desirable. Presenting directly from the GPU emulation thread also
// makes debugging GPU emulation easier with external tools, as presenting in
// most cases happens exactly between emulation frames.
DEFINE_bool(
host_present_from_non_ui_thread, true,
"Allow the GPU emulation thread to present the guest output to the host "