chewitt has quit [Read error: Connection reset by peer]
chewitt_ has joined #lima
monstr has joined #lima
smaeul has quit [Ping timeout: 264 seconds]
chewitt_ is now known as chewitt
yann has joined #lima
uis has joined #lima
<linkmauve>
enunes, here we’ll be less interrupted.
yann has quit [Ping timeout: 260 seconds]
<enunes>
linkmauve: sure
<linkmauve>
enunes, when I start gtk4-demo with GDK_DEBUG=gl-gles, it does run, even though it’s a lot slower than using cairo.
<linkmauve>
gears reports 8.5 fps.
<linkmauve>
And the clocks shadertoy looks totally broken in the Transitions and Effects demo.
<linkmauve>
The bottom right one is expectedly broken on GLES, as it currently asks for GLSL 150.
<linkmauve>
This window takes almost no CPU, like 2%, it’s probably bottleneck’d hard by the GPU.
uis has quit [Ping timeout: 256 seconds]
<enunes>
linkmauve: I wonder if profiling shows anything? I might do that first if I set up an environment to build gtk again
<linkmauve>
I’m doing that atm, gtk_icon_cache_list_icons_in_directory() is by far the function in which it spends the most time at startup…
<linkmauve>
enunes, I brought that up to #gtk btw.
yann has joined #lima
uis has joined #lima
<enunes>
linkmauve: GDK_DEBUG=gl-gles seems to still be available only on gtk debug builds, is there a way to use gles2 for regular distribution builds?
<enunes>
"gl-gles" is only available when building GTK with G_ENABLE_DEBUG. See GDK_DEBUG=hel
<linkmauve>
I didn’t even know I built a debug build. :x
<linkmauve>
Maybe that’s why it’s slow?
<enunes>
it was one of the things I complained about in that issue report, as it's a debug only option I'm not sure even if gtk4 planned to support gles2 in general
<enunes>
I didnt build it myself yet just picked from the distribution where the latest is gtk4-devel-4.0.3-1.fc33.aarch64
<linkmauve>
Probably we can make it fallback to GLES if it can’t get a GL 2.1 context.
<linkmauve>
Once we know that GLES does work.
<linkmauve>
(Which it seems, even though it’s so much slower than cairo here.)
<enunes>
even just having the env var would be helpful, the distribution people are already setting a bunch of vars to make stuff fallback to gles2 anyway
<enunes>
yeah without that all i get is 'unable to create a GL context'
monstr has quit [Remote host closed the connection]