Unfortunately unable to tag any versions below 1.13.
The Java executable included with the Minecraft installation apparently does not work for some systems. A rather odd situation.
Minecraft versions 1.8.9 and below seem to be completely unaffected under this environment, however when using any version 1.9+ the issue occurs. The FPS will go no higher than 3 frames as I've experienced, no matter what the settings have been changed to. The only workaround I have found is to set the Java executable to the one included in a Java installation (for Windows 64-bit, usually located in C:\Program Files\Java\jre[version]\bin) using the launcher profile advanced options.
Attachments
Comments 8
This is still an issue. I've also tried for 1.13.1 and I get the same outcomes. Something I failed to mention is that even reinstalling the Windows OS does not solve it.
We do not have enough information to find the cause of this issue.
Please force a crash by pressing F3 + C for 10 seconds while in-game and attach the crash report file ([minecraft/crash-reports/crash-<DATE>-client.txt|http://hopper.minecraft.net/help/guides/finding-minecraft-data-folder]
) here.
This issue may be temporarily resolved as Awaiting Response. Once the crash report is attached, the issue will be reopened automatically.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Your computer does not match the minimum system requirements needed to play Minecraft.
Specifically, you need at least OpenGL 4.4. You only have OpenGL 4.3.
I'd recommend that you update your graphics card driver(s). If you have trouble with that, or if it doesn't solve your issue, please visit the #minecrafthelp IRC chat for help.
For clarification, does this explain why it decides to magically work when I use the executable in the Java folder?
I'm not too sure. Maybe the executable from the Java folder includes a newer version of OpenGL, but I don't know for sure.
Could you trigger a crash report when using the executable in the Java folder? That way we can know for sure.
Is this still an issue for you, or did it get fixed in the meantime?