Closed truboxl closed 2 years ago
LIBGL_FB
Controls the Framebuffer output
0 : Default, using standard x11 rendering 1 : Use Framebuffer output (x11 bypassed, only fullscreen) 2 : Use Framebuffer, but also an intermediary FBO 3 : Use PBuffer, allowing x11 (and windowed) rendering even if driver doesn't support it
Android graphics driver has never been designed for X11, so mode 0 it wouldn’t work. PBuffer should work by copying each frame from an offscreen framebuffer to the X11 window.
EDIT: I have looked at the code and found that gl4es uses pixmap for LIBGL_FB=3, which Android doesn’t support. Replacing pixmap with something similar should get it to work.
I feel like we are so near yet so far away from driving actual hardware accelerated X11 graphics... Guess fixing LIBGL_FB=3 is the way forward huh...
Problem description
The current gl4es is a stub. I am not sure how somebody can get it working without symbol error like in https://github.com/termux/x11-packages/pull/373#issuecomment-913045821
I only managed to fix it up until it
renderslogs something but still black screen. Likely a major overhaul needed in gl4es to support Android X11 hybrid...And no... Proot doesn't work... We are talking real hardware acceleration. Check glxinfo and make sure you aren't using VMware or llvmpipe rendering...
What steps will reproduce the bug?
What is the expected behavior?
I only managed to fix until here, still black screen... More work is needed... Everything is done using VNC...
Below is logs for
glxinfo
andglxgears
usingLIBGL_FB=
0, 1 and 2 respectively...gl4es is obviously doing something in the thousand FPS range unlike Mesa hundred FPS range...
Unfortunately the error message is not in sequence, they all end up move to top for whatever reason when trying to collect logs...
System information