Issue with OpenGL code on Intel HD 4000 card (Windows 8)

[ATayl6]

I have some OpenGL code that seems to work fine on every setup bar Intel HD 4000 on Windows 8.

I have reproduced an example showing the problem (can be compiled using Visual C++)

On a working system it looks like

http://i39.tinypic.com/118zhvn.png[/IMG] http://i39.tinypic.com/118zhvn.png

On Intel HD 4000 on Windows 8

http://i42.tinypic.com/2ez1qh3.png[/IMG] http://i42.tinypic.com/2ez1qh3.png

I am assuming this is a driver issue (have tried the latest drivers but no joy) although can't rule out an issue with the code.

Can anyone help?

# include

# include

# include

// Function Declarations

LRESULT CALLBACK WndProc(HWND hWnd, UINT message, WPARAM wParam, LPARAM lParam);

void EnableOpenGL(HWND hWnd, HDC * hDC, HGLRC * hRC);

void DisableOpenGL(HWND hWnd, HDC hDC, HGLRC hRC);

// WinMain

int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance,

LPSTR lpCmdLine, int iCmdShow)

{

WNDCLASS wc;

HWND hWnd;

HDC hDC;

HGLRC hRC;

MSG msg;

BOOL quit = FALSE;

float theta = 0.0f;

// register window class

wc.style = CS_OWNDC;

wc.lpfnWndProc = WndProc;

wc.cbClsExtra = 0;

wc.cbWndExtra = 0;

wc.hInstance = hInstance;

wc.hIcon = LoadIcon(NULL, IDI_APPLICATION);

wc.hCursor = LoadCursor(NULL, IDC_ARROW);

wc.hbrBackground = (HBRUSH) GetStockObject(BLACK_BRUSH);

wc.lpszMenuName = NULL;

wc.lpszClassName = "GLSample";

RegisterClass(&wc);

// create main window

hWnd = CreateWindow(

"GLSample", "OpenGL Sample",

WS_CAPTION | WS_POPUPWINDOW | WS_VISIBLE,

0, 0, 512, 512,

NULL, NULL, hInstance, NULL);

// enable OpenGL for the window

EnableOpenGL(hWnd, &hDC, &hRC);

// program main loop

while (!quit)

{

// check for messages

if (PeekMessage(&msg, NULL, 0, 0, PM_REMOVE))

{

// handle or dispatch messages

if (msg.message == WM_QUIT)

{

quit = TRUE;

}

else

{

TranslateMessage(&msg);

DispatchMessage(&msg);

}

}

else

{

glLoadIdentity();

gluOrtho2D(-1.5938962727771744, 1.5938962727771744, -1.5707963267948966, 1.5707963267948966);

glBegin(GL_LINE_LOOP);

glVertex2d(-1.093332, -0.388151);

glVertex2d(-1.092969, -0.388418);

glVertex2d(-1.093067, -0.389266);

glVertex2d(-1.092257, -0.389503);

glVertex2d(-1.091499, -0.389893);

glVertex2d(-1.090951, -0.390575);

glVertex2d(-1.090157, -0.390978);

glVertex2d(-1.089468, -0.391521);

glVertex2d(-1.088742, -0.392055);

glVertex2d(-1.087883, -0.392249);

glVertex2d(-1.087084, -0.392626);

glVertex2d(-1.086413, -0.393203);

glVertex2d(-1.086254, -0.393989);

glVertex2d(-1.086176, -0.394827);

glVertex2d(-1.085459, -0.395254);

glVertex2d(-1.085169, -0.395996);

glVertex2d(-1.084897, -0.396781);

glVertex2d(-1.084354, -0.397474);

glVertex2d(-1.083956, -0.398172);

glVertex2d(-1.083321, -0.398783);

glVertex2d(-1.082729, -0.399405);

glVertex2d(-1.082467, -0.400180);

glVertex2d(-1.082225, -0.400995);

glVertex2d(-1.081717, -0.401707);

glVertex2d(-1.081027, -0.402269);

glVertex2d(-1.080291, -0.402681);

glVertex2d(-1.079516, -0.403059);

glVertex2d(-1.078943, -0.403656);

glVertex2d(-1.078322, -0.404300);

glVertex2d(-1.077667, -0.404873);

glVertex2d(-1.077484, -0.405731);

glVertex2d(-1.076762, -0.406152);

glVertex2d(-1.075884, -0.406375);

glVertex2d(-1.075022, -0.406608);

glVertex2d(-1.074493, -0.407311);

glVertex2d(-1.073843, -0.407932);

glVertex2d(-1.073323, -0.408644);

glVertex2d(-1.072456, -0.408786);

glVertex2d(-1.071758, -0.409285);

glVertex2d(-1.070857, -0.409484);

glVertex2d(-1.070075, -0.409861);

glVertex2d(-1.069489, -0.410512);

glVertex2d(-1.068698, -0.410995);

glVertex2d(-1.067836, -0.411107);

glVertex2d(-1.067201, -0.411728);

glVertex2d(-1.066532, -0.412285);

glVertex2d(-1.066634, -0.413133);

glVertex2d(-1.066101, -0.413807);

glVertex2d(-1.065469, -0.414428);

glVertex2d(-1.065068, -0.415170);

glVertex2d(-1.064413, -0.415767);

glVertex2d(-1.063483, -0.415732);

glVertex2d(-1.062698, -0.416106);

glVertex2d(-1.062019, -0.416678);

glVertex2d(-1.061062, -0.416697);

glVertex2d(-1.060094, -0.416654);

glVertex2d(-1.059338, -0.417027);

glVertex2d(-1.058474, -0.417017);

glVertex2d(-1.057568, -0.417294);

glVertex2d(-1.057204, -0.418026);

glVertex2d(-1.056303, -0.418113);

glVertex2d(-1.055507, -0.418516);

glVertex2d(-1.054678, -0.418734);

glVertex2d(-1.053737, -0.418715);

glVertex2d(-1.052943, -0.419190);

glVertex2d(-1.052074, -0.419547);

glVertex2d(-1.051119, -0.419520);

glVertex2d(-1.050170, -0.419607);

glVertex2d(-1.049325, -0.419460);

glVertex2d(-1.048452, -0.419198);

glVertex2d(-1.047541, -0.419239);

glVertex2d(-1.046582, -0.419825);

glVertex2d(-1.045594, -0.420411);

glVertex2d(-1.044648, -0.420998);

glVertex2d(-1.043674, -0.421584);

glVertex2d(-1.042728, -0.422171);

glVertex2d(-1.041757, -0.422757);

glVertex2d(-1.040797, -0.423344);

glVertex2d(-1.039834, -0.423930);

glVertex2d(-1.038864, -0.424513);

glVertex2d(-1.037980, -0.425037);

glVertex2d(-1.037424, -0.425686);

glVertex2d(-1.036745, -0.426171);

glVertex2d(-1.036153, -0.426806);

glVertex2d(-1.035561, -0.427445);

glVertex2d(-1.034792, -0.427867);

glVertex2d(-1.033982, -0.428285);

<p...

[DArce]

Let me check what would be the appropriate channel of support for this.

While I do so, could you please indicate what is the driver versions you have tested with?

[ATayl6]

Thanks for your offer of help

We have tested with a variety of drivers including the latest as downloaded from

http://www.intel.com/p/en_US/support/detect http://www.intel.com/p/en_US/support/detect

This issue is being reported by a number of our customers. The only common factor is Windows 8 and that graphics card.

Note it isn't a Windows 8 issue in general as all works fine on other PCs with different graphics cards.

Thanks.

[ATayl6]

@Diego_Intel Any update on this? We are keen to find a solution to this issue.

Regards.

Alastair

[DArce]

Hello Alastair, we are still waiting for a response on this, you may alternatively check through http://software.intel.com/en-us/forum Forums | Intel® Developer Zone which is the actual channel of support for these concerns

[ATayl6]

We have just had a report of the same drawing issues with a PC with a Intel HD 4000 card but running Windows 7.

Any help on this matter would be much appreciated as it's now a number of clients experiencing this problem.

[DArce]

We have been able to replicate the issue and now we are working on implementing this fix on a future driver release.

As you may know, we may not provide an estimated time for this to happen.

[ATayl6]

@ Diego_Intel Thank you for the update. Will I be notified when the fix is available?

[DArce]

Yes, we will let you know when the fix is available in our web site.

[SDunl]

hello,

I also have an issue with my Surface Pro and a program called Sketchup Make. If I role back my drivers it work but when windows updates my drivers again the program breaks.

[DArce]

SDunlop, a fix for the issue being discussed here is to be available in a future driver release. If your issue is related to this same topic, then please wait for this fix to be available. If your concern is related to a different software/problem, then please create a separate thread and provide full system configuration (device models, driver/application versions and steps to reproduce the issue)

[SDunl]

Hello Diego,

I believe this is the same issue and I just wanted to provide some additional information and resource related information so that the engineering/development team have enough information to properly test the new drivers before releasing them. Obviously I would much rather see a driver release that fixes all OpenGL related issues in one driver rather than having to continuously update.

[DArce]

Alright. Thank you for your feedback, you may test this when the new driver is released. As a side note, I would like to let you know that I played a little bit with Sketchup Make using Microsoft* Windows* 8, with drivers version

9.18.10.3165 with Intel® HD Graphics 4000 and it worked fine.

https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&keyword=3165 9.18.10.3165 Download Center

if your issue still persists, then please open a new thread with your full information on your system configuration, dxdiag report and steps and/or a file to reproduce your issue.

[DArce]

I would like to let you know that the issue has been investigated and replicated, and a fix will be available in a future driver release. However there is no estimated date for this to be released at this moment.

[ATayl6]

Is there any update available yet as it's been 4 months since I raised this issue and we are keen to pass on a solution to our customers.

Regards.

[DArce]

We were notified that the fix would be available on a future driver release however no ETA is available for this.

[Allan_J_Intel1]

Thanks for your patient; I have received information from engineering team that this issue has been fixed with driver version 10.18.10.3345

Please test the version above and let me know about your findings:

https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Graphics&ProductLine=Laptop+graphics+drivers&ProductProduct=3rd+Generation+Intel%C2%AE+Core%E2%84%A2+Processors+with+Intel%C2%AE+HD+Graphics+4000&ProdId=3712&LineId=1101&FamilyId=39 https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Graphics&ProductLine=Laptop+graphics+drivers&ProductProduct=3rd+Generation+Intel%C2%AE+Core%E2%84%A2+Processors+with+Intel%C2%AE+HD+Graphics+4000&ProdId=3712&LineId=1101&FamilyId=39

Allan.