Minecraft crashing loading the game
Myuui opened this issue · 8 comments
Nothing that relies on OpenGL API will work on Vulkan. If you want support, ask the maintainers of that mod to add support for the Vulkan rendering API.
Same goes with everything rendering related, Vulkan is new so support and work is needed and it will be gradual, but Vulkan is the future.
Also just make sure your GPU supports the lastest version of Vulkan, update your drivers.
After looking at the log, the GPU failed to intialise when loading the mod. VulkanMod only needs a minimum of Vulkan 1.1, and the GPU used does support Vulkan 1.3, So currently suspect an outdated Intel GPU Driver, as the version seems to be a 2021 driver.
Am not an expert with this so apologies if the above isn't helpful.
i've updated my graphics card driver to 27.20.100.9664 i hope it works
Success!
But the performance is worse than Sodium sadly
1.19.4 Singleplayer bad screenshot
But the performance is worse than Sodium sadly
Make sure to wait until shader compilation finishes if your cores are at 100%
Other thing is, do not test just raw fps, test while moving and while having things that actually affect performance, like mobs, trees, chunk rendering, etc.
Mentioned this in another issue, but imo is strongly recommended to use LazyDFU, as it is used to make developing with this mod easier, and least imo VulkanMod works best with it.
it dosen remove all of the CPu and Chunk ReBuild lag, but completely elimiates the CPU from being maxed out at 100% when loading the game.
AFAIk shaders are not the issue as most of them (30+) are compiled when the Red Splash Screen appears and take less than a second using ShaderC to compile them
Some specific Chunk/Entity rendering shaders are also compiled at certain events in game, but only about 50+ shaders are used in game, and they usually take about 50ms or less each, and are always reused once created so are never recompiled.
AFAIK, shader Compilation/Stuttering issues are usually sudden lag spike stalls (i.e. Elden Ring Bugs IIRC), and not consistent, constant lag like this, which points to a different bottleneck elsewhere.
