Brian Whelan

Default, but I think I've fixed it - I had downgraded my Video Card drivers a few days ago to test something - Updated them to the latest version and the problem is gone.

I know it's been a while, and the problem has pretty much been solved ^^ However oddly, (And it only happens occasionally) Looking at/Jumping into water often crashes my Intel HD 4000 drivers, forcing me to attempt to close Minecraft and occasionally making my screen go black until the drivers restart - Not that much of an annoyance, but it only started happening when Intel released the fix.

Just got the same crash again after removing the Intel regedit. I'll try updating my drivers and see if it fixes

The console just shows the same old "Shutting Down" - I've kept the allocation of ram at the default 1gb, because Java's Garbage collection isn't very good at handling large amounts and can cause more lag - It's not an issue with ram because I get a Windows balloon in the bottom right of my screen telling me that my Intel HD 4000 drivers have crashed - It hasn't happened since I removed the changes to the registry, but I haven't played enough to confirm it's gone.

Kind Regards,

Brian

Thanks Meri,

I wasn't aware I had to remove the Intel fix too - I'll remove those entries from my registry now and see if that fixes it.

Regards,

Brian

I was just playing a game of Survival Games when suddenly my Intel HD Graphics Drivers stopped responding, my whole screen froze and my Minecraft went black. I've never seen anything like this before so I guess it has something to do with Intel's fix conflicting with the launcher's fix - Any ideas how to fix this? It's happened 3 times in the course of 5 minutes

Also I agree with Meri that 1.6 lags more than 1.5.2, not too big a deal

I agree, I find that when I went back to 1.5.2, the framerate seems to be worse than I remembered, although the counter seemed to show about 70fps, sometimes fluctuating higher, so I guess our memories can be optimistic about things. I've noticed now in 1.6 I seem to get about 50fps in places, sometimes higher in fairly flat areas on max settings, so I'm happy with performance now as it's almost on par with what I actually got in 1.5.2, so as far as I'm concerned, I can go back to playing Minecraft properly 🙂

Thanks @Grum and Intel, Really glad that the temporary fix supplied by Intel boosted my FPS, the game is now playable again 🙂 Looking forward to Intel's driver patch so I can get back up to 70fps, but for now, Thanks! I really appreciate all your effort 🙂

Edit: Just tried it now - Getting 45fps 😃

Before I try out the Registry file, I just want to say that I really appreciate both Intel and Mojang for getting this fix out. I understand that you guys are under a lot of pressure from hundreds of different groups, and I really appreciate that you put your time aside to try to fix our problem. Thanks <3

I'm just going to reboot and try testing Minecraft, then I'll post my results here.

Ok, Rebooted and still had the same lag, so I ran the regedit again and just relaunched Minecraft. I'm getting about 30fps maxed out on an Intel HD 4000, so while it improved over before, I'm still lagging more than I did in 1.5.2 - I realise this is a temporary fix and I'm really glad it was finally released, but hopefully the actual driver released in the future can fix all of the lag and bring us back to about +70fps. Thanks!

Either way, With advanced OpenGL on and off, looking at plain open terrain, then at a huge mountain will cause a drop in FPS, because the game has to render all the new blocks that are visible to you. This happens to everyone

I don't get any radical FPS drops in 1.5.2, only slight stuttering - nothing like 1.6.2. It's hard to tell if I lag with Horses since I barely push 10fps on 1.6.2, but they don't cause me to go any lower - Also, Looking away into plain open terrain then back to mountains or some other type of terrain will cause lag, because the game has to render all these new blocks very quickly.

I'm not sure if the launcher is set to detect 2.4, so you might have to rename all the files to 2.9.0. We can't hack the launcher's code because it's been compiled and obfusicated, sadly. It could still be a problem with LWJGL and the new launcher, but the Intel drivers do cause most if not all of the lag. I'll try downgrading my LWJGL and seeing if I can get it to run and then I'll post back here, but I don't think it will solve the lag.

I'm getting kind've sick of Mojang for not helping us - Most Minecraft players use Intel cards, and when we get into trouble they pretty much blank us out and say it's not their fault. I haven't played Minecraft since 1.6.1 came out because of the lag, and I'm not going to play it until it's fixed (Besides testing fixes 😛)

Also, when testing 1.5.2 with the new LWJGL I noticed that, although my FPS said it was over 70fps, that the game wasn't as smooth as it was before - not sure if this is LWJGL or just a side-effect of 1.6.2's lag 😛

The problem is, We can't try 1.6.2 with LWJGL 2.4, because the new launcher automatically updates to 2.9.0 again. We've isolated the fact that it's a problem with Intel's drivers and the new launcher, and that it is not LWJGL. Intel are currently working on a fix for the drivers - You can check it out and post here:

http://communities.intel.com/thread/42832?start=15&tstart=0

There are a few guides to improving FPS with Intel + Dedicated cards above - You should check them out and see if it helps 🙂 1.6.2 downloads the latest LWJGL automagically, but I did try 2.9.0 on 1.5.2 and did not suffer a drop in performance - It's not LWJGL, but Intel's drivers not recognising the second Java process as a game, therefore not providing it with hardware acceleration.

Are you using an Intel card? Earlier in the comments I tested using new and old versions on both 1.5.2 and 1.6.1 with no improve in framerate, and we've already isolated the problem as coming from the new launcher and Intel's drivers.

We tried Intel's forums, and Intel told us to get Mojang to go it, while Mojang told us it's not their problem. I'm going to try asking on the Intel forums but I expect the same result as before.

This issue is for people with Intel HD 4000 graphics cards. You should try looking at some of the comments for fixes when the Integrated card is used instead of the dedicated card, However I do believe you have a different issue to us, as we are not experiencing lag spikes but rather lag all of the time.

Again, No luck running from command line, However running Minecraft from command line in MCP doesn't cause this lag. They do however use Python to launch the game, so I might have a look at the script they use.

@André Normally "Something's taking too long!" errors don't actually affect the game in any way, but it does seem to have something to do with the renderer. I didn't notice those errors, but I get them too. Thanks for pointing them out!

Using MCP (A modding tool that decompiles/recompiles the Minecraft source), which has a "StartClient.bat" file (Launches the game from command line without launcher) I don't get any lag, and the game runs just as if it was running on the old launcher. However this does not allow you to join Multiplayer games, only Singleplayer as it uses Offline mode - Using Brian Richard's link you can copy the session from your launcher to play Multiplayer, However for some reason that .bat file didn't solve my lag. I'll try it again with D3D No Hardware Check and see if it works.

Also under Profiles you can stop the launcher from closing.

@Dennis The reason the game starts out at a high frame rate is because the world has not yet rendered - within seconds after connecting to a server I drop to below 10fps - I can assure you my issue is what this bug is primarily about, otherwise I would not have contributed to it.

I'm not running Optifine, However trying it in a separate profile didn't help the cause at all. Switching VSync off and on rapidly, along with cycling through render distances temporarily improves the lag, as the world is re-rendered easing the load on the non-hardware accelerated graphics. I've been running the game on max on this laptop since I got it keeping well over 60fps, Which is why I believe it to be a problem with Intel's drivers that was only discovered when Mojang changed the launcher.

Thanks for your time however - I appreciate the help 🙂