-
-
Notifications
You must be signed in to change notification settings - Fork 335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vkcube framerate in latest version of termux-x11 #774
Comments
Can I please ask you to check which commit causes this? I mean checking artifacts in Actions tab. |
@twaik I installed and tested the above version. |
It is the latest available version. |
@twaik How can I explain it to you? If you tell me the procedure, I will comment right away. |
I mean can you please check CI runs one by one in chronological order (probably starting with the artifact from two weeks ago) and tell me when the problem starts to be reproducible? |
@twaik Please wait a moment. |
@twaik The symptom occurs starting from the build below! https://github.com/termux/termux-x11/actions/runs/12471770069 |
It is sad. This commit fixes mesa and angle frame sync. |
@twaik Tested on the latest build of |
@xMeM can you please take a look at what exactly may go wrong? |
It should be Success instead of TRUE ?
|
You are right. I do not know how I missed it. |
@twaik
2024_12_30.22_06.mp4
|
High result is probably because of dropping the frames which are not going to be displayed. So the driver works correctly. |
Problem description
The latest version of
Termux-X11
has fixed allX11 server
performance issues onSamsung Exynos devices
usingANGLE EGL
.However, when running
vkcube
,I noticed that it is showing an abnormally fast frame rate.
It is the same frame rate as when I added the
MESA_VK_WSI_PRESENT_MODE=mailbox
environment variable and ran it.Is this the intended behavior?
If it is the intended behavior,
Is there an environment variable or option that can make it show the normal frame rate as before?
What steps will reproduce the bug?
2024_12_25.03_18.mp4
What is the expected behavior?
No response
The text was updated successfully, but these errors were encountered: