It is now set to both a Radeon RX470 Graphic Driver AND a Microsoft Basic Display Adaptor after the Tech put the computer through a full diagnostic examination and upgrade sequence.I do not check in Preference Use Graphics Processor for Video Playback and I do nil video editing.
Microsoft Gdi Generic 1.10 Full Diagnostic ExaminationMicrosoft Gdi Generic 1.10 Driver AND AAre you able to play videosaudios from your catalog If answer to both of above questions is yes, then there is nothing to worry about. Microsoft Gdi Generic 1.10 Driver Installed OnAs you mentioned, this error simply tells that the MicrosoftIntel display driver installed on your system is not the latest one. So till the point you are not updating your Microsoft Basic Display Adaptor. My recommendation is: if everything is working fine at your end then can safely ignore the warning. I guess the thread actually belongs here, since it is kind of technical. I hope we may get in touch with a engineer, that may help us track what appears to be a bug in Intel HD Graphics 3000 and 4000 driver. They have in common, that the OpenGL renderer that we find is the GDI generic ( OpenGL core v. Intel renderer (OpenGL core v. So we have made some tests to troubleshoot the underlying issue. We have tried a bunch of both simple but also far fetched things, b ased on the fact that there are reports of weird behavior in this graphic series ( OpenGL Discussion and Help Forums ). All our tests have supposedly worked well on our users failing computers (GL context have reported right renderer and version). Some of these tests have bootstrapped OpenGL and the window as close to our software as you may get it, however with the only major difference that everything were bootstrapped from one assembly(exe). In contrast to our software, where our main application calls into a dynamic library, that calls in to a second dynamic library which bootstraps a Windows Form with a GL context within it. ![]() So we would really appreciate some technical insight about cases that may trigger your driver to fallback to the software driver included in Windows. You see HD 3000 HD 4000 are not currently supported products. ![]() As in your software is using an OpenGL version or feature the HD 30004000 HW (or SW) does not support. We are asking for GL version 2.0. The GL tests that we sent to our users, did the same bootstrapping of the context as our main application, and they apparently worked. We are creating the context before we are showing the form (that is not the case in our tests). It shouldnt be a problem since the driver are only supposed to bind a context to a HWND handle as far as I know.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |