mojira.dev

BBLZ

Assigned

No issues.

Reported

MC-267747 Click and hover events don't work when viewing chat while F1 is enabled Fixed MC-239900 Upgrading custom world to 21w43a ignores min_y and height Fixed MC-239794 Generation with noise_caves enabled is noticably slower Invalid MC-238823 Culling seems to at times fail in 21w37a+ Confirmed MC-237855 Caves & aquifers openings visible, possibly ingoring terrain top_slide Awaiting Response MC-219278 Being inside of a block no longer shows the block texture Fixed MC-219014 Charged creeper layer makes clouds and entities invisible Fixed MC-218711 Invalid Invalid MC-218681 Lag when changing Graphics mode Confirmed MC-218654 Nether particles appear under bedrock Invalid MC-218633 Smooth lighting has brighter outlines Fixed MC-218606 Lag spike when changing smooth lighting option Confirmed MC-218603 Screen turns dark grey when switching dimension Fixed MC-218596 Debug pie is blacked out Fixed MC-218554 Incorrect 4080 world import error message / no dimension validation Won't Fix MC-218548 Terrain doesn't render if player is above world height in 32 tall world Fixed MC-217802 Some blocks generate at wrong Y height in a superflat world Fixed MC-217509 Inefficient generation of aquifers, noise caves and ore veins Fixed MC-215669 Incorrect map on worlds with small height Confirmed MC-215667 Void effects incorrectly given under bedrock if min_y isn't 0 Awaiting Response

Comments

Haven't checked last snapshot but in 21w44a this appears to have been fixed!! 

[media]

High similarity with MC-166508, this is a duplicate!

This is not!

(@Dhranios)

Fixed, game internals use biome name instead of whole biome list in code now

The lagspikes are severely increased in a world with extended world height: Try this 4080 block tall custom world in 21w38a 

[media]

I just noticed there are affected versions attached that don't even support datapacks increasing world height. Isnt this bug only noticeable in worlds with increased height?

There seems to be a switch from low to higher fps at a certain number of blocks vertically away from max y, at at 32 this is 2048 blocks.

Edit: oh the chunks unload

In 21w14a mojang added the "min_surface_height" tag which is for defining the starting height of the surface builder, this tag also configures the minimum surface builder height of Nether Biomes. This change adds a point of inconsistency with this bug: Being able to define minimum surface level height but not maximum surface level height.

 

Yes, what I said makes no sense. It's just an excuse to create another reason why this bug should be fixed 

Without stronghold the dimension is invalid, and will indeed "break" the JSON but this is WAI iirc

Note: FPS can also decrease depending on how many chunks are loaded. The longer you look at something the more chunks could get loaded, the lower your fps might become, after how many seconds should the measurements be taken? The balancing of cpu resources might have also changed a lot last snapshot, amount of chunks loaded (letter C) should also be reported.

I'd like to further maintain this issue since you are unable to further provide affected versions. Would you be okay with me taking ownership of this issue? If you say yes I'll request ownership of this issue in the Mojira Discord. Thanks!

I can reproduce this issue in 21w10a. Did you try updating gpu driver by the way? There is a chance your PC will meet requirements.

I made a mistake, there are particles in both 08b and 10a, when I was testing I had particles turned off in 10a 🙂
This issue is invalid

Can confirm, they dont show at all for me
 

@moesh

Hi! I've tested a little further, and terrain does render when looking down, could you retest? Try looking mostly horizontal. Here is a video: https://youtu.be/gqpWL0uRoYk 

I've done a code analysis for one of my issues (MC-217802) using the mojang obfusication maps:

//net.minecraft.world.level.levelgen.flat.FlatLevelGeneratorSettings

public int getMinBuildHeight() {
  return 0;
}
    
public int getHeight() {
  return 256;
}

This hardcoding of getMinBuildHeight() and getHeight() results in this bug

With surface level do you mean ± 63, where you can see the open sky?

Hi @unknown, thanks for making that clear, I've edited the issue a bit(before seeing your message), is it clear to you there still is an issue in your fix? As said in the edited issue, the "noise" min_y + height has a limit of 2031, which is 1 off, if I'm correct this 2031 should be 2032 just like the other "type" min_y + height. 

This has not been fully fixed! This has only been fixed for the "type" and not for "noise", even worse, now it's (noise) min_y + height < 2031 which should be min_y + height ≤ 2032.

 

[media]

Is indeed "fixed" for "type", max became 2032 for both positive and negative.