WispApp uses glumpy with a glfw_imgui backend, which defaults to OpenGL 2.1 context. However, imgui expects an OpenGL 3.3+ context, which causes errors on some envs.
This MR creates the window with glumpy.app.configuration.get_default(), which effectively takes the correct GL version we put in the WispState config (the previous MR used app.configuration.Configuration(), this is not enough).
OpenGL 3.3 requires a VertexArrayObject to be bound to initiate a draw call, otherwise sparking some GL errors. WispApp now ensures there is a default VAO in place.
WispApp uses glumpy with a
glfw_imguibackend, which defaults to OpenGL 2.1 context. However, imgui expects an OpenGL 3.3+ context, which causes errors on some envs.glumpy.app.configuration.get_default(), which effectively takes the correct GL version we put in theWispStateconfig (the previous MR usedapp.configuration.Configuration(), this is not enough).WispAppnow ensures there is a default VAO in place.See also: https://github.com/glumpy/glumpy/issues/310
In addition, the following changes add some extra robustness:
GL_TEXTURE_MAX_ANISOTROPYis missing from the feature set._register_cugl_shared_texturewill now fallback toblitdevice2device=False(WSL mode) if cugl registration failed.Signed-off-by: operel operel@nvidia.com