ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
kenny has joined #wayland
crazybyte has quit [Ping timeout: 480 seconds]
manuel_ has quit [Remote host closed the connection]
manuel_ has joined #wayland
crazybyte has joined #wayland
caveman has joined #wayland
cvmn has quit [Remote host closed the connection]
manuel_ has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
fmuellner has quit [Ping timeout: 480 seconds]
DragoonAethis has quit [Quit: hej-hej!]
DragoonAethis has joined #wayland
tawonga has quit [Quit: WeeChat 4.0.0]
jmdaemon has quit [Ping timeout: 480 seconds]
jmdaemon has joined #wayland
crazybyte has quit [Ping timeout: 480 seconds]
crazybyte has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
Company has quit [Quit: Leaving]
nehsou^ has quit [Remote host closed the connection]
pieguy128_ has joined #wayland
tawonga has joined #wayland
pieguy128 has quit [Ping timeout: 480 seconds]
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
tzimmermann has joined #wayland
Seirdy has quit [Ping timeout: 480 seconds]
<DodoGTA>
Can glXWaitForSbcOML() be called after glXSwapBuffersMscOML() when using XWayland?
<kennylevinsen>
DodoGTA: yes and it works, that issue just describes a scenario where glxWaitForSbcOML waits longer than it would on pure X.
Kerr has quit [Ping timeout: 480 seconds]
DodoGTA_ has joined #wayland
Kerr has joined #wayland
<DodoGTA_>
kennylevinsen: Unfortunately that behavior prevents the game from running with an unlimited framerate
rv1sr has joined #wayland
Kerr_ has quit [Ping timeout: 480 seconds]
DodoGTA_ has quit [Remote host closed the connection]
<kennylevinsen>
DodoGTA: the answer to the question remains yes though. A bit counterproductive to *wait* if you want "unlimited framerate"
<MrCooper>
basically, it's relying on other implementations cheating and reporting the swap as "completed" when it really hasn't
<MrCooper>
or maybe it actually meant to wait for the previous swap to complete, i.e. off-by-one bug
rasterman has joined #wayland
DodoGTA_ has joined #wayland
<DodoGTA_>
kennylevinsen: So that WaiForSbc call shouldn't be made if the swap interval is 0, right?
DodoGTA_ has quit [Remote host closed the connection]
<MrCooper>
DodoGTA: some WaiForSbc may make sense to prevent the CPU/GPU from getting too far ahead, just not for the very last swap :)
cmichael has joined #wayland
<pq>
swick[m], I see LittleCMS has added support for MHC2.
<kennylevinsen>
DodoGTA: they are not using swap interval, they are using the OML sync control extension. That allows you to specify the exact MSC (refresh) you want to swap or wait for, but iirc the issue is that they are waiting for the current MSC
fmuellner has joined #wayland
Kerr has quit [Read error: Connection reset by peer]
gildekel has quit [Quit: Connection closed for inactivity]
<MrCooper>
kennylevinsen: current SBC (SwapBuffers counter)