-
-
Notifications
You must be signed in to change notification settings - Fork 477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NoAvailablePixelFormat error #913
Comments
Try commenting out the But, yes, this is definitely a bug, glutin needs to check if the underlying system's OpenGL is high enough version to support the features called by glutin. |
Devs, I have this same issue on Debian unstable on an older Lenovo Thinkpad x201, as well as on an Ubuntu 17.04 system running on a virtualbox VM. |
This is not neccesary a bug. I do not expect glutin to support a GPU with OpenGL version 1.1 (Intel GMA X4500). However, the error is not very descriptive and there is no documentation regarding minimum supported OpenGL version. |
Here's the output from my virtualbox machine. Looking like max core is 3.3. Not 1.1. |
The error is not a matter of supported OpenGL version. |
Same error occured in my environment (gentoo linux amd64) with The error happened with mesa-17.2.0_rc3 but didn't happen with mesa-17.1.6 or older versions. |
This issue also appears on Linux (Antergos - Arch based)
GPU is Nvidia GTX 1050. This error seems to have happened after updating mesa from Also see PistonDevelopers/piston#1202 for more details. |
I'm having the same issue on archlinux on a macbook air with intel integrated graphics. Downgrading mesa from |
I'm having the same issue on both Intel HD Graphics 630 and GTX 1050 via bumblebee. I'm running Arch with |
Update: Still the case with Update 2: No change for |
Mee Too!™ Just got
|
It is Srgb's fault. Uncommenting the "does not work" line below reproduces the error. As a result I had to replace all
|
FYI: 102354 – Mesa 17.2 no longer can give SRGB-capable framebuffer on i965, even though Mesa 17.1.x does. seems causing this issue. |
I'm not sure exactly what's happening, but with mesa 17.4.0-devel and 17.3.0-devel, this issue is still occurring despite indications that it should be fixed on master (which I believe is currently 17.3.0; versions are confusing me because oibaf has 17.4.0 available while mesa's website only has 17.3.0. Both have been updated since the patch should have gone out, as far as I can tell).
|
This issue seems to be fixed with the latest |
I'm working on a webrender based GUI framework and I get this error when executing the program via a remotedesktop connection on windows. Might this issue be causing the same error for me which is |
The problem is gone on my laptop with archlinux for X11 and wayland. $ glxinfo | grep -i opengl
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) 965GM
OpenGL version string: 2.1 Mesa 18.3.1
OpenGL shading language version string: 1.20 $ cargo run --example window
Finished dev [unoptimized + debuginfo] target(s) in 0.18s
Running `target/debug/examples/window`
Pixel format of the window's GL context: PixelFormat { hardware_accelerated: true, color_bits: 24, alpha_bits: 8, depth_bits: 24, stencil_bits: 8, stereoscopy: false, double_buffer: true, multisampling: None, srgb: false }
OpenGL version 2.1 Mesa 18.3.1 |
Getting this error on windows 8.1 when trying to use |
Is this a native windows installation or is it running in a VM? |
I am not sure, it seems native, but the performance is significantly better than before, it also contains an installation of Oracle's VM I am not sure because the computer broke and i brought it to someone that could fix it, when it came, it was with Oracle VirtualBox installed. Also, it was a x86 processor, but suddently when i got it back it was suddently in a 64-bit OS |
I tried running msinfo32 but nothing about VMs appeared, so i guess i am in native |
Also, using the crate glfw and gl_loader worked for me, i used a macro to transmute the pointer to a function pointer, not only did everything work, but I was even able to use a nice blue color in a basic window. I really dunno why glutin does not work |
Running the
window
example on Windows 10, with Intel GMA X4500 GPU results in errorNoAvailablePixelFormat
at.\examples/window.rs:11
. Glutin version is 0.9.1. Is it possible to configure the context to support this GPU? Let me know if more information is needed.The text was updated successfully, but these errors were encountered: