ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
radu242 has quit [Remote host closed the connection]
radu242 has joined #wayland
martin19_ has joined #wayland
martin19 has quit [Read error: Connection reset by peer]
damjan has quit [Quit: bye]
Lucretia has quit []
damjan has joined #wayland
columbar1 has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
hegstal has quit [Remote host closed the connection]
columbarius has joined #wayland
columbar1 has quit [Ping timeout: 480 seconds]
soreau has quit [Quit: Leaving]
soreau has joined #wayland
aquijoule_ has joined #wayland
richbridger has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
blue__penquin has joined #wayland
NoGuest17 has quit [Remote host closed the connection]
NoGuest17 has joined #wayland
spstarr has joined #wayland
tzimmermann has joined #wayland
dcz has joined #wayland
martin19_ has quit [Ping timeout: 480 seconds]
newbie has joined #wayland
fltrz has joined #wayland
hardening has joined #wayland
jgrulich has joined #wayland
juergbi has quit []
<fltrz>
Im having trouble getting example 3 different example skeleton applications to run VSYNCed and render a triangle. I can get the VSYNCed hello-wayland-opengl-render-loop to work, but get errors trying to createVertexShader (returns 0), I also tried getting the open.gl example application (which uses GLEW) and succeed in getting a rectangle displayed, but then its not VSYNCed, and I also tried "propella" 's triangle_simple.c , but it fails
<fltrz>
assertion on global.shells
juergbi has joined #wayland
<kennylevinsen>
fltrz: maybe your vertex shader is broken?
pnowack has joined #wayland
audgirka has joined #wayland
blue__penquin has quit [Quit: Connection closed for inactivity]
martin19 has joined #wayland
danvet has joined #wayland
immibis has joined #wayland
<fltrz>
the problem occurs before vertexshader, at glCreateShader(GL_VERTEX_SHADER)
<fltrz>
kennylevinsen, I'm really considering just using the glxgears.c from mesa's xdemos dir, it runs vsynced and displays quads
immibis has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
sozuba has joined #wayland
Lucretia has joined #wayland
<kennylevinsen>
fltrz: you can take the opengl from there - it works the same.
<kennylevinsen>
but maybe you're calling glCreateShader before the EGL context is created and made current? :/
<daniels>
weston-simple-egl is generally the most bulletproof one to use
<daniels>
which platform (in particular GPU/display drivers) are you on, and which compositor are you using?
<gitlab-bot>
wayland issue 54 in wayland-protocols "Add flag in linux-dmabuf-unstable-v1.xml to indicate secure buffer" [Linux-Dmabuf, Opened]
sozuba has quit [Quit: sozuba]
blue__penquin has joined #wayland
<pq>
yaay, nice to see wlb :-)
aleasto has joined #wayland
martin19 has quit [Ping timeout: 480 seconds]
aleasto has quit [Read error: Connection reset by peer]
aleasto has joined #wayland
<fltrz>
no, wasn't creating the EGL context before making current, as it was the same skeleton hello-wayland renderloop branch
<fltrz>
anyway, I just went oldskool fixed pipeline, and now happily drawing quads, with glOrtho & glVertex2i, since I need pixel perfect checkerboards
<pq>
fltrz, that sounds a lot like you were trying to call a gl function before making the context current.
<gitlab-bot>
wayland issue 513 in weston "subsurface-shot and yuv-buffer leaks in GL (Follow-up from "More leak fixes in tests, reported by ASan")" [Gl Renderer, Opened]
hegstal has joined #wayland
<pq>
fltrz, welcome to GL ES.
<fltrz>
thanks, I just fixed the shader
<fltrz>
thats the kind of trouble I get for duct-taping different tutorials together
<gitlab-bot>
wayland issue 56 in wayland-protocols "Document security considerations of protocols" [Opened]
cedric has quit []
tzimmermann has quit [Quit: Leaving]
cedric has joined #wayland
cedric is now known as bluebugs
Narrat has joined #wayland
jgrulich has quit [Ping timeout: 480 seconds]
Guest656 has quit [Remote host closed the connection]
aleasto has quit [Ping timeout: 480 seconds]
aleasto has joined #wayland
blue__penquin has quit [Quit: Connection closed for inactivity]
aleasto has quit [Ping timeout: 480 seconds]
eck has quit [Quit: PIRCH98:WIN 95/98/WIN NT:1.0 (build 1.0.1.1190)]
eck has joined #wayland
nerdopolis has joined #wayland
st3r4g has joined #wayland
aleasto has joined #wayland
immibis has joined #wayland
<fltrz>
pq, kennylevinsen I was thinking, for the problem I had, calling glFunctions before eglMakeCurrent, that sounds like something the -legl -lgles etc libraries could detect and error message about
dcz has quit [Ping timeout: 480 seconds]
aleasto has quit [Remote host closed the connection]
<soreau>
it might say something if you use debug version of mesa or set MESA_DEBUG but mesa isn't the only impl of these
hegstal has quit [Remote host closed the connection]
rasterman has quit [Quit: Gettin' stinky!]
mixfix41_ has joined #wayland
Narrat has quit []
mixfix41 has quit [Ping timeout: 480 seconds]
hardening has quit [Ping timeout: 480 seconds]
danvet has quit [Ping timeout: 480 seconds]
spstarr has quit [Remote host closed the connection]