Graphics Card Won't Recognize a Program as a Game.

[AMcNe1]

I have the Intel HD 4000 and my os is Windows 8 64 bit. A game that I commonly play recently came out with a new launcher. With that new launcher I get lag. In scenarios where every thing is the same (same save, same version) but the launcher is different, I get around 100 fps with the old launcher, and 20 fps with the new launcher. I think that this is due the the graphics card as not recognizing the program as a game. Help would be much appreciated.

[DArce]

What is the name of the game that you are having issues with?

If this started to happen after using another launcher, have you checked with the game developer? This might be a problem related with the launcher itself and not the video controller?

[AMcNe1]

The name of the game window is Minecraft 1.6.1. I have done some more research and the reason of the lag is because the launcher splits the game into two different programs and the one that the game is running on is not identified by the driver as a 3D application. So the reason for the lag can be fixed by either the game developer or the driver maker.

[DArce]

Please copy paste the dxdiag report from your system.

To get this, press Start key, type dxdiag and press enter, then save all this information.

[AMcNe1]

Here it is.

-----------------

Time of this report: 7/4/2013, 22:57:03

Machine name: ALEXS_LAPTOP

Operating System: Windows 8 64-bit (6.2, Build 9200) (9200.win8_gdr.130410-1505)

Language: English (Regional Setting: English)

System Manufacturer: Dell Inc.

System Model: Inspiron 5520

BIOS: A13

Processor: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz (8 CPUs), ~2.2GHz

Memory: 8192MB RAM

Available OS Memory: 8062MB RAM

Page File: 5170MB used, 4683MB available

Windows Dir: C:\Windows

DirectX Version: DirectX 11

DX Setup Parameters: Not found

User DPI Setting: Using System DPI

System DPI Setting: 96 DPI (100 percent)

DWM DPI Scaling: Disabled

DxDiag Version: 6.02.9200.16384 64bit Unicode

------------

DxDiag Notes

------------

Display Tab 1: No problems found.

Sound Tab 1: No problems found.

Sound Tab 2: No problems found.

Input Tab: No problems found.

[DArce]

I wanted to check if this system was using any kind of software such as Lucid Virtu* where the application needs to identify the software to trigger the performance options of the system, however this does not apply for this.

It seems that may should check with the game developer to see what could have been the reason for this change as the video controller does not make a difference between an application or a game.

[AMcNe1]

I talked to the game developer. They said that there is nothing that they can do to fix this problem. As running the game in the separate window is required for the further advancement of the game. Please help.

[DArce]

Please let me have the full dxdiag report generated in your system for further investigation.

Be sure to be using the latest generic driver posted on our site, driver version 15.31.9.64.3165 (9.18.10.3165) posted here:

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

[AMcNe1]

Nvidia and AMD were able to fix this bug, as the new launcher was still in beta. Note: This is affecting all computer with Intel ONLY graphics card. Multiple users have confirmed this with HD 2000-4000 cards.

DxDiag Report:

------------------

System Information

------------------

Time of this report: 7/12/2013, 15:10:56

Machine name: ALEXS_LAPTOP

Operating System: Windows 8 64-bit (6.2, Build 9200) (9200.win8_gdr.130410-1505)

Language: English (Regional Setting: English)

System Manufacturer: Dell Inc.

System Model: Inspiron 5520

BIOS: A13

Processor: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz (8 CPUs), ~2.2GHz

Memory: 8192MB RAM

Available OS Memory: 8062MB RAM

Page File: 3557MB used, 5720MB available

Windows Dir: C:\Windows

DirectX Version: DirectX 11

DX Setup Parameters: Not found

User DPI Setting: Using System DPI

System DPI Setting: 96 DPI (100 percent)

DWM DPI Scaling: Disabled

DxDiag Version: 6.02.9200.16384 64bit Unicode

------------

DxDiag Notes

------------

Display Tab 1: No problems found.

Sound Tab 1: No problems found.

Sound Tab 2: No problems found.

Input Tab: No problems found.

--------------------

DirectX Debug Levels

--------------------

Direct3D: 0/4 (retail)

DirectDraw: 0/4 (retail)

DirectInput: 0/5 (retail)

DirectMusic: 0/5 (retail)

DirectPlay: 0/9 (retail)

DirectSound: 0/5 (retail)

DirectShow: 0/6 (retail)

---------------

Display Devices

---------------

Card name: Intel(R) HD Graphics 4000

Manufacturer: Intel Corporation

Chip type: Intel(R) HD Graphics Family

DAC type: Internal

Device Type: Full Device

Device Key: Enum\PCI\VEN_8086&DEV_0166&SUBSYS_05691028&REV_09

Display Memory: 1792 MB

Dedicated Memory: 32 MB

Shared Memory: 1760 MB

Current Mode: 1366 x 768 (32 bit) (60Hz)

Monitor Name: Generic PnP Monitor

Monitor Model: unknown

Monitor Id: LGD033A

Native Mode: 1366 x 768(p) (60.052Hz)

Output Type: Internal

Driver Name: igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igdumdim32,igd10iumd32,igd10iumd32

Driver File Version: 9.18.0010.3165 (English)

Driver Version: 9.18.10.3165

DDI Version: 11

Feature Levels: 11.0,10.1,10.0,9.3,9.2,9.1

Driver Model: WDDM 1.2

Graphics Preemption: DMA

Compute Preemption: Thread group

Driver Attributes: Final Retail

Driver Date/Size: 5/7/2013 17:22:46, 8632320 bytes

WHQL Logo'd: Yes

WHQL Date Stamp:

Device Identifier: {D7B78E66-4226-11CF-C57F-6325B4C2C435}

Vendor ID: 0x8086

Device ID: 0x0166

SubSys ID: 0x05691028

Revision ID: 0x0009

Driver Strong Name: oem122.inf:5f63e5341859ec8c:iIVBM_w8:9.18.10.3165:pci\ven_8086&dev_0166

Rank Of Driver: 00E02001

Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C

DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT

Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{BF752EF6-8CC4-...

[DArce]

Thank you, let me further investigate on this and get back to you.

[howen]

Hello i have been having a similar problem with my graphics card not wanting to sync with my game. here is all the system info please help me fix this its really annoying.

------------------

System Information

------------------

Time of this report: 7/16/2013, 01:29:18

Machine name: DEATHLYSIN-PC

Operating System: Windows Vista™ Home Premium (6.0, Build 6002) Service Pack 2 (6002.vistasp2_gdr.130501-1537)

Language: English (Regional Setting: English)

System Manufacturer: HP-Pavilion

System Model: GG054AA-ABA a6177c

BIOS: BIOS Date: 06/01/07 11:25:23 Ver: 08.00.14

Processor: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz (2 CPUs), ~2.3GHz

Memory: 2038MB RAM

Page File: 2012MB used, 19967MB available

Windows Dir: C:\Windows

DirectX Version: DirectX 11

DX Setup Parameters: Not found

DxDiag Version: 7.00.6002.18107 32bit Unicode

------------

DxDiag Notes

------------

Display Tab 1: No problems found.

Sound Tab 1: No problems found.

Sound Tab 2: No problems found.

Input Tab: No problems found.

--------------------

DirectX Debug Levels

--------------------

Direct3D: 0/4 (retail)

DirectDraw: 0/4 (retail)

DirectInput: 0/5 (retail)

DirectMusic: 0/5 (retail)

DirectPlay: 0/9 (retail)

DirectSound: 0/5 (retail)

DirectShow: 0/6 (retail)

---------------

Display Devices

---------------

Card name: Intel(R) G33/G31 Express Chipset Family

Manufacturer: Intel Corporation

Chip type: Intel(R) GMA 3100

DAC type: Internal

Device Key: Enum\PCI\VEN_8086&DEV_29C2&SUBSYS_2A5D103C&REV_02

Display Memory: 286 MB

Dedicated Memory: 0 MB

Shared Memory: 286 MB

Current Mode: 1920 x 1080 (32 bit) (60Hz)

Monitor: Generic PnP Monitor

Driver Name: igdumdx32.dll

Driver Version: 7.15.0010.1666 (English)

DDI Version: 9Ex

BGRA Supported: Yes

Driver Attributes: Final Retail

Driver Date/Size: 2/26/2009 19:34:14, 536576 bytes

WHQL Logo'd: Yes

WHQL Date Stamp:

Device Identifier: {D7B78E66-6A82-11CF-0E75-570AA2C2CA35}

Vendor ID: 0x8086

Device ID: 0x29C2

SubSys ID: 0x2A5D103C

Revision ID: 0x0002

Revision ID: 0x0002

Video Accel: ModeMPEG2_A ModeMPEG2_C

Deinterlace Caps: {AEDC1D5D-8546-440E-AAB2-B69FA725AF82}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_FieldAdaptive

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{AEDC1D5D-8546-440E-AAB2-B69FA725AF82}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_FieldAdaptive

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{AEDC1D5D-8546-440E-AAB2-B69FA725AF82}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_FieldAdaptive

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{AEDC1D5D-8546-440E-AAB2-B69FA725AF82}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_FieldAdaptive

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{AEDC1D5D-8546-440E-AAB2-B69FA725AF82}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_FieldAdaptive

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{AEDC1D5D-8546-440E-AAB2-B69FA725AF82}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_FieldAdaptive

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{AEDC1D5D-8546-440E-AAB2-B69FA725AF82}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_FieldAdaptive

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend

{AEDC1D5D-8546-440E-AAB2-B69FA725AF82}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_FieldAdaptive

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/...

[AWell6]

A friend has the same problem. It continues after update 1.6.2.

Intel HD Graphics 4000.

I miss playing with him and just thought I'd throw my vote in for fixing and point out a Mojang bug report here:

https://mojang.atlassian.net/browse/MCL-767 https://mojang.atlassian.net/browse/MCL-767

Their stance seems to be that it's an Intel problem. And apparently Nvidia and AMD fixed this issue in a driver release... or some such.

I don't know really. But this is the last surviving 'Open' issue amongst a slew of 'duplicates'.

[DElli4]

I've been following that issue, as I am affected by this bug too. When I use the old launcher, I can get 60fps no problem. When using the new launcher, I get between 3-30ish fps. I have Windows 8, Intel Graphics 4000 HD as well.

[DArce]

Thank you for your feedback on this matter. We are investigating on the issue.

So, as soon as we have an update on this we will let you know.

[MDian1]

Hello Diego_Intel,

there are dozens of my Subscribers (YouTube) that have this specific INTEL-only problem as well.

The unknown number of people having this INTEL-specific issue is thousands at least for sure.

If you need any additional information, please ask for it, and all of those affected will try to help INTEL to help them.

Although it already has been mentioned, I try to sum it up:

If you read all of the comments of the aforementioned link https://mojang.atlassian.net/browse/MCL-767 https://mojang.atlassian.net/browse/MCL-767 , you will get the image how this problem looks like, and what people think is the Issue.

I can confirm that the Game Developer itself stated that the other Graphics Card companies did update their Driver while unreleased Snapshot Versions of the Game Minecraft were in a testing phase, and that they did state that INTEL did not update their Drivers, unlike the other companies.

Minecraft needs javaw.exe to run.

With the old Launcher, only 1 single javaw.exe was opened (you can see that in the Windows task manager).

Launcher and Gamewindow were basically "the same" (same window).

With the new Launcher, it starts at first a Launcher to login, and after chosing the Gameversion, it launches an extra Gamewindow which opens a second javaw.exe.

And apparently this is what the INTEL driver does not recognize as 3D-application for the GPU anymore. It seems to ignore it.

We have not found any way, be it by using Java arguments or anything like that, to tell the INTEL driver to see this second (Game)window as game application that needs Hardware Acceleration, hence people have horrid Lag/low FPS and cannot play this Game anymore. Basically you've had at least 60-120 FPS before, and now drop to unplayable 2-20 FPS at max (unsteady FPS).

The INTEL driver doesn't seem to understand this second window is a Game.

If you need any help - for example a Video how it looks like etc. - please just ask for it.

There are so many desperate Gamers that cannot play their favourite Game anymore and can't afford to get an additional dedicated GPU to circumvent the "INTEL-GPU-only"-problem.

Thank you kindly in advance for your effort,

Meri

EDIT: Anyone having more tech knowledge than me please correct my above text in case I wrote something wrong - thank you very much!

[MDian1]

Just an addition to what I've written before, I copy & paste from the link/Issue, because it describes better than I just did, what we *think* is the Issue - but we cannot be 100% sure because we do not know how Intel Drivers operate!:

"Systems with nVidia or AMD GPU's show no FPS difference between the old and new launcher.

However, Intel GPU powered systems drop to 1/3 or even 1/4 the framerate with the new launcher.

Since issue previously existed on 3rd party launchers such as MagicLauncher, sp614x (coder of Optifine and MagicLauncher) and I have narrowed the culprit down to the fact that the new launcher uses a separate process to run the game while the previous Minecraft.exe launcher ran the game inside the same process.

I have theorized that Intel drivers no longer recognize the game as a 3D application when this happens thus and limits GPU utilization, but it's hard to know for sure without more knowledge about how Intel drivers operate."

[DArce]

LapisDemon, we are aware of the issue and we are currently investigating on it.

SparxDragon, you are using Microsoft* Windows* 8 on a system based on the Intel (R) G31/G33 Express Chipset video controller. As you may know, the drivers for that controller are provided only by the operating system developer and such generic drivers may have limited features as the ones required to play this game

[MDian1]

Hello Diego, awesome, thank you!

Just thought (feared) you might think only few people have this problem because of the lack of participants here.

There are alot of them, and I just hope INTEL wouldn't consider this a minor problem, only because not many people post in here.

Thank you very much for your work, alot of Minecrafters hope for help.

Kind regards,

Meri

[EWo]

Experiencing the same issue. Thanks for looking into this, Intel.

[MDian1]

Dear Ladies and Gentlemen of INTEL,

as I already wrote a week ago, I'd like to know the status regarding the future INTEL Drivers.

I just wrote in the https://mojang.atlassian.net/browse/MCL-767 thread of Mojang's bugtracker-site Mojira that we users don't know what's going on and what is planned in the future, because neither INTEL nor Mojang is giving us any update or feedback regarding this matter.

It would be very much appreciated if anyone from Mojang or INTEL would tell us whether or not the future Driver will contain the Minecraft-fix in the way that Mister Broes has suggested it for no further future performance complications, or if there is any other kind of agreement or plan beind the scenes regarding INTEL Drivers and Mojang Launcher.

The information about when the new Drivers will be released for INTEL would be very helpful as well, so the Minecraft community can react in time and is prepared and "warned", because, from what I understood, the temporary Hackfix in the new Minecraft Launcher will get reverted as soon as INTEL has released their new Drivers.

Thank you very much in advance for an answer,

kind regards,

Meri

[NICHOLAS_F_Intel]

Hi Meri,

I do not have any info or an ETA for you at this point. I am aware that is being worked on from both sides though, and that is all. I will update this thread when there is more information.

Thank you for your patience!

-Nic