1.7.10 Forge
Agenor Ramadan
Try downgrading your driver; this has worked for others with the same issue currently affecting Intel GPUs (like any other software drivers can have bugs so newer is not always better; given how widespread this issue has become, with multiple reports daily now on the forums, Reddit, etc, this almost certainly points to a broken driver update and a true fix will have to wait for Intel to fix it).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
I was really frustrated! All of my 1.7 packs broke. Looking at certain blocks sometimes permanently made the window go black until I restarted minecraft. I'm glad I found this, but downgrading our drivers should never be a permanent fix.
I don't think that Intel is even aware of this issue yet; I could only find one relevant report on their official support page and the person who created it just disappeared without a resolution (unfortunately, this happens far too often; worse is when there is a resolution but they never say how they fixed it; of course, as you said downgrading is not a permanent fix):
-3d-settings/m-p/1403970
Any news on this? A lot of my friends have this issue and I'm unable to help as it runs perfectly fine on my PC (Win 11, Nvidia). My friend has an Intel iGPU, I believe the UHD 620, and he has the same issue.
Downgrading drivers or using a dedicated GPU are still the only solutions that I've been able to find; the only other clue is that it appears to only affect release 1.0.0-1.7.10, but not newer or older versions, suggesting that there is something unique to these versions, but nobody has attempted to find/try to fix it (as far as I can find, probably locked away on a Discord somewhere, where it can't be found with a public search); I can't check myself (I have an Intel HD 4000 but it is disabled/unusable, and such an old GPU may not experience the same issue, most/all reports have mentioned newer GPUs, mainly UHD) but one possible clue is that they added a "lightmap" texture (this is combined/overlayed with normal textures and enables the game to seamlessly change sky light brightness without having to re-render chunks, as well as add a "flicker" effect to block light), no idea how this relates to held items completely breaking rendering though (the code seems to be the same, that said, this is based on online code snippets from Beta 1.7.3 compared to release 1.6.4; ideally you'd compare the entire rendering codebases for the closest working/broken versions to minimize differences (release 1.8+ doesn't have this issue either but its rendering code is very different so it is not a good comparison).
There are mods which include a patch that fixes this issue, one of them being CoreTweaks:
Note: I've previously recommended ArchaicFix elsewhere but for some reason they decided to remove their patch, recommending CoreTweaks instead, such is the curse of relying on 3rd party mods (ideally somebody would make a mod that solely exists to patch the issue. I also only know of mods for 1.7.10 specifically, unless you count my own "jar" patch for 1.6.4, though it seems to be Forge compatible).
Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:
When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.
When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.
Personally, 1.7.10 will always have a special place in my heart. While I was a beta player, I never really got into modded until 1.7.10. That being said, I was one of the people that was very resistant to the combat update, but I came around eventually. New mods and packs eventually won out, and here I am on the bleeding edge with the rest of what I used to refer to as "the crazies". Some of my favorite packs of all time are back on 1.7.10, and I don't think that's likely to change any time soon. Outdated, sure. Obsolete? Not hardly!
I wasn't trying to argue semantics as much as show some love for 1.7.10, however, "obsolete" is defined as "no longer produced or used". While yes, it's no longer being used by Mojang in their current releases (at least not in its entirety), the code is still being used by "lazy modders" and too many players to speculate on an actual number. I would then submit that it is, by definition, not obsolete, just old.
Basically, 1.7.10 version is the best version to use in custom forge servers with friends.
It's not only my opinion, we done a test and if 1.8.9 or 1.12 are the most powerfull ones, 1.7.10 still the best if you don't have a server and want to host a VPN to play with your friends.
Crete mods for 1.7.10 means create costum content for and/or with your friends.
Staying in 1.7 is not only a dumb resistance for change, its a dishonest way to fool new players and (mainly) modpackers and server admins to stay with a very old version with more problems and less features.
Everything became more clear and nice to tweak in my opinion. Even for mods it really impacted. Remember the old AtomycStryker Ruins mod? Vazkii made Pillar, which use the vanilla structure system and is far more easy to make than the former. There are also other examples similar in which a new replacement mod does things far less shady than their precursor and uses more the available vanilla systems (perharps NEI > JEI can count).
There only a small couple of mods i lost, but i would say its more because of Bukkit drama and shutdown than the 1.8 transition: TrainCarts (i still waiting for someone to make this), perharps Lockette (but Vanilla introduced a way to lock chests already), the permission system (althourgh i dont play multyplayer enough and with so much people to actually require it) and any mod to change the Villager models to Humans (i think today this would be a violation of EULA, but MCA is somewhat still going).
Anyway for any modder still coding only for 1.7: PLEASE dont force your players to stick with a version so old and with so few features Beta was good but this new versions are EXCELLENT, such amazing RPG-esque tematics for me were decisive to add a new breath to the game.
Players will tend to stay with what they like when they already have the game experience they want. If players are sticking with 1.7 at least a few modders will stick with it as well because they are likely playing 1.7 as well. It really just comes down to personal preference.
c80f0f1006