Go to osugame
OSU — Can’t find the name of intel icd opengl driver when nvidia gpu is enabled for osu through control panel but its fine when I right click on osu.exe and choose run on nvidia card. How to fix?
So when I switch OSU to use my nvidia graphics card as the default through NVIDIA control panel I get the error I mentioned in the title. I imagined this would mean I couldn’t use it at all. I was wrong. Strangely, I can use OSU on my nvidia graphics card if I go directly to the osu exe, right click, and then choose run with nvidia graphics card. Why is this error happening only when I select my nvidia gpu through nvidia control panel? I don’t want to have to go to the exe every time I want to play OSU? How can I get osu to automatically run on the nvidia graphics card through nvidia control panel and work? Any help is greatly appreciated.
P.S. — Please don’t leave solutions like «just use integrated graphics», as I am trying to use the nvidia card for osu, or «just put the osu shortcut on your desktop» as that is not what I’m asking in the question
Archived post. New comments cannot be posted and votes cannot be cast.
@smoogipoo I am able to reproduce the problem. Besides that, I got a similar crash today:
OpenTK.Graphics.GraphicsContextException: [EGL] Failed to create window surface, error BAD_NATIVE_WINDOW.
在 OpenTK.Platform.Egl.EglWindowInfo.CreateWindowSurface(IntPtr config)
在 OpenTK.Platform.Egl.EglContext..ctor(GraphicsMode mode, EglWindowInfo window, IGraphicsContext sharedContext, Int32 major, Int32 minor, GraphicsContextFlags flags)
在 OpenTK.Platform.Egl.EglAnglePlatformFactory.CreateGLContext(GraphicsMode mode, IWindowInfo window, IGraphicsContext shareContext, Boolean directRendering, Int32 major, Int32 minor, GraphicsContextFlags flags)
在 OpenTK.Graphics.GraphicsContext..ctor(GraphicsMode mode, IWindowInfo window, IGraphicsContext shareContext, Int32 major, Int32 minor, GraphicsContextFlags flags)
在 #=zg40uki8N_8sKf7t$_ow3GAuhImSk.#=zephTqFg=(Int32 #=zkKEAnHk=, Int32 #=zJC1FmpU=, GraphicsContextFlags #=zk_ERPZ4=)
在 #=zXBIWPGr9zk0MwurYP3gdJy0=.OnHandleCreated(EventArgs #=ztTr01ko=)
This time I did not connect my external monitor with an HDMI cable, I connect a universal dock to my laptop and connect the HDMI cable to the universal dock. Setting it to prefer the integrated graphics card does not work anymore.
Обновлено: 09.02.2023
Describe the crash:
A pop-up saying «Can’t find the name of Intel ICD OpenGL driver» pop up twice and the crash window appears.
I tried to set Fullscreen=0 in .cfg file, it shows black screen instead, the osu background music can be heard, no pop-up or crash.
I checked my drivers and they are up-to-date.
Screenshots or videos showing the encountered issue:
«在»means «at» in Chinese
osu!lazer version:
osu!lazer shows a black screen as well, but no pop-up. I do not play osu!lazer currently so it is not a problem for now.
Logs:
Computer Specifications:
Device: Aspire VX5-591G
Processor: Intel Core i7-7700HQ
Problem Details: Whenever I start osu! with GTX 960M I get the error message «Can’t find the name of Intel ICD OpenGL driver» dialogue box. I can’t press the «OK» button on the box as the cursor is always «busy» spinning whenever I mouse over it.
osu! opens fine with iGPU but runs like shit with occasional cursor position reset while playing, stutters, lag, etc.
No, there is no crash screen. I had to end osu!.exe in Task Manager.
Shift-clicking to open the repair tool thingy also results in the same dialogue box with slightly different appearance.
Also happens with Stable (Latest), Beta and CE.
i7 6700HQ
8GB DDR3 1600MHz
GTX 960M 2GB
Windows 10 Pro OEM
All GPU drivers updated. Used to have 369.xx now 375.70. No difference.
Video or screenshot showing the problem:
osu! version: 20161101.1beta
Последний раз отредактирован NeVMiku 2016-11-08T00:35:48+00:00 , отредактирован 2 раз.
Processor: Intel i5 6300HQ
Graphiccard: Nvidia Gtx 970M
Windows 10
Kao wrote:
Are you serious? Really?
You wanted me to start another thread only to be redirected to the same one I was on? REALLY.
Please go away. You’re not helping at all.
Huh. This seems to be an occurring error lately.
Hold shift while opening osu!, and when the recovery dialog opens, try enabling the option «compatibility mode». This do anything? If not, try switching to Stable(Fallback). Any luck there?
OBDavid wrote:
Processor: Intel i5 6300HQ
Graphiccard: Nvidia Gtx 970M
Windows 10
I don’t think this is the same problem. I’d make a new thread for your problem.
Pawsu wrote:
Huh. This seems to be an occurring error lately.
Hold shift while opening osu!, and when the recovery dialog opens, try enabling the option «compatibility mode». This do anything? If not, try switching to Stable(Fallback). Any luck there?
First off, your cute avatar is gone! Why?
Secondly, shift+clicking it results in the same problem. The dialogue box appears but no crash screen.
Fallback is fine. But I’m not playing on that. >.>
Последний раз отредактирован NeVMiku 2016-11-06T17:05:20+00:00 , отредактирован 1 раз.
NeVe12p4wNeD wrote:
First off, your cute avatar is gone! Why?
Secondly, shift+clicking it results in the same problem. The dialogue box appears but no crash screen.
This one isn’t cute?
And if I’m understanding the OP correctly, the same thing occurs when you try to open the .exe repair osu! found in your osu! folder?
Pawsu wrote:
NeVe12p4wNeD wrote:
First off, your cute avatar is gone! Why?
Secondly, shift+clicking it results in the same problem. The dialogue box appears but no crash screen.
This one isn’t cute?
And if I’m understanding the OP correctly, the same thing occurs when you try to open the .exe repair osu! found in your osu! folder? There is no .exe for the repair tool directly, only osu!.exe with -config shortcut which I assume is what you’re talking about. Same result. The dialogue box comes up and hangs so that I had to End Task.
Also I’ve always run osu! with Compatibility Mode. I find it to be smoother.
Последний раз отредактирован NeVMiku 2016-11-06T17:12:01+00:00 , отредактирован 1 раз.
NeVe12p4wNeD wrote:
There is no .exe for the repair tool directly, only osu!.exe with -config shortcut which I assume is what you’re talking about. Same result. The dialogue box comes up and hangs so that I had to End Task.
This is actually pretty strange. It worked correctly a little bit ago, right? Have you updated or installed anything that could have caused this?
Pawsu wrote:
This is actually pretty strange. It worked correctly a little bit ago, right? Have you updated or installed anything that could have caused this?
About a few days ago it worked fine.
On the 28th October I had «Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3197954)» update. And 10 days before that (18th) I had the «Update for Windows 10 Version 1607 for x64-based Systems (KB3199209)» update.
As always, Windows doesn’t really tell you much about their updates but upon looking into the KB codes I found on this site that there is «Addressed additional issues with USB, Wi-Fi, clustering, setup, Microsoft Edge, Internet Explorer 11, licensing, PowerShell, Component Object Model (COM), Windows kernel, graphics, and Bluetooth.»
On the other hand I can’t find any information about KB3199209.
I did not install nor remove anything.
Whoops, I linked that thread above because it was solved by rolling back updates.
Most recent updates of version 1607 seems really buggy. There was another thread with the update 1607 has started to make his client do the same exact crash.
I’ll have to look for a while to see if the problem is caused by the update or not
The only thing I can think of is waiting for updates or going back updates :/
I have found a lot of threads that concern the KB3197954 update, and most of those problems were addressed with another game throwing in the same error.
The difference is what fixed it was through updating Java which I don’t think helps here, since osu! Doesn’t heavily rely on Java.
I have also taken note that there isn’t a really definitive fix for this, since it’s really specific in a certain degree.
OBDavid wrote:
average_mitch wrote:
- Intel HD Graphics Family / 4400 Update, Version 10.18.10.3316
4rz0 wrote:
- Windows 10 Pro release, most recent (10.0.10240)
- JRE 1.8.60 x64
- Intel HD Graphics 3000
- Intel drivers from May 2015, obtained trough Windows Update (9.17.10.4229)
Take note that they are really old articles, with the case of updates being the sole cause. Since they’re old, you can’t say that the problems caused in the links are the same exact here. However, I have reason to believe it could have caused it again.
t/518686
cherrypie01 wrote:
I have tried everything there but those didn’t help. It seems for some reason my Intel graphics driver deleted itself or something.
I recovered to a week ago and the problem seems solved.
Maybe a Windows update caused it? Anyway thanks for your help.
The cases above and the circumstances are very close, with the same OS version and with Intel HD
feedthebeast wrote:
I took a stab in the dark and shut off the Xbox Game bar integration by turning off the DVR options completely. Low and behold, it worked. It seems that there may be an issue for some people that when the DVR is enabled (which it is by default)
NeVe12p4wNeD wrote:
Kao wrote:
Are you serious? Really?
You wanted me to start another thread only to be redirected to the same one I was on? REALLY.
Please go away. You’re not helping at all.
This link was for OBDavid, sorry if that looked like I was tricking you. But the log shown was same of that thread.
His problem is the same now in that thread. With the problem caused by an update.
Pawsu wrote:
Huh. This seems to be an occurring error lately.
Hold shift while opening osu!, and when the recovery dialog opens, try enabling the option «compatibility mode». This do anything? If not, try switching to Stable(Fallback). Any luck there?
OBDavid wrote:
Processor: Intel i5 6300HQ
Graphiccard: Nvidia Gtx 970M
Windows 10
I don’t think this is the same problem. I’d make a new thread for your problem. I think they’re the same t/518686 this thread where OP first posted and the OP from that link itself throw in the same error, in which OBDavid had the same log.
Could NeVe12p4wNeD post their crash log (if any) here aswell?
Within said thread, the log means this
The runtime throwing a NullReferenceException always means the same thing: you are trying to use a reference. The reference is not initialized (or it was initialized, but is no longer initialized).
This means the reference is null, and you cannot access members through a null reference.
This could be referenced to the ICD Driver not being found.
Bottom line?
I really can’t pinpoint a real fix to this anymore. But since it’s caused by updates, rolling back updates until new updates that (hopefully) fixes these are addressed.
This has been spreading suddenly, and they’re always concerned with a recent update.
Try restoring to a previous version or update.
if windows update is the main cause, why don’t you try to update it again? mine on KB3199986 and doing fine.
Thanks for the reply Kao. I’ll try updating it again as Nub1 suggested, if not I’ll rollback.
I just installed an older Intel® HD Graphics 530 driver and now my osu works.
OBDavid wrote:
I just installed an older Intel® HD Graphics 530 driver and now my osu works.
Confirmed works on my laptop. Downgrading the Intel Graphics Driver fixed the problem. I don’t know why though because I’m running it off dGPU in the first place.
I’m really glad you were able to solve it. This was certainly a weird problem. Thanks, OBDavid! I’ll make sure to keep this in mind next time this error pops up.
Marking as resolved. You don’t have to manually mark it yourself — a support team member or lurking GMT will do so.
Glad to see my hardwork of research was correct
This is interesting, but I’m sure Intel will do an update very soon and will fix the problems
I too had this problem and when I installed the older versions, osu worked again
However, after sleeping my computer and waking it up the next morning, it seems the error is back
Since this is resolved, you should make a new thread instead.
Kitsunex wrote:
I too had this problem and when I installed the older versions, osu worked again
However, after sleeping my computer and waking it up the next morning, it seems the error is back
Windows probably installed the new version by itself. Disable the updates for that or do a rollback to a previous version for only that update and Windows should ignore said update in the future.
Had this problem happening on a fresh Windows 10 install (10.0.14393) on a laptop with Intel HD Graphics 530 (driver 21.20.16.4542) and a NVIDIA GTX 960M (driver 375.95, Optimus). I had the NVIDIA GPU set to be used by-default in NVIDIA’s graphics control panel, and osu! thus used the NVIDIA GPU to start. If I start osu! on the integrated Intel graphics however, it starts fine.
I didn’t have to downgrade drivers (both drivers were the latest Intel and NVIDIA offered on their download page; not from WU), and disabling Game Bar didn’t help. I have all available W10 updates installed and I’m not on a preview build currently.
Espionage724 wrote:
Had this problem happening on a fresh Windows 10 install (10.0.14393) on a laptop with Intel HD Graphics 530 (driver 21.20.16.4542) and a NVIDIA GTX 960M (driver 375.95, Optimus). I had the NVIDIA GPU set to be used by-default in NVIDIA’s graphics control panel, and osu! thus used the NVIDIA GPU to start. If I start osu! on the integrated Intel graphics however, it starts fine.
I didn’t have to downgrade drivers (both drivers were the latest Intel and NVIDIA offered on their download page; not from WU), and disabling Game Bar didn’t help. I have all available W10 updates installed and I’m not on a preview build currently.
If this is a problem, then you should open a new thread, since this is already resolved.
However, osu! Should work when you run it with the GPU
I had my nvdia drivers make a custom profile for osu! To run with the GPU and it made 7ms input lag to 2ms.
So GPU > Integrated Graphics
It’s probably because you have a bad configuration of your drivers
same problem, but i have fixed it.
first i tried download and install the newest intel and nvidia graphic drivers, no help.
then i uninstalled them both, just clicked on the ‘uninstall’ button in the driver properties, no 3rd soft was used. after that i can open osu! and it performed an update.
then i installed the newest intel and nvidia drivers again, and osu! run fine.
at this point i don’t know if the update or uninstalling drivers that fixed the problem.
This error happened to me today as well, but I have found much easier solution for all of you guys, who will ever face this issue again! You are welcome
Solution:
Open Device Manager, click Start > Control Panel > Device Manager
Expand Display Adapters
Double-click on your Intel® display device
Select the Driver tab
Click Roll Back Driver to restore
Don’t bump old marked threads please. It’s quite old, the solution is likely irrelevant
Seems like I have same issue, but your url is invaild now.
So can you find an vaild method to me? thanks!
Details avaliable in viewtopic.php?f=5&t=549058
Espionage724 wrote:
Had this problem happening on a fresh Windows 10 install (10.0.14393) on a laptop with Intel HD Graphics 530 (driver 21.20.16.4542) and a NVIDIA GTX 960M (driver 375.95, Optimus). I had the NVIDIA GPU set to be used by-default in NVIDIA’s graphics control panel, and osu! thus used the NVIDIA GPU to start. If I start osu! on the integrated Intel graphics however, it starts fine.
I didn’t have to downgrade drivers (both drivers were the latest Intel and NVIDIA offered on their download page; not from WU), and disabling Game Bar didn’t help. I have all available W10 updates installed and I’m not on a preview build currently.
Scorpy wrote:
This error happened to me today as well, but I have found much easier solution for all of you guys, who will ever face this issue again! You are welcome
игра запускается на интеловской видяхе но фпс меня не устраивает, а когда пробую переключить на дискретную 950м выдает эту ошибку.. дрова обновлял, и еще всякие процедуры с ютуба но ничего не помогло. другие игры работают, проблемма не в видяхе.
заходишь через блокнот osu!<имя компа>.cfg, потом ctrl+F, пишешь CompatibilityContext, и меняешь 1 на 0
а если пишет что не удаётся найти CompatibilityContext
лол, расширенный опен ГЛ твоя видюха не поддерживает
OpenGL обновлял? Если обновлял, тогда должен расстроить: Видеокарта не поддерживает нужную версию.
So recently all the drivers in my laptop got automatically updated and i got this Intel OpenGL Driver problem and i can’t open osu!, i found some temporary solutions and that is to use intergrated graphics instead of the nvidia graphics that i usually use for osu!, or disabling compatibility mod but those options really degrades the performance and it gives a really noticeable input lag. i tried switching to cutting edge and it’s still doesn’t work.
I don’t know a proper solution for this and it’s pretty much effecting osu! only, for now i’ll try playing with intergrated graphics until this gets fixed or until i found another solution that works for me
Читайте также:
- Как стать сейлормун в реальной жизни
- Doom emacs что это
- Как спасти грюнта в mass effect 3
- Что значит verified в geometry dash
- Batman arkham city где лежат сохранения
Некоторые пользователи Windows получали сообщение « Не могу найти имя драйвера Intel ICD Open GL » при открытии игры, Google Chrome или другого приложения, использующего Open GL ES . В большинстве случаев проблема возникает после того, как пользователь обновит до Windows 10 более старую версию. В некоторых случаях процесс обновления заканчивается установкой несовместимого драйвера HD Intel, который вызывает ошибку.
Вот краткий список приложений и игр, которые, как известно, конфликтуют с этими изменениями, вызывают ошибку « Не удается найти имя драйвера Intel ICD Open GL» :
- Гугл Хром
- Панель управления Nvidia
- Nvidia GeForce Experience
- Расширенная телеметрия и визуализация данных Arduino
- Происхождение
- Gephi для домашних заданий
- GeoGebra Classic
- Ultima Online
- Net Vu Observer
- Wakfu (Steam-версия)
- Большеберцовая кость
- Battle.net
- OSU!
Если в настоящее время вы столкнулись с ошибкой « Не удается найти имя драйвера Intel ICD Open GL» , приведенные ниже методы могут помочь. Нам удалось определить несколько потенциальных исправлений, которые решают проблему для пользователей, находящихся в такой же ситуации, как и вы. Пожалуйста, следуйте приведенным ниже исправлениям по порядку и посмотрите, какое из них помогает решить вашу проблему.
Метод 1: загрузка последней версии драйвера графики Intel
К счастью, Intel решила эту проблему довольно рано, так что прямо сейчас у нас уже есть жизнеспособное исправление, подтвержденное множеством проблем. Последний новый базовый пакет драйверов (15.46) содержит исправления, специально предназначенные для решения этой проблемы. Прежде чем делать что-либо еще, установите этот драйвер и посмотрите, удастся ли ему решить проблему.
Вот краткое руководство, как это сделать:
- Перейдите по этой ссылке (здесь) и загрузите исполняемый файл для установки.
- Откройте исполняемый файл и следуйте инструкциям на экране, чтобы установить последнюю версию драйвера видеокарты Intel.
- Перезагрузите компьютер и посмотрите, была ли удалена ошибка « Не удается найти имя драйвера Intel ICD Open GL », открыв приложение, которое ранее отображало проблемы.
Если этот метод не помог решить вашу проблему, перейдите к способу 2 .
Метод 2: изменение версии приложения в соответствии с архитектурой вашего ПК
Другие пользователи сообщали, что виновник был идентифицирован не как несовместимость драйвера, а как несовместимость с версией архитектуры приложения.
Чтобы было понятнее, ошибка « Не удается найти имя драйвера Intel ICD Open GL »
также может возникнуть, если вы пытаетесь открыть приложение, которое было разработано для работы в 32-битных системах с 64-битного компьютера. То же самое и наоборот, хотя вероятность намного меньше.
Имея это в виду, давайте исследуем, соответствует ли версия архитектуры вашей операционной системы разрядной версии приложения. Вот краткое руководство по всему этому:
- Нажмите клавишу Windows + R, чтобы открыть команду «Выполнить». Введите « cmd » и нажмите Enter, чтобы открыть окно командной строки .
- В командной строке введите следующую команду и нажмите Enter :
wmic os получить архитектуру
- Вы сможете увидеть используемую в настоящее время архитектуру непосредственно в OSArchitecture .
- Теперь, когда вы знаете архитектуру своей ОС, убедитесь, что приложение, которое вы пытаетесь открыть, имеет требуемую разрядную версию. Если этого не произошло, удалите его и переустановите правильную версию.
- Убедившись, что версия приложения правильная, перезагрузите компьютер и посмотрите, сможет ли приложение запуститься при следующей перезагрузке.
Если вы все еще боретесь с проблемой, перейдите к последнему методу.
Метод 3: возврат к более старой версии драйвера Intel Graphic
Если первые два метода не помогли, вполне возможно, что стандартное исправление, выпущенное Intel, не применимо к вашей ситуации, и производитель вашего ПК еще не выпустил конкретное обновление драйвера для вашей модели.
В этом случае единственное жизнеспособное решение — вернуться к более старой версии, которая правильно работала в соответствии со спецификациями вашего компьютера. Вот краткое руководство, как это сделать:
- Посетите эту ссылку ( здесь ) и загрузите установщик для драйвера графической системы Intel® (версия 15.40) в соответствии с вашей версией Windows и архитектурой ОС.
Примечание. Хотя вы можете поэкспериментировать с разными версиями из Центра загрузок Intel, известно, что версия 15.40 является одним из самых стабильных выпусков. Если вы обнаружите, что этот драйвер выдает ту же ошибку « Не удается найти имя драйвера Intel ICD Open GL» , вы можете поэкспериментировать с другими старыми версиями.
- Откройте программу установки и следуйте инструкциям на экране, чтобы установить более старую версию драйвера графики Intel®.
- После установки драйвера перезагрузите компьютер и посмотрите, решена ли проблема и можно ли открыть приложение без ошибки « Не удается найти имя драйвера Intel ICD Open GL» .
This article is applicable to the following wrappers:
Behaviour¶
osu! crashes on startup, displaying an error message that says osu! was unable to obtain a graphics context.
Cause¶
Note
A previous version of this article incorrectly stated that osu! used DirectX. It has now been corrected. Please see issue #8 on GitHub for more information.
This usually occurs because a user enabled Compatibility Mode in osu! settings, or changed to a screen resolution that Wine couldn’t handle.
Standard osu! uses OpenGL which is supported by the Wineskin, while Compatibility Mode will use ANGLE / OpenGL ES which is not supported by osu! Wineskins. This explains why osu! will crash with OpenGL ES-related errors on Compatibility Mode.
Resolution¶
-
Find your user profile/configuration file.
-
Locate where
osu!.app
(your Wineskin) is installed -
Right click on it and select
Show Package Contents
-
You should now see three files/folders:
Contents
,drive_c
andWineskin
. Clickdrive_c
. -
From here, click
osu!
. -
From here, locate
osu!.yourcomputername.cfg
and open this file in a plain text editor such as TextEdit.
-
For example, my configuration file is osu!.Adrian.cfg
and it looks like this:
Tip
The default name for this file is usually osu!.Apple.cfg
Note
Don’t get confused with osu!.cfg
which is a completely different and much smaller configuration file.
Danger
Heed the warning and don’t share this configuration file with anyone else, not even us. It contains hashed versions of your passwords.
-
You’ll need to either delete or change a number of screen resolution options if you don’t know which is causing osu! to crash. If you know what option is breaking osu!, then you only need to modify/delete that specific option, as listed below.
Compatibility Mode¶
If you enabled Compatibility Mode and now osu! won’t start, find the CompatibilityContext
option.
Tip
Use Command + F
in TextEdit to quickly search for CompatibilityContext
.
Note
osu!macOS Agent will automatically disable Compatibility Mode as part of its troubleshooting steps.
If you did enable it, it would look like this:
Change this to:
Then, start osu!
If you can’t find CompatibilityContext
¶
Add the following line to the bottom of osu!.yourcomputername.cfg
:
Then, start osu!
Screen Resolution¶
If you changed the screen resolution to something a bit weird, find these options:
-
Height
-
Width
-
HeightFullscreen
-
WidthFullscreen
Tip
Use Command + F
in TextEdit to quickly search for these options.
Then, change the values accordingly to your last known previous settings, or to the recommended values as shown below. You can also delete them to have osu! initialise everything for you again.
Preferably:
-
Height
andWidth
should be Wine’s specified screen resolution (or otherwise, a standard screen resolution like1920x1080
) -
HeightFullscreen
andWidthFullscreen
should be your computer’s effective/scaled screen resolution.
Find Wine’s specified screen resolution
If you’re using Virtual Desktop on the X11 driver and need to modify Height
and Width
:
Locate where
osu!.app
(your Wineskin) is installedRight click on it and select
Show Package Contents
You should now see three files/folders:
Contents
,drive_c
andWineskin
. ClickWineskin
.Click Set Screen Options
Locate the Screen Resolution dropdown as shown below — what it is set to is Wine’s specified screen resolution:
In this example it is 1920x1080
. Therefore, Width = 1920
and Height = 1080
.
Find your fullscreen resolution
To find osu!’s fullscreen resolution, you need to know your current scaled resolution for the monitor you’re playing osu! on.
Your scaled screen resolution on this monitor is
x
where:
- Width =
- Height =
Now, replace the corresponding Height and Width values in osu!.yourcomputername.cfg
with those displayed above.
If that didn’t work¶
There could be something else going on here, and performing basic troubleshooting should help you get to the bottom of it.
If you’re not sure what’s going on here, copy any osu! crash logs as well as generating a report with osu!macOS Agent, and let us know on the forums.
Note
Random side note that may or may not be useful to you: (i didn’t have anywhere else to put it)