Michael Mapstone
Assigned
Reported
Comments
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
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?????????????
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.
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.
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.
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.