I see other "resolved" issues similar to this, except that it is not resolved. The bug is an issue with the 1.9 version of Minecraft because this didn't exist with previous versions. When starting a game, the screen/graphics become fuzzy, distorted, and blocks look clear with patches of graphics flashing here and there. Definitely not playable. When enabling VBO, it does fix the graphics issue, but the game lags so bad that it isn't playable. Previous versions worked perfectly fine on the computer without having VBO enabled. Please fix.
I do not have a log at this time, but it is the same issue in MC-98326 report, which was marked as resolved when it really isn't.
Related issues
Attachments
Comments
migrated
migrated
follow the steps provided at MC-90269 to fix your issue, because those broken/outdated intel drivers don't go well with 1.9
migrated
I tried uninstalling and reinstalling the driver already through Windows Update, which looked like it got the correct drivers for the graphics, but I will try and manually install the driver from Intel's website and see if that fixes the issue.
migrated
So, after trial and test with different drivers and settings, I found the solution! I manually installed the Intel Graphics driver 20.19.15.4300 (15.40 / Jan 28,2016) from their downloads site. After I installed the driver, I launched minecraft 1.9 and it worked at first. However, after launching the game again, java crashed and kept on crashing anytime I tried to launch minecraft. I restarted the computer and still the crashing happened. I noticed that the screen flashed after I restarted, and saw that windows updated to graphics driver version 20.19.15.4331. So I uninstalled that, turned off windows auto driver update, and re-installed the 20.19.15.4300 version. It worked again when I launched minecraft, but not any time after (just like before). I decided to play with some java settings and thats where I found the solution. Once I allocated at least 2G of RAM at startup for the game, it worked. I used the java arguments "-Xms2G -Xmx3G". This worked along with using the driver version 20.19.15.4300 and I did not have to use VBO mode.
migrated
I'm having this issue too, and I've update all drivers. I've tried all the 'tricks' people have suggested.