Brian Whelan
- bmanrules
- bmanrules
- Europe/Stockholm
- Yes
- No
MC-12407OS: Windows 8
Java : 7u17
In 1.4.7 I would receive 60-80fps with a HD texture pack, however as of 1.5 I have dropped to 40-60fps on a standard pack and 30fps with a HD pack. I am also now unable to record footage of my mods. I tried 13w12~ along with 1.5.1 and while 13w12~ reduced lag slightly I was still unable to hold 30fps up constantly while recording. I also receive lag spikes that shoot up to 100fps then back down to low levels and up to around 50fps again. I believe this problem is to do with the improved lighting engine in 1.5
In 1.4.7 I would receive 60-80fps with a HD texture pack, however as of 1.5 I have dropped to 40-60fps on a standard pack and 30fps with a HD pack. I am also now unable to record footage of my mods. I tried 13w12~ along with 1.5.1 and while 13w12~ reduced lag slightly I was still unable to hold 30fps up constantly while recording. I also receive lag spikes that shoot up to 100fps then back down to low levels and up to around 50fps again. I believe this problem is to do with the improved lighting engine in 1.5
---- Minecraft Crash Report ----
// Oops.Time: 20/03/13 00:43
Description: Manually triggered debug crashjava.lang.Throwable
at net.minecraft.client.Minecraft.l(SourceFile:1162)
at net.minecraft.client.Minecraft.K(SourceFile:572)
at net.minecraft.client.Minecraft.run(SourceFile:524)
at java.lang.Thread.run(Unknown Source)A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------– Affected level –
Details:
Level name: MpServer
All players: 1 total; [bdw ['bmanrules'/1, l='MpServer', x=1999.54, y=57.62, z=-302.44] ]
Chunk stats: MultiplayerChunkCache: 441
Level seed: 0
Level generator: ID 01 - flat, ver 0. Features enabled: false
Level generator options:
Level spawn location: World: (1996,4,-298), Chunk: (at 12,0,6 in 124,-19; contains blocks 1984,0,-304 to 1999,255,-289), Region: (3,-1; contains chunks 96,-32 to 127,-1, blocks 1536,0,-512 to 2047,255,-1)
Level time: 3053 game time, 3053 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: 2 total; [rf ['Boat'/0, l='MpServer', x=2006.72, y=56.28, z=-308.06] , bdw ['bmanrules'/1, l='MpServer', x=1999.54, y=57.62, z=-302.44] ]
Retry entities: 0 total; []
Stacktrace:
at bdt.a(SourceFile:282)
at net.minecraft.client.Minecraft.b(SourceFile:1887)
at net.minecraft.client.Minecraft.run(SourceFile:533)
at java.lang.Thread.run(Unknown Source)– System Details –
Details:
Minecraft Version: 13w12~
Operating System: Windows 8 (amd64) version 6.2
Java Version: 1.7.0_17, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 425691768 bytes (405 MB) / 648740864 bytes (618 MB) up to 954466304 bytes (910 MB)
JVM Flags: 2 total; -Xms512m -Xmx1024m
AABB Pool Size: 9635 (539560 bytes; 0 MB) allocated, 2 (112 bytes; 0 MB) used
Suspicious classes: No suspicious classes found.
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
LWJGL: 2.4.2
OpenGL: Intel(R) HD Graphics 4000 GL version 4.0.0 - Build 9.17.10.2875, Intel
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Texture Pack: Default
Profiler Position: N/A (disabled)
Vec3 Pool Size: 47 (2632 bytes; 0 MB) allocated, 13 (728 bytes; 0 MB) used
Not a duplicate - that one refers only to HD packs, mine is overall lag
I get the same error - While in a vehicle if you quit and return to the game your player vibrates inside the Minecraft while in third person mode.
Do you have Touchscreen mode enabled in your settings?
I'm having the same problem, and it doesn't look like Mojang plan to fix it for 1.6.2 - Hopefully they release an automatic launcher update tomorrow.
Have you enabled development snapshots under "Edit Profile"?
That's because when Dinnerbone was notified of the error on Twitter he wasn't told it was Intel/On a laptop and assumed it was a Desktop that had switched from dedicated to integrated. Both Dinnerbone and Jeb have yet to see this error.
"Like, if the "culprit" is the process that has been "outsourced" now, why not "merging" it back as it was before ?
Is it really "needed" for the New Launcher to run like that ? (The said process.)"
This. It's pretty much confirmed that the source of the problem is the new launcher,and I can't be the only one finding having two windows open confusing and annoying, especially with the changed icons from grass to a crafting table.
I understand now from watching Dinnerbone's twitter that the seperate window is needed for the Plugin API, which, as a modder I have been waiting for for a long time. I understand that the extra launcher window is helpful for bug fixing but most of the time I just launch Minecraft using MCP and use the console to check for bugs, which, as it only opens one java process, is also lag free. My laptop only has an integrated GPU and so I'm pretty much stuck with not being able to play Minecraft for the next while, until either Intel or Mojang find a fix - I realise Mojang can't fix a problem with Intel's drivers, and as you said earlier, hopefully we can get Mojang to talk to Intel in regards to it's drivers.
@Grum/all It may not be a real graphics card, but it's certainly a large amount of Minecraft's player base, which means it should concern you. You said it was a problem with updating to LWJGL 2.9.0, Yet when I try to use a nightly build of 2.9.1 or even go back to 2.8.5 the launcher re-downloads 2.9.0 and uses it instead. I agree with Alex and Stephen above. If it was caused by LWJGL, it's been there for a long time and is more likely to be the fact that Minecraft is now run in a seperate process. I feel pretty let down by Mojang as they are aware of the problem yet don't seem to be bothered to solve it ("It's also not a real videocard").
@Meri Minecraft 1.6 ships with LWJGL 2.9.0, which is the latest release, but there is a nightly build of 2.9.1 on the LWJGL site. You shouldn't technically need to update it unless you want to use 2.9.1 though. MCP is currently broken because it looks for 2.9.1 while Minecraft uses 2.9.0
Just tried using 2.9.0 on 1.5.2 using the old launcher - FPS stayed the same as before, some slight dips from about 70ish to 50ish but mainly stayed around 70-80fps in Singleplayer. Still much better performance than the performance I receive with the new launcher (5-20fps).
The new launcher uses 2.9.0, so updating to 2.9.0 isn't going to fix anything, because nothing will have changed. The old launcher used LWJGL 2.4.2. On the new launcher, 1.5.2 lags as much as 1.6.2 does, with 2.9.0, while using 2.9.0 on the old launcher doesn't cause any lag. I'm not sure it is a problem with LWJGL, but more a problem with the launcher/intel's drivers as said earlier.
Same, Hopefully Intel fix this problem soon, as I haven't been able to play Minecraft since the new launcher released.
Unfortunately there is no current fix - unless you have a dedicated Graphics Card. We'll need to wait for Mojang or Intel.
It's happening to all of us right now, and there isn't much we can do about it until either Mojang change the launcher or Intel fix their drivers.
I can confirm new launcher update does not improve this problem in any way - Windows 8.1 (Blue) 64x with Intel HD 4000 and latest drivers.
This should work with any card - I'm going to try it out now on an Intel HD 4000. I'll post the results here. Thanks pwzty!
Should I need to reboot after setting the enviroment variable? It hasn't had an effect so I'll try rebooting now.
Sadly, No luck for me. Game started at 90fps in Multiplayer and dropped to below 10fps within a matter of seconds - Running Intel HD 4000 with Windows 8.1 Preview (The preview is confirmed not to cause any issues with Minecraft). Rebooted PC after setting variable,
Ran it while Minecraft wasn't running - Hardware Acceleration is working. I'll try that other enviromental variable now (It is an Enviromental variable right?
) - Thanks for all your help.
No luck - lag still persists. Thanks for all your help! I really appreciate it.
@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
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.
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!
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.
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.
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.
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.
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
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
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.
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
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!
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
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
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
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
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
Just got the same crash again after removing the Intel regedit. I'll try updating my drivers and see if it fixes
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.
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.