Massive Visual Glitching with VBOs off and Chunk distance over a level the graphics card cannot handle (Caused by outdated AMD drivers)

I have noticed that if I set my Render Distance to 20(20 and above would cause the issue) and reload the world, then 20 and below would be ok and everything above would cause the issue. So I set my distance to 32 and reloaded..... Now everything works fine, I'll be sure to post here if the issue shows up again.

EDIT #1: Just loaded my world up on 32 distance, no chunks loaded at all except for the ones that were within a 2 chunk radius of me. I will experiment with VBOs and post back here.

EDIT #2: Ok, so I turned the distance down to 20 and reloaded again. Now everything works perfectly, with VBOs on and off. Seems like this is just a bug with older worlds, none of my worlds created on the snapshot have this issue.

EDIT #3: Ruh roh.... Now that all of my chunks load fine, none of the entities in my game will function... Mobs don't move and I can't interact with them, can't pick up items, can't open chests, etc.

Confirmed for 14w30c somehow the normal (not villager) zombie model get bugged and after changing the chunk distance it was still bugged (only reopening Minecraft helped)

Been discussing this with folks on our server and this appears (for us at the moment) to be limited to people using AMD/ATI graphics cards. I myself have a Radeon 7850 and am having this. Two others have reported the same issue. When changing render distance to 10 it goes away. Have not tried a progressive scale down, but 16 distance has the problem. I have heard someone testing with render distance 32 and it not being an issue.

We also ugraded to 14w31a and it is still an issue in that snapshot as well.

According to MC-64829, allocating 2GB of RAM to Minecraft seems to fix the issue. Can anyone else confirm this?

@Blah I confirm that in MC-64829 Allocating 2GB of ram solves the issue.

May be possible, all of the 6 screenshots here have <= 1GB allocated.

I have 3G allocated and am still experiencing this. I have also tried all render distances from 11-32 and none work for me. Lowering it to 10 seems to clear it up.

I have upgraded my video drivers to the latest (catalyst 14.4) and am running the latest Java 7 and still have the issue (though FPS is slightly better, but still not what it was in 1.7.9).

https://www.youtube.com/watch?v=bNMjMasDJak
See it.

I've allocated 2GB of ram and render distance over 10 chunks will cause this glitch

I have just tried with 4gb of ram allocated and it no longer seemed to clitch

It seems that when you go over the 16 chunk distance you need at least 4 GB or more allocated or the game won't work as do most 64 bit programs that require more than 4 GB or they won't work properly.

This issue does, as far as I checked, only affect AMD graphics cards, and a 'fix' would be to disable any distances higher than 16 for AMD cards.

I haven't seen it in a while, however I have an nVidia card so I don't think it is specific to AMD.

@everyone having this issue:
Please force a crash by pressing F3 + C for 10 seconds while in-game and attach the crash report ([minecraft/crash-reports/crash-<DATE>-client.txt|http://hopper.minecraft.net/help/finding-minecraft-data-folder]) here _{(or leave the} OpenGL _{line of the crash report as a comment here)}

My graphics card (AMD 6700 w/ Catalyst 14.10-rc) is affected:

OpenGL: AMD Radeon HD 6700 Series GL version 4.4.12967 Compatibility Profile Context 14.200.1004.0, ATI Technologies Inc.

OpenGL: GeForce GTX 765M/PCIe/SSE2 GL version 4.4.0, NVIDIA Corporation

OpenGL: AMD Radeon HD 6450 GL version 4.4.12874 Compatibility Profile Context 14.100.0.0, ATI Technologies Inc.

Made https://bugs.mojang.com/browse/MC-66614 then found this - Crash log attached.

I was seeing this issue with render set above 12
then with 4G allocated and VOB on was ok at 32
then made new world and nothing rendered, sank to Y=0, only saw the particles that you see when Y < 6

---- Minecraft Crash Report ----
// Why did you do that?

Time: 8/10/14 9:14 PM
Description: Manually triggered debug crash

java.lang.Throwable
	at bsn.r(SourceFile:1566)
	at bsn.as(SourceFile:875)
	at bsn.a(SourceFile:312)
	at net.minecraft.client.main.Main.main(SourceFile:120)


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Stacktrace:
	at cee.a(SourceFile:308)

-- Affected level --
Details:
	Level name: MpServer
	All players: 1 total; [cif['ALostDog'/40764, l='MpServer', x=-53.50, y=-0.01, z=261.50]]
	Chunk stats: MultiplayerChunkCache: 0, 0
	Level seed: 0
	Level generator: ID 04 - customized, ver 0. Features enabled: false
	Level generator options: 
	Level spawn location: -44.00,64.00,256.00 - World: (-44,64,256), Chunk: (at 4,4,0 in -3,16; contains blocks -48,0,256 to -33,255,271), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
	Level time: 3726 game time, 3726 day time
	Level dimension: 0
	Level storage version: 0x00000 - Unknown?
	Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false)
	Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
	Forced entities: 1 total; [cif['ALostDog'/40764, l='MpServer', x=-53.50, y=-0.01, z=261.50]]
	Retry entities: 0 total; []
	Server brand: vanilla
	Server type: Integrated singleplayer server
Stacktrace:
	at cee.a(SourceFile:308)
	at bsn.b(SourceFile:2255)
	at bsn.a(SourceFile:321)
	at net.minecraft.client.main.Main.main(SourceFile:120)

-- System Details --
Details:
	Minecraft Version: 14w32d
	Operating System: Windows 7 (amd64) version 6.1
	Java Version: 1.7.0_65, Oracle Corporation
	Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
	Memory: 272785072 bytes (260 MB) / 1694318592 bytes (1615 MB) up to 4281597952 bytes (4083 MB)
	JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx4G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
	IntCache: cache: 1, tcache: 1, allocated: 12, tallocated: 94
	Launched Version: 14w32d
	LWJGL: 2.9.1
	OpenGL: AMD Radeon HD 6530D Graphics GL version 4.1.11079 Compatibility Profile Context, ATI Technologies Inc.
	GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.

	Using VBOs: Yes
	Is Modded: Probably not. Jar signature remains and client brand is untouched.
	Type: Client (map_client.txt)
	Resource Packs: []
	Current Language: English (US)
	Profiler Position: N/A (disabled)

I've had that happen once when adjusting the chunk distance down to 8. All I get is the same chunk at the edge of world generation, acting as a barrier of sorts.

same problem here, for render distance set above 16 in 14w32d

@August Junkala:
Can you reporduce this issue by raising the view distance over 16 and VBO off? If not, then this issue only occurs on AMD cards, you are the only ones stating that it once happened on Nvidia as well.

Not that it matters, but I filed the bug so telling me the issue doesn't affect nVidia doesn't make a whole lot of sense to me.

To answer your question though, no I am not getting the issue any more. I haven't seen it in any sessions since the first instance. Just to be sure, I just started a fresh world and the only issue I saw was one reported by another user when first entering a world: only the chunk I was in generated. I could walk off the edge and slowly fell off until a few minutes later when the geometry started filling in.

When exploring new areas I use the highest available view distance (16 when I saw the issue, 32 now) otherwise I use 16 or lower (no point swapping extra chunks I can neither see nor have any need to see). I have always played with VBO off (the default as far as I am aware). Also when I saw the issue, I used the default❓ mem size (1GB), although bumped it to 2GB when 32 view distance was added since that feature is disabled with a smaller mem size.

Other issues I suspected could be related have also disappeared (i.e. chunk visual updates are no longer severely lagged, and chunks don't periodically fail to generate visible geometry at all).

Possibly fixes that are unexpectedly not universal (e.g. the AMD chipsets w/ problems can't take advantage of the fix).

I see this issue whenever I increase my render distance from 11 or below to 12 or above. Restarting the game (not reopening the map or relogging from the server) fixes the issue, and the issue only happens if my render distance is set to 11 or below when I start the game.

And yes, I have an AMD Radeon HD graphics card.

EDIT: And of course as soon as I post this it completely stops happening. Still, I have had this happen several times when increasing render distance and I am quite sure it was the switch from 11- to 12+ that triggered it, as I definitely just had it happen when I changed from 11 to 12. It's also worth noting that turning your render distance back down removes the glitch.

I still get the visual glitching. VBO was off and render distance set to max

@Jason Webb: Screenshot with F3 open please.

Still get the Glitch on 14w34b, VOB off by changing the render distance to >16. VOB on solved the Bug.
If I start the game with render distance >16 VOB off, I don`t get the glitch. Only by changing distance ingame.

OpenGL: ATI Radeon HD 4800 Series GL version 3.3.11672 Compatibility Profile Context, ATI Technologies Inc.

Can confirm what @unknown wrote (AMD 6700, Catalyst 14.7 beta)

Everything is up to date.

screenshots taken at 19 chunk render distance.

Open GL line from crash report:

OpenGL: AMD Radeon HD 7520G GL version 4.2.12420 Compatibility Profile Context 13.151.0.0, ATI Technologies Inc.

Same problem with viewing distance over 12.

Launched Version: 14w34b
LWJGL: 2.9.1
OpenGL: AMD Radeon HD 5800 Series GL version 4.4.12874 Compatibility Profile Context 14.100.0.0, ATI Technologies Inc.
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.

Using VBOs: No

This is an error with running low on memory. I experienced it while playing minecraft modded, with a 128x resource pack and 1 gig of ram. Just add 1 or 2 more gigs of ram and the issue should be fixed. I also see that you are low on ram allocated to the game in the F3 screen.

@Michaelx3: no, same problem with vanilla texturepack and 4 gigs free ram, just for java.

Glitching in 34b.

Can't reproduce it anymore in 14w34d. Now I can play fine with 32 Chunk distance, with and without VBO. Fixed for me.

With Render Distance set to "9 chunks"

Similar to Jay Blunt, cannot reproduce either in 14w34d.

I can reproduce it in 14w34d.

Same problem. Forced crash log.
AMD Readon HD 6870 Graphics Card

Same problem, 14w34b. Forced crash log.

Same problem, I am also using a AMD Radeon HD 7570M/HD 7670M (intergraded graphics card). Forced crash log attached.

This needs to be fixed out of all the other ones so far. No crashes so far, and it seems that when this bug happens the RAM usage is unusual high taking up to 80%+ and my PC slows down. I think the VBO option is the whole problem of this as nothing else does this.

Able to reproduce this with 1.8 pre1, using AMD Radeon HD 5770.

So... yes, this is AMD dependent.

Confirmed for 1.8 pre1 using a AMD Radeon HD 7770

I'm having this problem, too. I have an ATI Radeon X1600.

This sounds like my problem. First occurred when I boosted the render distance form 10 up to 16. I had it on 10 to speed generation of a brand new world then changed to 16 once we'd explored a bit. It seems to create this glitchy pattern whenever I have the chunk render distance above 10. That being said, it varies. 16 and above everything glitches out. 13+ everything more than 2 chunks away to one direction (eg. West) of my current position glitches out. 11-12, just a few chunks in the distance glitch out.

edit: running an HD 7770. VBO is off. 16Gb RAM (minecraft set to use min 2Gb max 4Gb.

OpenGL: AMD Radeon R9 200 Series GL version 4.4.12874 Compatibility Profile Context 14.100.0.0, ATI Technologies Inc.

Visual output: http://puu.sh/b4yOL/a01337ebc7.jpg
This flashed and changes when i move around. This happend after i changed my Render distance inside the Client from 8 to 32

It seems AMD dependent but the very interesting thing is that this only occurs for me if I haven't a resource pack but with one i haven't this glitch i retry it without an resource pack and if this makes a difference I'll start to deobfuscate the code to see whats going on .

Ok at the moment i can't recreate it but as it has occured for me I had the LAN server running maybe this has something to do with it ...

No. It is an issue that either happens w/ low frequency on nVidia cards, or has been fixed on that chipset in the interim. Either way that is information that is helpful to programmers in identifying what the issue is. It allows changes that have been made recently to be evaluated as potentially exposing discrepancies between AMD and nVidia chipsets. If it has been fixed, that narrows down the possible set of commits to look at.

Low-level issues like this are a pain to diagnose to begin with; discarding information is not helpful.

this Happens to me but only after I change my skin.

Video - https://www.youtube.com/watch?v=_GuZaipnt3U&list=UU6xCBWcp4WTL_DVozEsC94Q

Hi all,
I had this issue but was resolved after updating to the latest available AMD graphics driver from their support site
OS: Win8.1 Pro AMD64, GPU: HD6850, JRE7u51, MC 1.8-pre1.
The problem was present using the automatically downloaded Windows Update driver.

Hi all, been playing with my settings. Running win 7 Pro 64 Bit OS in Alienware Aurora. With the latest JAva 64 Bit edition 67 and java setting inprofile to 4G max I can now use up to 14 chunks with no issues. Go to 15 chunks and it acts as going to 13 before upgrading my java version. Not sure if this helps anyone but it appears to have given me 2 more chunks. Better than nothing.

also experiencing the same problem after 10 chunk render distance. very glitching and flashing

Minecraft 1.8-pre2

I only seem to experience this bug after I change my render distance to 10 or more. 9 and below has no issue.

Crash report after getting the bug & force crashed with F3+C

I got this bug when setting up my view distance to 32 from 16. (1.8-pre2)

As Arusu said, changing the view distance causes this. I recorded it, with wobble shaders to make it worse. This is always fun to watch, while confusing your brain a little: https://www.youtube.com/watch?v=hygpaf8mqc0

I have the same issue when setting my render distance over 17. I've attached a gif that shows what I see.

It may be related to the ram of the graphic card or something like that... I mean it may be a lack of ressources but still a bug.

Crash report added as requested. Interestingly I found that though my device driver update check says there were no updates, a new version of the AMD catalyst control centre found a newer one and duly installed it. I can now go from 12 to 15 chunks with no issues. A small step for minekind.

OpenGL: AMD Radeon HD 7900 Series GL version 4.4.12874 Compatibility Profile Context 14.100.0.0, ATI Technologies Inc.
GL Caps: Using GL 1.3 multitexturing.

Have just been straining my brain on memory settings and for some reason decided to go and change my JVM argument in my game profile to the following -Xmx8G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M. I can now work at the maximum chunk setting of 32 with no apparent screen glitches. I have tried it at in-between settings and its stable. Oh happy days.

@Michael Mapstone

sucks for people with 4GB or less RAM 😞

Yeh, sorry about that Tristan and I agree it does suck. It does however lead one to the view that the whole issue is actually more one of resource usage by the game and not necessarily the AMD video cards that it has been targeted at. Perhaps the Mojang team can take a look at this?????????????

Tested in two machines:
1: Desktop AMD FX-8350 (8 cores at 4Ghz), 16Gb RAM, Radeon HD7870, Win7 x64, Java 1.8.0_20 x64
2: Laptop AMD A10-5750 (4 cores at 3,5Ghz), 8Gb RAM, Radeon R9-M290X, Win7 x64, Java 1.8.0_20 x64
Same result. Crash dump & screenshot is from the Desktop.
Viewing distance is 13 chunks. Setting it to 12 fixes all problems.

Asked line of crash dump:
OpenGL: AMD Radeon HD 7800 Series GL version 4.4.12967 Compatibility Profile Context 14.200.1004.0, ATI Technologies Inc.

Edit: I tried the solution by Michael Mapstone (JVM argument -Xmx8G), I can't use the maximum viewing distance, but now the corruption shows at 17 chunks or greater. At 16 chunks it works well so far.

Do the chunks rapidly flicker between different rendering options? When I get this bug, the chunks change rapidly between different biomes and physical features.

Ferran, What driver do you have for your Radeon HD7870. It should be:

Display Driver ver. 14.10.1006
OpenCL(tm) Driver ver. 10.0.1348.5

I ask this as when I upgraded to these for my 7900, it made a notacible difference. By teh way the normal upgrade checker does not necessarily work. you may have to down load the updated AMD Catalyst Centre to get it as there is a conflict in the normal checker. Have a look at: http://support.amd.com/en-us/kb-articles/Pages/AMDCatalyst14-4WINReleaseNotes.aspx.

cheers

Michael,
I have the Catalyst 14.7 beta (because I had some problems with Wolfestein: TNO and I already had the lastest stable release installed). This version is still the lastest publicy avaible.
I know it's a beta, but everything works perfecly (and by the way, the problems with Wolfestein didn't get fixed by installing this beta driver)
Version info on the CCC say my version is 14.20.1004-140709a-173735E

I've found it in 1.8-pre3 😞

Minecraft Crash Report ----
// Surprise! Haha. Well, this is awkward.

Time: 8/28/14 9:25 PM
Description: Manually triggered debug crash

java.lang.Throwable
at bss.r(SourceFile:1563)
at bss.as(SourceFile:877)
at bss.a(SourceFile:314)
at net.minecraft.client.main.Main.main(SourceFile:120)

A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

– Head –
Stacktrace:
at cel.a(SourceFile:308)

– Affected level –
Details:
Level name: MpServer
All players: 1 total; [cim['Squawkers13'/109, l='MpServer', x=-636.50, y=89.09, z=187.37]]
Chunk stats: MultiplayerChunkCache: 961, 961
Level seed: 0
Level generator: ID 00 - default, ver 1. Features enabled: false
Level generator options:
Level spawn location: 0.00,64.00,192.00 - World: (0,64,192), Chunk: (at 0,4,0 in 0,12; contains blocks 0,0,192 to 15,255,207), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
Level time: 51930 game time, 5836 day time
Level dimension: 0
Level storage version: 0x00000 - Unknown?
Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false)
Level game mode: Game mode: creative (ID 1). Hardcore: false. Cheats: false
Forced entities: 90 total; [abo['Bat'/30720, l='MpServer', x=-604.48, y=22.85, z=242.70], abo['Bat'/9218, l='MpServer', x=-596.34, y=14.19, z=121.25], abo['Bat'/23825, l='MpServer', x=-633.75, y=15.10, z=240.25], aen['Creeper'/30487, l='MpServer', x=-571.50, y=22.00, z=225.50], afu['Skeleton'/30488, l='MpServer', x=-583.50, y=30.00, z=129.50], aen['Creeper'/30489, l='MpServer', x=-585.50, y=30.00, z=125.50], aen['Creeper'/30490, l='MpServer', x=-584.50, y=30.00, z=130.50], agh['Zombie'/14621, l='MpServer', x=-628.63, y=45.00, z=160.97], abo['Bat'/29470, l='MpServer', x=-662.47, y=52.07, z=123.63], aco['Squid'/30754, l='MpServer', x=-603.50, y=59.94, z=215.41], aco['Squid'/30755, l='MpServer', x=-604.22, y=61.09, z=211.31], aco['Squid'/30756, l='MpServer', x=-607.56, y=57.28, z=208.69], aco['Squid'/30757, l='MpServer', x=-610.78, y=60.25, z=220.25], agh['Zombie'/21542, l='MpServer', x=-572.50, y=36.00, z=154.50], afu['Skeleton'/21543, l='MpServer', x=-572.50, y=36.00, z=155.50], agc['Spider'/7720, l='MpServer', x=-629.72, y=53.09, z=207.97], aen['Creeper'/29993, l='MpServer', x=-562.50, y=20.00, z=142.50], aen['Creeper'/29994, l='MpServer', x=-561.50, y=20.00, z=139.50], aen['Creeper'/30512, l='MpServer', x=-567.09, y=28.00, z=116.44], agh['Zombie'/30513, l='MpServer', x=-561.50, y=29.00, z=109.50], aco['Squid'/30770, l='MpServer', x=-681.69, y=59.16, z=244.88], aen['Creeper'/30515, l='MpServer', x=-564.88, y=28.00, z=116.78], aco['Squid'/30771, l='MpServer', x=-693.16, y=59.72, z=249.00], afu['Skeleton'/30517, l='MpServer', x=-617.50, y=13.00, z=116.50], aco['Squid'/30773, l='MpServer', x=-678.47, y=57.50, z=248.41], agh['Zombie'/30518, l='MpServer', x=-582.66, y=14.00, z=153.34], agh['Zombie'/30519, l='MpServer', x=-577.66, y=14.00, z=153.34], agh['Zombie'/30520, l='MpServer', x=-577.66, y=14.00, z=152.34], agh['Zombie'/30521, l='MpServer', x=-580.66, y=14.00, z=153.34], aen['Creeper'/30524, l='MpServer', x=-556.88, y=36.00, z=150.69], aco['Squid'/30782, l='MpServer', x=-595.03, y=57.72, z=184.22], aco['Squid'/30783, l='MpServer', x=-592.38, y=62.16, z=184.13], aco['Squid'/30784, l='MpServer', x=-586.50, y=59.69, z=190.78], aco['Squid'/30785, l='MpServer', x=-594.22, y=57.91, z=194.03], afu['Skeleton'/30283, l='MpServer', x=-620.50, y=29.00, z=216.50], afu['Skeleton'/30284, l='MpServer', x=-621.50, y=29.00, z=213.50], agc['Spider'/30287, l='MpServer', x=-642.50, y=50.00, z=235.50], aco['Squid'/30799, l='MpServer', x=-668.34, y=49.75, z=250.88], adg['Armor Stand'/3409, l='MpServer', x=-638.50, y=68.00, z=192.50], afu['Skeleton'/30289, l='MpServer', x=-645.53, y=50.00, z=239.66], afu['Skeleton'/22873, l='MpServer', x=-600.56, y=22.00, z=220.13], afu['Skeleton'/20320, l='MpServer', x=-564.50, y=36.00, z=153.50], cim['Squawkers13'/109, l='MpServer', x=-636.50, y=89.09, z=187.37], afu['Skeleton'/20343, l='MpServer', x=-690.25, y=16.00, z=204.69], aco['Squid'/30847, l='MpServer', x=-687.50, y=54.41, z=149.16], aco['Squid'/30848, l='MpServer', x=-684.28, y=50.09, z=142.59], aco['Squid'/30849, l='MpServer', x=-687.50, y=49.66, z=150.25], aco['Squid'/30850, l='MpServer', x=-686.84, y=50.00, z=146.22], afu['Skeleton'/30595, l='MpServer', x=-618.50, y=29.00, z=120.50], aen['Creeper'/30350, l='MpServer', x=-592.50, y=17.00, z=238.50], aep['Enderman'/30100, l='MpServer', x=-562.50, y=32.00, z=189.50], abo['Bat'/30874, l='MpServer', x=-614.25, y=36.41, z=215.50], agg['Witch'/20636, l='MpServer', x=-686.72, y=15.00, z=208.69], ads['Boat'/157, l='MpServer', x=-672.53, y=62.71, z=210.84], abo['Bat'/29858, l='MpServer', x=-630.25, y=62.10, z=190.75], abo['Bat'/24739, l='MpServer', x=-588.67, y=19.12, z=135.66], afu['Skeleton'/30887, l='MpServer', x=-643.28, y=49.00, z=199.19], afu['Skeleton'/30888, l='MpServer', x=-641.69, y=52.00, z=196.78], agc['Spider'/30889, l='MpServer', x=-646.19, y=49.00, z=197.81], agh['Zombie'/30122, l='MpServer', x=-653.50, y=14.00, z=216.50], abo['Bat'/30381, l='MpServer', x=-618.19, y=23.50, z=256.25], abo['Bat'/30638, l='MpServer', x=-705.08, y=13.04, z=240.11], aen['Creeper'/29878, l='MpServer', x=-658.50, y=17.00, z=231.50], abo['Bat'/30653, l='MpServer', x=-569.72, y=17.10, z=154.66], aen['Creeper'/20158, l='MpServer', x=-578.50, y=32.00, z=109.50], agh['Zombie'/20162, l='MpServer', x=-602.50, y=41.00, z=123.50], afu['Skeleton'/20169, l='MpServer', x=-560.50, y=20.00, z=136.50], afu['Skeleton'/30922, l='MpServer', x=-559.50, y=30.00, z=120.50], aco['Squid'/10957, l='MpServer', x=-599.22, y=55.06, z=204.06], afu['Skeleton'/30670, l='MpServer', x=-595.94, y=34.00, z=116.44], aco['Squid'/10961, l='MpServer', x=-618.28, y=56.97, z=217.63], abo['Bat'/24788, l='MpServer', x=-579.77, y=13.05, z=146.63], abo['Bat'/30676, l='MpServer', x=-562.49, y=25.88, z=229.34], aco['Squid'/10966, l='MpServer', x=-691.34, y=52.00, z=192.63], aen['Creeper'/30423, l='MpServer', x=-564.56, y=23.00, z=251.00], aen['Creeper'/30424, l='MpServer', x=-566.00, y=24.00, z=245.53], agh['Zombie'/30936, l='MpServer', x=-601.50, y=47.02, z=259.50], aen['Creeper'/30937, l='MpServer', x=-600.50, y=47.02, z=259.50], aen['Creeper'/30426, l='MpServer', x=-573.50, y=24.00, z=241.50], afu['Skeleton'/30436, l='MpServer', x=-621.50, y=21.00, z=248.50], aen['Creeper'/30190, l='MpServer', x=-582.50, y=44.00, z=203.50], afu['Skeleton'/30193, l='MpServer', x=-617.50, y=14.00, z=206.50], afu['Skeleton'/30709, l='MpServer', x=-572.50, y=42.00, z=138.50], afu['Skeleton'/30710, l='MpServer', x=-574.50, y=42.00, z=138.50], agh['Zombie'/30711, l='MpServer', x=-573.38, y=42.00, z=145.13], agh['Zombie'/30456, l='MpServer', x=-615.50, y=17.00, z=201.50], agh['Zombie'/30712, l='MpServer', x=-574.50, y=42.00, z=136.50], aen['Creeper'/30457, l='MpServer', x=-613.50, y=17.00, z=207.50], abo['Bat'/30205, l='MpServer', x=-606.48, y=19.47, z=200.79], agh['Zombie'/30462, l='MpServer', x=-654.50, y=41.00, z=118.50]]
Retry entities: 0 total; []
Server brand: vanilla
Server type: Integrated singleplayer server
Stacktrace:
at cel.a(SourceFile:308)
at bss.b(SourceFile:2252)
at bss.a(SourceFile:323)
at net.minecraft.client.main.Main.main(SourceFile:120)

– System Details –
Details:
Minecraft Version: 1.8-pre3
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.8.0_11, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 397347648 bytes (378 MB) / 1471152128 bytes (1403 MB) up to 1908932608 bytes (1820 MB)
JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx2G
IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94
Launched Version: 1.8-pre3
LWJGL: 2.9.1
OpenGL: AMD Radeon HD 6700 Series GL version 4.2.11318 Compatibility Profile Context, ATI Technologies Inc.
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.

Using VBOs: No
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: [Lithos Core.zip]
Current Language: English (US)
Profiler Position: N/A (disabled)

Confirmed For 1.8 Pre Release 3 😛

Confirmed For 1.8pre3! 😞 For me this glitch happened when i created a new world and VBOs was on and Render Distance was 2 chunks for some reason.When i would change VBOs to Off and go anything above 2 chunks the glitch was shown.However when i was at 2 chunks the glitch didn't apear.To test this a generated a new world with VBOs=On and Render Distance 4.I tried every render distance(from 2 to 16 chunks for me) and the glitch did not apear.However when i turned VBOs=Off.Every render distance over 5 chunks with show the glitch.I did a 3rd test to prove this theory.I made a world with VBOs=On and Render Distance=8.With VBOs=On every Render Distance worked.When i turned VBOs off the glitch would be shown every render distance over 5 chunks(like in test 2).So it seems that when i turn off VBOs and my render distance is over 5 chunks the glitch apears.This might be because the VBOs doesn't work as wanted with AMD/ATI.This glitch should be a priority to fix as it is photosensive, or untill it is fixed there should be a way to warn people with photosensive epilapsy!

The same happens to me but my graphics card is like 2 months old and a very good one, this glitch has been happening for around 1 and a half for me but that is when i started playing on the snapshots so i dont know exactly when it started but my guess is when the new rendering system was added (Still happening in Pre release 3). It is all dependant on render distance for example when i load up any world and turn my render distance up one more that i spawned in with it does the bug, but if I put to higher (So it does the glitch) and then i restart minecraft i can then see further but not further then what i spawned in using

It says Fixed In Version: 14w34b and it still happens in 1.8pre3 😛

I just loaded snapshot 14w34d and I'm not experiencing the glitch anymore. There is considerable lag on world creation, when saving, and when switching but presumably this is because of the amount of chunks that are being generated.

I also find that if I Alt+Tab the game becomes unresponsive. Not sure if that's related but I'll have to do more testing.

@@unknown This ticket claimed to be "fixed" in 14w34b but was reopened.

The pre3 of 1.8 also does something similar with me, same graphics card actually. Use 32 chunks in the nether directly in front of your portal and watch minecraft go nuts.

The 1.8 release Version also has this. Why is this released when it Bugs on most AMD/ATI Cards ? I don't get this.

Fabian: Use a lower render distance, toggle the VBO option, and/or increase the memory limit (look at previous comments). One or some combination of those solutions fixes the problem in most cases. In mine, I can get to 32 chunks of render distance without any graphical glitches if I increase the memory limit to 8Gb and enable the VBO option.
By the way, having a large render distance can severely degrade performance.

I play with VBO on and 4 GB Ram and when i turn the Viewdistance to 32 Chunks the Bug is gone. But the memory usage is huge. I mean huge (2x-3x as in 1.7). And i don't think that a by default disabled VBO is the real solution for this (either it gets turned on by default on AMD/ATI or the real Bug gets fixed).

1.8
I have this bug with a R9 290 however when I have 32 chunks wanting to be loaded IF I turn VBOs on it fixes this issue also it only happens trying to load 14 renders or further

I have an amd and I have the same problems with the chunk rendering with 32 chunks (with the 1.8 version)

Screenshot of the bug

OpenGL: AMD Radeon HD 7570 GL version 4.2.12422 Compatibility Profile Context 13.152.0.0, ATI Technologies Inc.
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.

Release 1.8 have also this bug

Wellcome 1.8 however as expected the rendering issue still exists. I was chatting to another user and we both suddenly remembered a similar bug in a much earlier version of Minecraft. About 1.5 ish we think. The issue was to do with graphics not been cleared on exiting one game and either going back after a change in options and another game. The short term solution was to exit fully ensuring Java was closed and then reopen and all was OK. Someone fixed it then.

This led me to a bit of playing around. I have AMD Radeon HD 7900 dual graphics cards each with 3G on board and 16 G of RAM. In short I have the grunt that should be well sufficient.

I had the same problem at greater than 12 chunks. I then upgraded my java to 1.7.0_67 and got to 14 chunks. I then upgraded my drivers to the latest 14.100 version dated 2014-04-17 and got to 16 chunks. I then changed my JVM argument to bring my max mem to 8G (-Xmx8G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M) and it did not work.

I then set the chunks to 32 saved and exited fully from teh game and Java and then went back in and low and behold 32 chunks works fine. I have trashed it with all settings on max and got the mem running at just under 3 g and all is fine and dandy. the interesting part is that if I then exit a game and go to another one without closing down Java, then the next game will only work to 16 chunks. If I go out completely and close down Java and then come back in, guess what, the other game works fine on 32 chunks. If I change down the chunk numbers, everything remains OK but if I go up again the glitch appears. But then all I have to do is save the game with the errant chnuk figure, exit Minecraft and Java and reload and all is fine.

This leads me to suspect that there is actually an issue with java and that unless you close Java down, the loaded graphics do not clear or become unbalanced. So I have a workaround that allows me to play all my games at 32 chunks with my AMD Graphics card by ensuring that I only play with a vanilla Java load and my previous video settings irrespective of how high or low the chunk setting was on last save, will work fine.

I would like Kumasasa to take a closer look at this and not just leave it as and AMD graphics card problem as it appears that there is a factor to do with Java and the rendering.

Just to confirm what my spec is, extract from a forced crash report

Minecraft Version: 1.8
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.7.0_67, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 397236256 bytes (378 MB) / 1416335360 bytes (1350 MB) up to 8576565248 bytes (8179 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx8G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 12, tallocated: 94
Launched Version: 1.8
LWJGL: 2.9.1
OpenGL: AMD Radeon HD 7900 Series GL version 4.4.12874 Compatibility Profile Context 14.100.0.0, ATI Technologies Inc.
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.

From MC-70575 / @unknown:

OpenGL: ATI Mobility Radeon HD 4200 Series GL version 3.3.11672 Compatibility Profile Context, ATI Technologies Inc.

This issue still persists in the stable Minecraft 1.8 release.

On my system (with a AMD HD7950):

16 chunks render distance: http://i.imgur.com/oEfi1qj.png (works fine)
20 chunks: http://i.imgur.com/wEUYdx1.png (glitches start appearing in the distance)
25 chunks: http://i.imgur.com/U0SBtgl.png (glitches surround me view, constantly flickering different geometry when I move my view around)

This issue is still persistent in the stable Minecraft 1.8 release.

My video card: AMD R9 290 (latest driver version)
Video of issue: http://www.youtube.com/watch?v=f6jTyDDfguQ

I have the same problem (AMD HD Radeon 8800M) which plays games like skyrim at ultra settings with mods even at 60 frames. I dont know how minecraft cant handle it, but w/e. Also it only happens from 25-30 render distance. Any lower and it basically goes away.

crash report during blocks messing up. AMD R9 290 latest driver.

Same problem for AMD Radeon HD 7600M Series

Same problem Hd 6900 latest driver

Similarly, in the release version 1.8, video card AMD R9 270 2GB
The latest drivers for the video card.

As a side note, water and giant mushrooms in unaffected chunks have very strange visual glitches as well.

AMD R9 290X crossfire

This bug occurred when I had VBOs off and I increased my render distance. When I increased the distance it made tons of new chunks and some nearby cow models and the extending area started to experience massive glitches.

Oh and I have this information about my video card found by AMD Overdrive

Name AMD Radeon(TM) HD 7800 Series
Description AMD Radeon(TM) HD 7800 Series
Vendor ATI Technologies Inc.
Core Frequency 450.00 MHz
Memory Capacity 2048 MB
Memory Frequency 1200.00 MHz
Memory Bit Width 256 Bit
Display Mode 1440 X 900 : 32 (60Hz)

Only happens for me when chunk rendering is pushed past 12 regardless of memory settings or VBO on or off. Does not happen for me long as chuck distance is <= 12. Happens in both Single, and multiplayer as of 1.8 never had issues with this kind of graphics garbage from 1.7.x or older. Also -d64 option did nothing... nor did using uselessly 2gig of xmx/xms ram settings. The visual glitches for me are oddly not ALL around. its only on the leading edge of unloaded chunks to the east and west, and moving to them doesnt move it back either. Also moving north and south is fine and loads properly... Btw everyone testing on a 'server' should increase the server render distance, only a 'local' running game can render 12+ typically.

this happened to me in 1.8.

maybe it helps 😉

https://www.youtube.com/watch?v=lh8D4dRDkaw&feature=youtu.be

The VideoFile is too big for Jira (11,5MB or 10,03MB (zipped)) so i couldn't upload it here.

GPU: ATI R9 270
CPU: AMD Phenom II 955BE
Memory: 8GB DDR3 (4GB for Minecraft)

Now that my computer is fixed, I can finally confirm this in 1.8. For me, I get a little bit when at 16, but then it takes up half of the area that I'm in at 17 (3/4 of it at 18, all at 19).

OpenGL: ATI Mobility Radeon HD 5650 GL version 4.0.10179 Compatibility Profile Context, ATI Technologies Inc.

I had this when I allocated 4Gb to JVM and had render distance set to 32 chunks.
(same as https://bugs.mojang.com/secure/attachment/80700/2014-08-25_07.44.47.gif )

I also have an AMD Radeon card.

IIRC it disappeared when I lowered JVM memory to around 2,5Gb.

I used to have this bug, but got it fixed today.
ill share my findings.

first things i had but the bug was still there
latest videocard drivers
jvm arguments: -Xmx4G
java version: 1.8.0_05

the bug was fixxed after the following changes:
java version: 1.8.0_20
jvm arguments: -d64 -Xmx4G

so far i have been able to switch rendering distance ingame without the need for restart or vbo being on or off.
i used to have this problem above 20ish chunks

I have this issue if I raise my render distance above 7. I thought it was because I was using 32-bit java on my 64-bit computer, but after getting the right version and upping my memory, the issue happens once I raise the render above 8.

I have this issue if I raise my render distance above 7. I thought it was because I was using 32-bit java on my 64-bit computer, but after getting the right version and upping my memory, the issue happens once I raise the render above 8.

Same issue here;
Java: Version 7 Update 67
AMD Driver: 14.4

OpenGL: AMD Radeon HD 7800 Series GL version 4.4.12874 Compatibility Profile Context 14.100.0.0, ATI Technologies Inc.

Might be worth noting that mobs no longer move when this occurs and the game will crash when you exit the world.

Hold on a second, the reporter of this bug doesn't even have an AMD? If you look at @unknown's posts, he says he has an nVidia. This could mean that this is caused by a feature all AMD's have, but some nVidia's too. However, he also said he hasn't experienced this lately, meaning that it can be toggled or that the graphics card can do it another way. See https://bugs.mojang.com/browse/MC-62958?focusedCommentId=187961&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-187961

Adding -d64 to the JVM arguments fixes this on 32 render distance. Without it occurred when it was over 12.

Hello, I seen the same thing. A temp fix try turning on "VBO" hope this helps.

my video recording this: https://www.youtube.com/watch?v=hapenSnHa_k

Squawkers, where do you add that part in the JVM arguments?

I have also experienced this glitch (and i do have an AMD) but i have found that it turns off if you go to 9 chunk render or lower. although if you go above 12 chunk render it will expand to everything you can see even the chunk you are in.

more visual glitching when chunk loading is set too high

Java version (64bit) 1.8.0_20 and jvm arguments -d64 -Xmx4G solved it for me.

i have the same problem in 1.8 as well

I have this graphical error above render distance 17, attached crash report.

Added the JVM arguments and can still confirm the visual glitching at 32 chunks.

In fact, a bit worse as well. With said arguments added, I get the glitching at 11 chunks instead of 16.

-d64 fixed it for me. Is that the root of the problem?

I'm not entirely sure. This should probably be added into the description, though:

Workaround for some players

Adding "-d64" to the JVM arguments for Minecraft may fix the issue.

-d64 -Xmx4G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M

Please note that this may not work 100% of the time!

I have it at distances greater than ~22 chunks. Turning VBOs on completely fixes the issue for me. High memory usage seems to aggravate the problem, as I experienced the glitch at 16 chunks after quickly changing from 2 chunks (memory usage spiked and stayed at ~95%). Graphics:

AMD Radeon HD 6700 Series GL version 4.2.11931 Compatibility Profile Context, ATI Technologies Inc.

-Xmx8G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M Seems to completely fix the bug and cause the game to be playable at over 32. I looked at the code and it seems to be set from min 128MB to max 8GB.
Maybe the problem is because of lack of freedom allocating rams. Maybe it works idk 🙂

Can still confirm the visual glitching, even at 8GB allowed!

I think the -64 thing fixed it for me, thanks 🙂

My problems are gone with AMD driver update to Catalyst version 14.9 (AMD Radeon R9 280)
With older versions (13.251 & 14.3) I had problems with render distance greater 12, now it's all fine even with distance 32

This is my crash. thanks for helping

I've had this glitch forever. it makes everything way harder than usual. But this fixed it!!! Well... not 100%, when I turn my render distance to around 15 it still does it... but now I can turn it to 10 and that makes a big difference. Thank you so much!!!

Attaching my crash report.

Images of the bug (AMD Radeon Graphics card) render distance 11, 1.8.1-pre3

This is happening to me on my AMD Radeon 6480

@Michael Mapstone
Your solution worked perfectly and I can go up to 32 render distance without any bugs.
For anyone not bothered to find the comment, his solution was to put minecraft up to 32 render distance, then completely close minecraft and relaunch it.

Got it with AMD Radeon HD 6700 Series.

Got it on AMD Radeon HD 6670, turning on VBOs disappeared the bug

Chunk Loading bug on 16 Render Distance (Happens from 11-16 Render Distance for me 1.8)

I have just turned VBOs on and to my surprise, it fixed the bug. (I tried on all render distances.)

It also greatly improved FPS and chunk loading.

this still happens 1.8,1 pre 3 not fixed

In 1.8.1 pre3 it's even worse; before it happened on Render Distance 19+, now 13+.

1.8.1 pre 4 doesn't fix the issue.

Hey moderators change the Fixed Version to None it still happens.

@@unknown: Don't tell us what to do.

1. If a ticket got fixed but repopened the fixed version remains there to track the history of this ticket.

2. 14w34a is an archived fixed version and cannot be removed

Didn't think my issue was so similar to this but apparently it is. MC-74155
Here's a video from that bug: http://youtu.be/GSsfBL3nbqI

This bug as bin fix by amd on the latest amd drivers beta "[407431]: Minecraft sometimes produces corruption when changing video settings in windowed mode." (14.11.2 beta)

Also happens on ATI Radeon HD 4800

Can anyone confirm that this is fixed after updating to the latest beta drivers (14.11.2)?

NOTE: If Minecraft shows a "Pixel Format not accelerated" crash after updating to these drivers, then you're experiencing MC-71565 and will have to downgrade.

I tested and no problem for me with the latest beta drivers (14.11.2)

Resolved, updated description with link to AMD Beta drivers

@Kumasasa - Only one person confirmed that the new beta drivers fixed it. Shouldn't we at least wait for a few more confirmations (and the final drivers) before marking this as Resolved?

The mods probably did check themselves to see if the drivers resolved the issue for them as well, though they may not have explicitly stated that. I know I had it, and updating to the beta drivers resolved the issue for me. The drivers being in beta is beside the point in any case, as the fact that one of the fixes listed by AMD in their updated drivers was to solve this issue indicates that the issue was primarily on their end. This takes it from a bug report for Minecraft to a bug report for AMD's graphics drivers. Hence why this ticket and similar issues are marked as "invalid".

@@unknown: Yes, I did test that and well said about the "invalid" resolution.

The beta drivers don't seem to support the Mobility Radeon 4200 that I'm running, and adding -d64 didn't fix it. Am I out of luck? At it isn't completely game-breaking...

@@unknown: Latest "legacy" driver is Catalyst 13.9: http://support.amd.com/en-us/download/desktop/legacy?product=legacy2&os=Windows%207%20-%2064

I think the title and description need to be updated to reflect on current issues.

The title should read as such: Massive Visual Glitching with VBOs off and Chunk distance over a level the graphics card cannot handle (Caused by outdated AMD drivers)

As with the description, it basically looks like a huge mass of confusion between the moderator notes, so I managed to simplify it with basically just solutions and workarounds.

The description should read as such:

Solutions

Update to AMD Catalyst 14.11.2 Beta (Not Recommended, as it is a beta driver)
Update to AMD Catalyst Omega (14.12) (Recommended)

Both drivers can be downloaded here.

"Pixel format not accelerated"

If you're receiving this crash after updating to the drivers listed above, then you're experiencing MC-71565, and will have to downgrade to the old drivers. Follow the instructions there on how to do so.

Workarounds

There are multiple workarounds that can fix this issue.

You can do any of the following listed below. These might've fixed the issue for some, but not all, people who have this bug.

Recommended:
Turn VBOs ON (Options -> Video Settings -> Use VBOs: ON)
Turn down render distance to an acceptable setting (where it doesn't produce the glitching)

Not Recommended:
Adding -d64 to the JVM arguments for Minecraft
(Example: -d64 -Xmx4G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M)
Assigning more memory (One user has said that they still experience it at about 3.5 GB)

So wait
What you're saying is
"Upgrade to these drivers to fix. If your game crashes when you do that, just downgrade."

No.

What I'm saying is "upgrade to these drivers to fix. If your game crashes, then you're experincing MC-71565 and will have to downgrade in order to play the game again".

There clearly are workarounds if you didn't notice them.

thanks man! this helped alot. i will be sure to go to this page if i find another glitch.

Happened to me again in snapshot 15w35b. What I did was I just paused the game for 10 mins., not changing the setting, then when I continued the game it happened. Happens also when opening a chest, pixels appear in the GUI of the chest. Also, when you place custom heads in the world then the bug happened, it doesn't show up the second layer of the skin (hat).

I've been having this glitch a lot while opening/creating multiple worlds without restarting the game (snapshot 15w37a) in between. If I save while having this state, the world will have it permanently (tried creating 2 worlds, restarting and opening the newer one). The first world I play (unless it already had that state saved) in that snapshot seems to be fine and I also do not have this bug in 1.8.8 at all.

It should get a proper fix, because the driver version I currently have is already required by different other games that I'd prefer to keep working fine. Also this is actually a compatibility issue with AMD graphics cards that needs to be either noted in the System Requirements or get fixed, when releasing pay2play games, as this is game breaking unless you fix it yourself.
Side note: AMD graphics card suck for gaming, will buy nvidia card for next PC.

EDIT: I just read the "Chunk distance over a level the graphics card cannot handle" part...I have 120fps locked stable with my graphics card. I don't think it has any trouble with the render distance at all.

Turn VBOs ON (Options -> Video Settings -> Use VBOs: ON)
Now my game doesn't respond... I assume it means = get the driver?

not necessarily. 5750 13.12 drivers zero problems only happens sometimes when I change DD and a restart of the client fixes it. imho the issue is something dealing with what is being changed for draw dist. possibly imho fixed buffer size being resized and its not being 'cleared' properly. (since buffers are not GC'd at all) eg. the long time growbuffer error a good indication (but I dont know if that still existing either but I believe it is)

That's the same issue I've had

I have been having Minecraft max out my memory and stutter really bad to where it is unplayable. I have to move my max chuck distance completely down to even try to play the game.

Affects 15w44b with VBO's off.

I'm playing on Minecraft 15w47c, and I have that same glitch where the chunks distort. I also manage to fix it by turning VBO's on.

OOOOHHHHH!!!! so thats why its fixed now.... Thanks!

Never had this issue in 1.8 but it happened about three quarters of the time in 16w04a. I'm guessing some of the 1.9 changes make it more likely to trigger.

Since enabling VBOs seems to fix the problem reliably, it'd be nice if Minecraft could do that automatically if it detects the broken driver version. Throwing up your hands and saying "It's AMD's fault! Update your drivers!" seems like a copout when Mojang could work around it so easily.

It's a very bad idea for applications to implement hacky work arounds for well known and already fixed problems of any OS, driver or supporting software. This would have side effects and be be a never ending story eating up too many resources. Keep in mind that Minecraft still runs on > 10 yr old hardware with nearly 20 yr old OS (Yes, the 97 in Windows 97 is the release year).
Except from all that, the concept of a platform independant software would be foiled.

To name only a few of this issues:

• MC-297 "Pixel Format Not Accelerated" / "Could not init GLX" / Bad video card drivers

• MC-6665 Mac Computer Crash on Expanding Minecraft Window

• MC-32606 JVM Crash in ig75icd64.dll (Broken Intel graphics card driver)

• MC-90269 JVM crashes in ig8icd64.dll (Broken Intel graphics card driver for "Intel HD Graphics 5500")

• MC-94900 JVM Crash in ig9icd64.dll (Broken Intel graphics card driver)

• MC-14051 JVM crashes in ig4dev32.dll / ig4dev64.dll (Broken Intel graphics driver for the "Mobile Intel 965 Express" graphics card)

• MC-34749 Hopper: java.lang.IllegalStateException: failed to create a child event loop - Caused by AntiVirus / Firewall software

You may ask yourself some questions:

• Aren't the manufacturers of drivers responsible to auto alert users when massive issues are fixed ?

• Why are broken drivers still delivered by Windows update ?

• Why are Laptops still manufactured with crappy and broken graphics chipsets ?

• Why are users installing Windows 10 on hardware not capable of running it, because too weak, no drivers available ?

Don't blame others for things you are responsoble for: It's up to you to provide a working environment.

End of discussion here, please follow up at http://reddit.com/r/mojira

hey genius in the crash reports it says "manually caused debug crash"
that's a intentional crash...
:
F3 + C ( Hold 10 Seconds)
or
Fn + F3 + C[Function] (Hold 10 Seconds

@Donovan Daniels That is because this is not a crashing bug, it is a visual glitching bug. Seeing the visual effects of the bug (examples in attached screenshots) does not make the game crash. The crash reports there were forcibly triggered so that the developers could have real debug data to work with. The reports contain a lot of data about the environment the game is running in (see System Details section), which could be useful when trying to fix the issue.

As it turns out, though, the issue was with AMD's drivers, not the game, so if you're experiencing this on a computer with an AMD graphics chip, update your drivers.

This has been duplicated by another report (in 1.9.1) but the latest issue that this ticket mentions (that this bug is present in) is 1.8.1

because this is not an issue from minecraft, it's your hardware, this ticket won't be updated

I followed the first recommended "Workaround", turning on VBOs, and it's working so far! Thanks a lot!!