Well that's a good theory, but as I said in the bug report this issue was present in 3rd party launchers that used a separate process way before LWJGL was updated to 2.9.0. If the fault really is LWJGL, it's been there for a long time. And unfortunately, there are millions of us without a "real videocard" that got 90 FPS before this issue.
I was messing around with those variables and flags a few days ago in an effort to get hardware acceleration working. From what I've read -Dsun.java2d.d3d=true and similar flags only affect 2D rendering, i.e. text. that why they're part of Java2D. Secondly, Minecraft doesnt not use Direct3D, it uses OpenGL, so flags like J2D_D3D_NO_HWCHECK=true and -Dsun.java2d.d3d=true should be -Dsun.java2d.opengl=true and J2D_OPENGL_NO_HWCHECK=true or something like that, I'm not sure of the exact syntax. Regardless, they only affect 2D rendering anyway. If anyone knows the flags for a 3D rendering environment, let me know.
Cheers I give my sincerest thanks to you Rae and everyone at Intel who worked on this problem. Looks like that finally did the trick. Frame rates are right back to what they should be! I and many other people will be very glad they can play Minecraft again. Goes to show what talking to the right people will do for a problem. Thanks Aaron Welles for bringing Intel's attention to this issue if that was you. Time to go tell the MC community!
P.S. would you care to explain what exactly the issue was that the reg file modified? I am pretty curious after all this discussion.
Brian, keep in mind that if you're like me, you've been messing around with settings for so long trying to get the game playable that the settings are no longer optimal. I had to turn of Advanced OGL, smooth lighting and V-sync and even then I still thought it was a bit slower than I remembered. But, I opened the 1.5.2 launcher right next to it to test and framerates were the same. I guess our memories tend to be optimistic about the past sometimes.
Spencer H.
MCL-767
Yes it is. As far as I can tell from reading the complaints on the forums and some other testing, it affects all Intel HD 2000-4000 video cards.
Please vote for this issue so it gets fixed.
Well that's a good theory, but as I said in the bug report this issue was present in 3rd party launchers that used a separate process way before LWJGL was updated to 2.9.0. If the fault really is LWJGL, it's been there for a long time. And unfortunately, there are millions of us without a "real videocard" that got 90 FPS before this issue.
I was messing around with those variables and flags a few days ago in an effort to get hardware acceleration working. From what I've read -Dsun.java2d.d3d=true and similar flags only affect 2D rendering, i.e. text. that why they're part of Java2D. Secondly, Minecraft doesnt not use Direct3D, it uses OpenGL, so flags like J2D_D3D_NO_HWCHECK=true and -Dsun.java2d.d3d=true should be -Dsun.java2d.opengl=true and J2D_OPENGL_NO_HWCHECK=true or something like that, I'm not sure of the exact syntax. Regardless, they only affect 2D rendering anyway. If anyone knows the flags for a 3D rendering environment, let me know.
Cheers I give my sincerest thanks to you Rae and everyone at Intel who worked on this problem. Looks like that finally did the trick. Frame rates are right back to what they should be! I and many other people will be very glad they can play Minecraft again. Goes to show what talking to the right people will do for a problem. Thanks Aaron Welles for bringing Intel's attention to this issue if that was you. Time to go tell the MC community!
P.S. would you care to explain what exactly the issue was that the reg file modified? I am pretty curious after all this discussion.
Brian, keep in mind that if you're like me, you've been messing around with settings for so long trying to get the game playable that the settings are no longer optimal. I had to turn of Advanced OGL, smooth lighting and V-sync and even then I still thought it was a bit slower than I remembered. But, I opened the 1.5.2 launcher right next to it to test and framerates were the same. I guess our memories tend to be optimistic about the past sometimes.
So you reverted the previous change that caused the graphics corruption and just used the new launcher?