Minecraft Java finally got a graphics API selector in the latest snapshot, and yeah—this is a big deal because the game has been stuck on OpenGL for way too long. In this video I jump in with basically maxed settings and grab a baseline: around 250 FPS in a heavier scene with lava, lighting, and mobs. It’s “fine” on my 4080 + 7950X setup, but Minecraft performance has always been weirdly unreliable, and OpenGL has been a prime suspect for years. Then I flip the switch to Vulkan… and immediately run into the most bizarre behavior. The game actually runs Vulkan, but only when it decides to use my integrated graphics, which turns everything into a choppy mess. If I disable onboard graphics to force the 4080, Minecraft refuses to run Vulkan at all—even with “prefer Vulkan” selected, it just falls back to OpenGL. I tried the usual stuff: driver reinstalls, full system restart, and poking around Nvidia settings, but nothing fixed it. Even a newer snapshot that supposedly addressed Vulkan issues didn’t solve this specific problem, so for now the takeaway is simple: Vulkan is promising, but the current implementation is still rough and, in my case, basically unusable on the dGPU.