Katelyn Gadd

Basically since some AMD drivers report they can use adaptive vsync and then HARD CRASH I'll have to make a utility that runs before my games and tests any iffy claims from the GPU and stores the pass/fail results for the framework to use.

This works because my framework keeps a LiteDB flat-file database in the user's roaming folder that's available to all games using the framework which emulates HTML's LocalStorage, so that's what the utility would read/write from and so would the games. Wheeeeee.

More good news: since my framework's premise on desktop is to be compatible with WebGL (and so constrained by it) that means it should be OpenGL ES compatible by default which gives me the option of running my games on Windows through ANGLE/DirectX rather than OpenGL.

I'm not sure if OpenGL or ANGLE by default on Windows is a better idea, if anyone has experience with that let me know.

Use ANGLE, it's what browser vendors do. Using native GL is something you can get away with if driver vendors optimize for you, like id

Are there any gotchas I should be aware of when using ANGLE instead of OpenGL that you know of?

Their implementation of features is a little weird sometimes, and their shader compiler can act funny sometimes too. They have a bug tracker though, and it's relatively solid

I've found bugs in ANGLE before but they eventually got fixed and usually weren't major. I think @eevee and @mcclure111 might've had some issues with ANGLE WebGL as well?