dorky hacking stuff and 
glitches / 
\ she/her / loves people more than tech \ PhD @vu5ec / breaks things \ collects NDAs and lengthy embargoes 
U tweetove putem weba ili aplikacija drugih proizvođača možete dodati podatke o lokaciji, kao što su grad ili točna lokacija. Povijest lokacija tweetova uvijek možete izbrisati. Saznajte više
If I dump a printf in the text-writing function then I can see that it's executing code and trying to display happy messages, but I guess something is going wrong in these 1000 lines of OpenGL code which I copied without thinking about. Let's, uhm, *rolls dice*, try valgrind.
Doing random stuff was fail; tried apitrace. It views OpenGL calls/state, didn't help. More success by replacing shaders with stubs. Text shader doesn't appear unless I hardcore its texture id. Not sure if correct, "debugging" continues. (yes, I am too sick to do real work 
)
Have you looked at renderdoc? It allows inspecting the gl pipeline and intermediate values between its stages
It looked indeed like a better tool but it didn't like capturing my code despite afaict only using OpenGL 3.2 and not old compact stuff (which is a requirement for renderdoc). Maybe I'll grab the source and try to work out what goes wrong..
shaders were a curse!
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
but I'm sure if I keep doing Random Horrible Coding Hackery™ something exciting is bound to happen eventually.
