![]() To change your game to a different version, start the launcher. You will need to buy a new video card or computer to play new versions.įor now, you can still play 1.7.2 or older versions of the game. The Intel 4 Series (and older) video cards are unable to play 1.7.4 and future versions of Minecraft. Ig4icd32.dll appears to be part of Intel's graphics drivers.įrom Mojang's bug entry on this, MC-14051: Your computer is likely to be very old, and a new computer may be a Alternatively for desktop users, you can buy a new GPU,īut the fact that your computer has an Intel 965 Chipset means that ![]() To play 1.7.4 or later versions, you will need a new computer. Likely affect all future versions of Minecraft.Īs such, you may work around this error by using a version prior toġ.7.4, such as 1.7.2. ![]() This error currently only affects all versions past 1.7.4 - and will A full list of affected devices can be found Some chipsets in the Intel 4 Series, most notably the Intel 965Įxpress Chipset are known to have issues with OpenGL support, that mayĪll Intel GPUs using the ig4dev32.dll and ig4dev64.dll drivers are If you do not have another GPU, then there is nothing you can do about this error, short of replacing your (presumably quite old) graphics card, or even your entire computer.įrom the support pages on regarding this issue: Intel 4 Series Chipsets Dedicated GPUs tend to have better supported/more compatible drivers than integrated ones. If you have another GPU in your computer, try running Minecraft with that: right mouse button on the executable → Run With → (something other than "integrated"). This manifests to the user in a client as the window stuck on a blank loading screen (the dirt background) and the window not responding.Your graphics card does not support newer versions of Minecraft. The second solution would automatically solve the config issue and preserve the existing config for possible fixing, at the cost of allowing the game to load with the default config that is mismatched to the previous config, causing (possibly unrevertable) issues with mod behaviors unintended by the player or pack developer.Ī hybrid solution could be considered where it informs the user as in the first proposal and, on the same screen, offers to remediate the issue as in the second proposal.Ĭuriously, it seems that triggering this bug on initial load by editing a server config to have an unparseable value (which I did by editing forge-server.toml and replacing one false with fals) before loading the world causes the world loading process to stall due to the raised exception and its side-effects on the rest of the process. This would not be preferrable given that most users don't either want to or are able to edit and correct config files. The first solution would put the burden of fixing the config on the player, forces the player to either fix the config or remove it (either by deletion or by renaming), allowing a fresh config file to be generated.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |