Vulkan java (left) vs Bedrock (right) 32 chunk render distance both



by Distinct-Pride7936

15 Comments

  1. I’m assuming you’re (or whoever is recording) capped at 60fps and using a laptop, considering the ryzen 3 and integrated graphics

  2. LOL Vulcan reminds me of playing bedrock on a Realm, elytra-crashing into invisible mountains.

  3. secretiveconfusion on

    This is a weird comparison, Vulkan is a graphics API and shouldn’t have much of an effect on chunk generation.

  4. This is… unhelpful.

    You gotta stand still for a moment and let everything load. We are aware Bedrock is much faster at chunkloading than Java. That was the primary goal of the rebuild.

    But Vulkan is a rendering engine. It shouldn’t have any major impact on chunk load times anyway. How does the FPS compare once everything is loaded out to the chunk limit?

  5. KingoKings365 on

    Bro is using integrated graphics in java and expecting us to think this is in good faith.

    Use your dedicated card in both and show performance overlays in BOTH before anyone can take you seriously

  6. Yeah uhm, that’s not relevant?
    Java is Java, no matter the rendering API, works different than Bedrock, that is C++

    And you’re using a iCPU, is not bad tho, but the performance should be the same in both cases, and we can’t see the fps… :3

    If you’re talking about chunk load and generation, that’s way way way different and has nothing to do with the rendering API, Java is so much demanding than Bedrock, not even remotely close, Bedrock can use all CPU Cores and Threads but Java is limited to Single thread performance for chunk generation.

    Anyways nice post!

  7. Anarchistcowboy420 on

    I used to play bedrock at 100 chunk render on my decades old gaming pc. It was quite the downgrade when I switched to Java for the mods.