The actual issue is with the game itself from what I recall, despite usually only being seen on Intel graphics since their drivers don't ignore/work around it. This leads to many blaming Intel or its drivers as the cause when its the game. Both nVidia and AMD hardware had this begin to happen on older drivers if I'm not mistaken, but then it stopped occurring with them. I would imagine they both probably simply went back to ignoring/working around this issue. Likewise, very old Intel drivers don't have the issue but using older drivers is not always a solution.
This occurs in the window of versions after beta 1.7.3 but before release 1.8 (if VBOs are enabled, otherwise it can continue to occur up until release 1.12 or 1.13). A change was made to beta 1.8 that, at the time, made no effective difference (drivers of the time were less strict), but it sometimes does with drivers now. nVidia and AMD are probably more likely to have decades of built up workarounds for obscure issues like this on older versions of games using older graphics APIs, but stuff like that probably isn't a priority for Intel's driver team at this point. Their hardware is mostly focused on DirectX 12+/Vulcan (which is why their stuff is fine there, but then in DirectX 11 and prior they are often behind). Intel's entry into the dedicated market is more recent.
You probably need to fix this in the code if you want to play those versions on hardware that uses video drivers which result in this. Some versions may have publicly available fixes but I'm not sure what all of them are.
I wasn't specifically stating that you have to fix it yourself. Most people can't, and neither can I, but I was just saying that that the source of solving it would be either changing the code, or working around it some other way.
Whether you want to buy a specific graphics card for an outdated version of a single game is up to you. I'd consider that ridiculous, personally, but I'm looking at things in broader terms because it should be up to the software to adapt to the world around it, not the other way around. The problem here is that this does gets resolved in the software... in a later game version. So if you want to play those older game versions and they mean that much to you, then you may need certain hardware that has drivers which avoid this particular issue.
Alternatively, the better fix the issue with the game itself because will the drivers always ignore the issue? But not everyone can do that.
I think a few versions do have fixes released, like I said, but I'm not sure what/where they are. I just know they exist for a few versions. 1.7.10 is one of them. I'm not sure if 1.0 is.
I wanted to see the first release of Minecraft Java so i made a instance and clicked new world. Here's what happened.
Someone will make a HL1 or HL2 mod. Right?
The actual issue is with the game itself from what I recall, despite usually only being seen on Intel graphics since their drivers don't ignore/work around it. This leads to many blaming Intel or its drivers as the cause when its the game. Both nVidia and AMD hardware had this begin to happen on older drivers if I'm not mistaken, but then it stopped occurring with them. I would imagine they both probably simply went back to ignoring/working around this issue. Likewise, very old Intel drivers don't have the issue but using older drivers is not always a solution.
This occurs in the window of versions after beta 1.7.3 but before release 1.8 (if VBOs are enabled, otherwise it can continue to occur up until release 1.12 or 1.13). A change was made to beta 1.8 that, at the time, made no effective difference (drivers of the time were less strict), but it sometimes does with drivers now. nVidia and AMD are probably more likely to have decades of built up workarounds for obscure issues like this on older versions of games using older graphics APIs, but stuff like that probably isn't a priority for Intel's driver team at this point. Their hardware is mostly focused on DirectX 12+/Vulcan (which is why their stuff is fine there, but then in DirectX 11 and prior they are often behind). Intel's entry into the dedicated market is more recent.
You probably need to fix this in the code if you want to play those versions on hardware that uses video drivers which result in this. Some versions may have publicly available fixes but I'm not sure what all of them are.
Overallsteak748 I'm using the normal Minecraft launcher
Someone will make a HL1 or HL2 mod. Right?
Princess_Garnet But what if I don't know how to code? Do i just get a new graphics card?
Someone will make a HL1 or HL2 mod. Right?
I wasn't specifically stating that you have to fix it yourself. Most people can't, and neither can I, but I was just saying that that the source of solving it would be either changing the code, or working around it some other way.
Whether you want to buy a specific graphics card for an outdated version of a single game is up to you. I'd consider that ridiculous, personally, but I'm looking at things in broader terms because it should be up to the software to adapt to the world around it, not the other way around. The problem here is that this does gets resolved in the software... in a later game version. So if you want to play those older game versions and they mean that much to you, then you may need certain hardware that has drivers which avoid this particular issue.
Alternatively, the better fix the issue with the game itself because will the drivers always ignore the issue? But not everyone can do that.
I think a few versions do have fixes released, like I said, but I'm not sure what/where they are. I just know they exist for a few versions. 1.7.10 is one of them. I'm not sure if 1.0 is.
Oh ok, thanks!
Someone will make a HL1 or HL2 mod. Right?
This is a bug that has to do with the new intel drivers since late 2021 and there's a fix for Many versions
"I stand on my ground"