diff options
author | wm4 <wm4@nowhere> | 2014-12-19 20:32:50 +0100 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2014-12-19 20:34:11 +0100 |
commit | e749d26ac3347da2e319fc7f57e6ebb72becbd7b (patch) | |
tree | 7ff92d07a106b3d3d377d041f577f976e2dc4250 | |
parent | d31e5842929c98913fab0546b984ec4e153b2386 (diff) | |
download | mpv-e749d26ac3347da2e319fc7f57e6ebb72becbd7b.tar.bz2 mpv-e749d26ac3347da2e319fc7f57e6ebb72becbd7b.tar.xz |
vo_opengl: skip GLES when autoprobing
There are probably bugs with GLES support; also, if you somehow get GLES
instead of desktop GL on a desktop computer, something else is probably
wrong. So I see no point in using this automatically. We first need to
find out whether the GLES support works on real hardware, and whether
it is useful at all.
-rw-r--r-- | video/out/gl_common.c | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/video/out/gl_common.c b/video/out/gl_common.c index 79d6dd73ad..05bce4dfb5 100644 --- a/video/out/gl_common.c +++ b/video/out/gl_common.c @@ -957,6 +957,11 @@ MPGLContext *mpgl_init(struct vo *vo, const char *backend_name, goto cleanup; } + if (ctx->gl->es && vo->probing) { + MP_INFO(ctx->vo, "Skipping experimental GLES support (use --vo=opengl).\n"); + goto cleanup; + } + if (ctx->gl->mpgl_caps & MPGL_CAP_SW) { MP_WARN(ctx->vo, "Suspected software renderer or indirect context.\n"); if (vo->probing) |