Jason Winzenried

@unknown's resource pack reduces my GPU usage to 67% of what it was before applying it.  Not noticed any downsides to it.  geforce 2060 super

this is indeed the same bug as "underground rain"  as seen at https://bugs.mojang.com/browse/MC-180090 and probably others

worlds from before 20w17a have their heightmaps messed up when loaded in 20w17a. Can see with f3: the S and M values (for WORLD_SURFACE and MOTION_BLOCKING) are just completely random values. A world newly created with the new snapshot does not show this issue for me.

this is the same bug as https://bugs.mojang.com/browse/MC-179858

worlds from before 20w17a have their heightmaps messed up when loaded in 20w17a.  Can see with f3 the S and M values (for WORLD_SURFACE and MOTION_BLOCKING) are just completely random values.  A world newly created with the new snapshot does not show this issue

please implement this.  After literally hours of forceupgrade, any newly visited (but already existing) chunk lags a lot to load.  It's nice to convert all the blockdata or whatever at one go, but it would be awesome to be able to do so with lighting as well.  It's just as slow visiting new chunks as before I ran forceupgrade

of course, I was far to broad in my usage of "you". Of course you can't do anything about it. I wish someone would though! So yeah I slacked off on checking (I've been keeping it up for a while, as you will notice from the post date + list of affected versions). 1.7.2 to 1.7.5 wasn't really a large enough change to prompt me to check again. I've done so now, and with the latest snapshot, and it is still there.

I do wish you would get your story straight between "Should your issue return please submit a new complete ticket with all available information." and "Please do not clone existing tickets"

could we get some consistency please?

"Should your issue return please submit a new complete ticket with all available information."

yes it's still an issue. How can you expect me to check this report every few months when none of you** can take a second to change two characters in the codebase and fix it? How much effort am I supposed to expend on this?

**I unfairly directed this ire towards the moderators. Sorry!

still present in 1.6.4 and 1.7pre

REPRODUCE:

1: load this world: http://www.mediafire.com/?8o5hj55pwjolwos
2: walk under the platform. Watch the shadow disappear. This only happens with platforms at level 15, 31, 47, 63, etc, for the reasons described in the initial report.

confirm from scratch
1: start a flat world.
2: Build a large 1 block thick platform at y level 31 (or 15 or 63)
3: exit.
4: Load world again. walk on the ground under the platform. Shadow from the platform disappears as the lighting is updated based on the heightmap (which does not see the platform)

deleterious effects, clear explanation, two character fix. six months old.

this bug tracker is useless

part of me wants to just wait and see if this gets fixed along with Dinnerbone's lighting changes. At the same time, as long as he is doing that, I'd love to be sure this actually gets addressed. This bug has been around since 1.8 beta at least.

lighting errors as a result of the heightmap ignoring y levels 31 and 63 (as it does for every level that's at the top of an ExtendedBlockStorage)