I've been playing Release 1.6.4, and for some reason, after flying in Creative Mode in a world for a bit, a visual bug will start to occur, where chunks will start glitching in and out of rendering. All the chunks around me become absolute visual chaos as they keep flickering. Just recently, a horrible visual glitch was occurring all across my screen as well while I was in glitched chunks. Any way to fix this?
If you use nVidia video hardware, go into the control panel and disabled "threaded optimization" and see if that helps. To this day in current versions, that setting at the default value can apparently causes performance/stutter issues, and in the past, it would cause the sort of thing you're describing, but I think it only tended to happen with OptiFine and with multi-core chunk rendering.
In theory, i think this is supposed to potentially (key word) improve performance in some situations (key word), but in reality if often seems to also do the opposite, and namely, it can introduce input delay/input inconsistency, and it can seems especially in CPU limited scenarios (perhaps a clue, since Minecraft is like this), that it is often recommended to be set off.
As always, best do to do you own testing and if you don't see a major difference, leave it alone.
If it's not that (or you don't have nVidia hardware, which doesn't have that setting), then I don't know. I think 1.3 through 1.6.4 did have an issue with the render distance at far (which was bugged and limited to 10 chunks instead of 16) where some chunks would disappear, but I don't think they would flicker.
Pictures of a video would help though because this "visual chaos" could be incorrect geometry due to an unstable video card? If it's consistently just the chunks flickering and everything else is fine though, then that's less likely.
This sounds a lot like a widely-reported issue with AMD cards, due to a driver memory leak, it manifests after some time, depending on how often chunks get updated (much more often with flying around), due to a driver-side memory leak which eventually exhausts VRAM, then all system resources (it ha even been reported to crash the entire system).
Luckily, the latest driver (24.8.1) fixed the issue, or so it claims:
If you use nVidia video hardware, go into the control panel and disabled "threaded optimization" and see if that helps.
This no longer works since the setting is overridden when Minecraft is running, unless you use certain 3rd party launchers (it searches for ".main", as in "net.minecraft.client.main.Main", the pointer to the class that starts running when the game is launched)
I don't know what driver versions that pertains to, and there may undoubtedly be people using driver versions older than that (or with third party launchers, as you stated), so saying "that no longer works" seems a bit presumptuous, no? That is, that may become the more common norm going forward, but we don't have the information from the thread starter to presume that right now.
This is the idea behind "information in, information out". Until we have more details, we can only give broad recommendations (as opposed to specific ones where we can rule out certain things).
In any case, I brought it up because historically (back then, and even today), it has been known to cause issues in some circumstances,so it's worth recommending until we have more information (such as "I don't even have nVidia video hardware").
As for being low/out of VRAM, when that happens, system memory will start being used. Up to half of a system's memory can be used for this purpose. This will typically have performance implications (because it's now accessing memory over the PCI Express bus, which is much slower than the bandwidth between the GPU and obnboard dedicated VRAM), but it shouldn't cause issues otherwise. Now once that is exhausted (or even a bit before that point, especially if the system memory is low enough that being left with as little as half of the RAM results in too little being available for the OS/game/applications), then I'd expect some sort of crashes as opposed to visual glitches. I'm not saying this isn't possible, and maybe you're even going off established results from what others have reported.
The thread starter does mention it happens only after flying in creative for a bit, so it's possible it could be either, depending on how long "a bit" is, and how much VRAM/system RAM the PC has (the less there is, the sooner it would occur, especially since as I understand it, the issue causing this VRAM use accumulates fast).
The last time I tried 1.6.4, I saw oddities with chunks visually disappearing. Not flickering, and not with other visual anomalies or issues, but chunks would just disappear, often when near the edge of the render distance. I do currently have an AMD video card, but my VRAM was nowhere near full at the time, and I remember you saying there was a reason this could occur in those older versions (probably 1.3 through 1.6?), especially at "far", which I was playing on, with chunks near the edges or something.
But yeah, it could be a number of things, and until the thread starter gives more details, I don't think we can rule any of these out yet.
This is the idea behind "information in, information out". Until we have more details, we can only give broad recommendations (as opposed to specific ones where we can rule out certain things).
Aside from an AMD driver issue, I found a video on Reddit which looks like what they may be describing and it appears to be a different manifestation of the Intel driver issue; the video starts with smooth lighting turned off, which has chunks flickering and becoming invisible, then they turn it on and instead of becoming invisible you get the much more familiar missing textures (missing as in no texture but the blocks themselves are still colored according to their tint; green grass/leaves, white everything else). Another thing that identifies this issue is that entities are black and holding an item cases the entire screen to glitch out:
Also, the easiest way to install this may be to add it to an Optifine jar, replacing the file inside, then install Optifine as normal (via the installer or as a Forge mod. For all I know it may even be possible to install larger mods like TMCW in this manner, removing all the Optifine files first so only the installer is left). It does seem to conflict with some of its functionality but that doesn't seem to matter for its basic use, only more advanced features like anisotropic filtering (only the original fix has been tested with Optifine):
Yeah, that's mostly why I asked for clarification or even a picture/video example to know exactly what's going on.
Having dealt with tech/PC support long enough has taught me that sometimes, people will describes things one way and it will be completely different. Often times, a certain issue will be given a term that it's not (such as calling outright graphical corruption screen tearing), or they describe something as an issue that isn't necessarily an issue, but just a fact of life with how PCs work (so, more of an expectation not matching reality issue), and so on. I'm not saying the thread starter is doing this, but more information is always helpful when in doubt. Broad descriptions without details get broad, maybe not applicable, answers until more information is given.
I never knew the "lack of OpenGL compliance situation" (not sure what else to call it) could result in something totally different depending on whether smooth lighting is on or off. I've only seen it the way it is shown with it on, but the other way almost looks like it could match what they describe.
I've been playing Release 1.6.4, and for some reason, after flying in Creative Mode in a world for a bit, a visual bug will start to occur, where chunks will start glitching in and out of rendering. All the chunks around me become absolute visual chaos as they keep flickering. Just recently, a horrible visual glitch was occurring all across my screen as well while I was in glitched chunks. Any way to fix this?
If you use nVidia video hardware, go into the control panel and disabled "threaded optimization" and see if that helps. To this day in current versions, that setting at the default value can apparently causes performance/stutter issues, and in the past, it would cause the sort of thing you're describing, but I think it only tended to happen with OptiFine and with multi-core chunk rendering.
In theory, i think this is supposed to potentially (key word) improve performance in some situations (key word), but in reality if often seems to also do the opposite, and namely, it can introduce input delay/input inconsistency, and it can seems especially in CPU limited scenarios (perhaps a clue, since Minecraft is like this), that it is often recommended to be set off.
As always, best do to do you own testing and if you don't see a major difference, leave it alone.
If it's not that (or you don't have nVidia hardware, which doesn't have that setting), then I don't know. I think 1.3 through 1.6.4 did have an issue with the render distance at far (which was bugged and limited to 10 chunks instead of 16) where some chunks would disappear, but I don't think they would flicker.
Pictures of a video would help though because this "visual chaos" could be incorrect geometry due to an unstable video card? If it's consistently just the chunks flickering and everything else is fine though, then that's less likely.
This sounds a lot like a widely-reported issue with AMD cards, due to a driver memory leak, it manifests after some time, depending on how often chunks get updated (much more often with flying around), due to a driver-side memory leak which eventually exhausts VRAM, then all system resources (it ha even been reported to crash the entire system).
Luckily, the latest driver (24.8.1) fixed the issue, or so it claims:
https://www.reddit.com/r/GoldenAgeMinecraft/comments/1f4vbrk/amd_just_fixed_the_memory_leak_bug/
This no longer works since the setting is overridden when Minecraft is running, unless you use certain 3rd party launchers (it searches for ".main", as in "net.minecraft.client.main.Main", the pointer to the class that starts running when the game is launched)
https://github.com/CaffeineMC/sodium-fabric/commit/8ae68cfa82949a09d53b6ea066ebdba40d5674d4
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 don't know what driver versions that pertains to, and there may undoubtedly be people using driver versions older than that (or with third party launchers, as you stated), so saying "that no longer works" seems a bit presumptuous, no? That is, that may become the more common norm going forward, but we don't have the information from the thread starter to presume that right now.
This is the idea behind "information in, information out". Until we have more details, we can only give broad recommendations (as opposed to specific ones where we can rule out certain things).
In any case, I brought it up because historically (back then, and even today), it has been known to cause issues in some circumstances,so it's worth recommending until we have more information (such as "I don't even have nVidia video hardware").
As for being low/out of VRAM, when that happens, system memory will start being used. Up to half of a system's memory can be used for this purpose. This will typically have performance implications (because it's now accessing memory over the PCI Express bus, which is much slower than the bandwidth between the GPU and obnboard dedicated VRAM), but it shouldn't cause issues otherwise. Now once that is exhausted (or even a bit before that point, especially if the system memory is low enough that being left with as little as half of the RAM results in too little being available for the OS/game/applications), then I'd expect some sort of crashes as opposed to visual glitches. I'm not saying this isn't possible, and maybe you're even going off established results from what others have reported.
The thread starter does mention it happens only after flying in creative for a bit, so it's possible it could be either, depending on how long "a bit" is, and how much VRAM/system RAM the PC has (the less there is, the sooner it would occur, especially since as I understand it, the issue causing this VRAM use accumulates fast).
The last time I tried 1.6.4, I saw oddities with chunks visually disappearing. Not flickering, and not with other visual anomalies or issues, but chunks would just disappear, often when near the edge of the render distance. I do currently have an AMD video card, but my VRAM was nowhere near full at the time, and I remember you saying there was a reason this could occur in those older versions (probably 1.3 through 1.6?), especially at "far", which I was playing on, with chunks near the edges or something.
But yeah, it could be a number of things, and until the thread starter gives more details, I don't think we can rule any of these out yet.
Aside from an AMD driver issue, I found a video on Reddit which looks like what they may be describing and it appears to be a different manifestation of the Intel driver issue; the video starts with smooth lighting turned off, which has chunks flickering and becoming invisible, then they turn it on and instead of becoming invisible you get the much more familiar missing textures (missing as in no texture but the blocks themselves are still colored according to their tint; green grass/leaves, white everything else). Another thing that identifies this issue is that entities are black and holding an item cases the entire screen to glitch out:
https://www.reddit.com/r/GoldenAgeMinecraft/comments/17uy71r/how_do_i_fix_this_this_happens_with_10_to_16_i/
In this case there is already a solution which I made a year ago, and more recently, an improved version:
https://www.dropbox.com/scl/fi/cnhayr0rwbkh9d7h7j6h4/1.6.4_opengl_fix.zip?rlkey=vkyn73bzwiiao7t7tag589t4z&dl=0
Also, the easiest way to install this may be to add it to an Optifine jar, replacing the file inside, then install Optifine as normal (via the installer or as a Forge mod. For all I know it may even be possible to install larger mods like TMCW in this manner, removing all the Optifine files first so only the installer is left). It does seem to conflict with some of its functionality but that doesn't seem to matter for its basic use, only more advanced features like anisotropic filtering (only the original fix has been tested with Optifine):
https://www.minecraftforum.net/forums/mapping-and-modding-java-edition/minecraft-mods/1294926-themastercavers-world?comment=351
Either way, more information is needed to know the exact issue.
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?
Yeah, that's mostly why I asked for clarification or even a picture/video example to know exactly what's going on.
Having dealt with tech/PC support long enough has taught me that sometimes, people will describes things one way and it will be completely different. Often times, a certain issue will be given a term that it's not (such as calling outright graphical corruption screen tearing), or they describe something as an issue that isn't necessarily an issue, but just a fact of life with how PCs work (so, more of an expectation not matching reality issue), and so on. I'm not saying the thread starter is doing this, but more information is always helpful when in doubt. Broad descriptions without details get broad, maybe not applicable, answers until more information is given.
I never knew the "lack of OpenGL compliance situation" (not sure what else to call it) could result in something totally different depending on whether smooth lighting is on or off. I've only seen it the way it is shown with it on, but the other way almost looks like it could match what they describe.