-
Notifications
You must be signed in to change notification settings - Fork 1
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
Crash after start: Error creating GL context: couldn't find any pixel format #21
Comments
Sorry for the confusion, dparnell's branch is separate from mine. Please try the latest build from my branch here. |
Sadly the same for appveyor builds. |
Potentially related: PistonDevelopers/piston#1202. Could you post the gl report from opengl extensions viewer? (You have to go to the GL Report tab before clicking the save icon at the top). Also do you use the linux version of alacritty on the same computer? |
No, I don't. The report seems to be very sad, almost nothing supported 😱 ReportRenderer: GDI Generic Vendor: Microsoft Corporation Memory: 0 MB Version: 1.1.0 Shading language version: N/AMax texture size: 1024 x 1024 GL Extensions: 3 GL_WIN_swap_hint Core features |
It seems like your display adapter doesn't support enough of OpenGL for alacritty to work properly. It depends on OpenGL 4.5 and I suspect the same error would occur if you tried using the linux version. |
Ok, it's caused by my docking station. My laptop is actually OpenGL 4.4 and runs Alacritty successfully. ReportRenderer: Intel(R) HD Graphics 5500 Max texture size: 16384 x 16384 GL Extensions: 219 GL_ARB_tessellation_shader Core features |
Well on my 960m Nvidia GPU ,another problem occurs. Alacritty runs only in debug mode but there is another window with following errors.
|
That's just caused by a change in the config file syntax, they used to be floats but have since been changed to integers. Updating your config file should remove the warning. If you have an issue different from the one in the title please create another issue instead of commenting on an unrelated one. |
@zacps Ok, what do think? Is it "Windows" related? I would say so, probably connected how drivers and other stuff is handled on Windows in connection with screen sharing, though not directly connected to alacritty. But I'm not sure which upstream component I should report to. |
I was talking to @gurpreetshanky about the unrelated comment. Honestly I'm not sure what could be done about the issue. Your best bet would be to report it against glutin, the opengl library we use, but I'm not sure it's even solvable. It's probably an issue with the video pass through on the dock, but it's possible there might be a workaround somewhere. |
I know :)
Great, thank, will try. |
Closing because of the downstream issue, if there's something else that can be done in alacritty please create an issue here |
Win 10.1803
Build provided by dparnell here: alacritty#28 (comment)
The text was updated successfully, but these errors were encountered: