but usually you have `glEnable` and `glDisable` their functionality
but usually you have
glEnable and glDisable their functionality
P(if they change the spec in a significant way)
Qthis one specific one isn't always supported.
GL_ARB_timer_queryPyeah so just do
gl.TryGetExtension(out ArbTimerQuery tq)
DYes, but if it is supported it will automatically be activated
Prefer to my original point. if it's supported, it can't just go changing the spec willy nilly without the user knowing as that'd be massively problematic.
Pbut you can assume that if it's supported you can use any of its functionality without any extra steps
Qin that case it just isn't supported. Fine.
DOh yeah, but you know how it is for Vulkan.
Pofc
DPbut yeah use TryGetExtension as outlined above. if that returns true,
tq contains the commands you want to use.Pworth noting that this extension is core in 3.2
Pso you should check both the opengl version and the extension
Pas an implementation is theoretically free not to report support for the extension even if it implements 3.2
DWhat the fuck
DGotta love OpenGL rules
Qdoesn't matter - I was just trying to measure some stuff, but works without that just as well. Actually just trying to debug why Silk.NET.Windowing makes NVG rendering this:
And yes, I'll look at it in renderdoc later - just thought it looks funny
And yes, I'll look at it in renderdoc later - just thought it looks funny
Pfor the love of god please fix that cancle typo
Plmfao
Palso what's gone wrong with windowing?
QNO! I prefer this spelling and otherwise my existance would be ruined...
P.....but it's an invalid spelling
Pit is not a word
Qbetter?
Pmuch
Qthis is with GLFW
Pbut yeah what's windowing doing wrong here?
Q
Pare you setting your preferred bits
Qno, but not setting them in glfw either.
Pyeah, if you don't set your preferred bits each library is free to do whatever the hell it wants
DI have to say Silkynvg looks awesome!
Qwell that's because it's the same as NanoVG...
Qthat might of course be a point...
Pwell it's awesome nonetheless
Qthank you 
DYeah, regardless of it being the same as NanoVG you can still take some credit :)
Pso it looks like you're probably missing a stencil buffer
Pjudging from the sdl code
QI am. Although I do have no idea how this backend works, which is why I am here.
DI think that's normal for graphics programming 
DI'd try to help you, but I don't know what the hell a stencil buffer is used for other then that it can be used to track how often a pixel is accessed
QIt’s a binary mask if a render call affects a certain area of the framebuffer
DI suppose that's interesting, though I'm not sure what it could be used for 
Best guess would be you could use it for partially presenting, but the performance of that isn't too great to sacrifice space in my framebuffer
Best guess would be you could use it for partially presenting, but the performance of that isn't too great to sacrifice space in my framebufferPrecommend doing this
where opts is your
where opts is your
WindowOptions or ViewOptionsQIt seems stencil buffer bits is 0. That of course would fix it
QIn NVG it’s used to just render a big rectangle shaded and then only present the bits that are wanted, this multi vertex stuff doesn’t require shading then only the simple rectangle.
Dah interesting
QBut don’t ask me about the stencil ops, no idea what they do...