Freakin_Sweet
Assigned
Reported
MC-135244
Can set SpawnRadius gamerule to invalid values causing CTD
Fixed
MC-128755
FallingSand Entities lose their marbles at extreme world coordinates
Duplicate
MC-128479
Biome Blend Very Unoptimized
Invalid
MC-99562
Block crack textures not aligning with model
Awaiting Response
MC-98858
Redstone Wire not appearing on Redstone Block
Duplicate
MCL-3910
Launcher Loading Other Profiles
Incomplete
MC-83478
Black Screen & OpenGL Crash
Duplicate
MC-66159
Custom Generated World Can't Change Emerald's Statistics
Duplicate
Comments
What is the randomTickSpeed of your world? I can't replicate the bug on my end in a newly created world, unless I change the tickspeed.
At least for me, the blocks and technical parts seem to load fine, it only refuses to render some chunks. When I place down a block in one of the invisible chunks, the chunk instantly renders and has no issues. Pausing the game helps some, but its still atrocious.
This bug is STILL PRESENT in 19w14b! And for other options in addition to the resolution slider, for me.
Extremely annoying! Can confirm for 19w14b.
Just happened to me in a survival world in 18w50a... guess that's what I get for using snapshots.
Not sure how to close an issue by myself, BUT, it seems that this has been fixed in 1.13.1! The game no longer crashes with a high spawnradius as far as I can tell.
Definitely affects 1.13 official release.
I think you're right @unknown. I've been mucking about a lot lately in creative worlds, teleporting all about, killing myself, y'know, the usual. And dying very far from your spawn just causes this ghosty glitchy lag-spikey... thing, to happen. It takes ages to really respawn.
Yeah... very broken. It's opposite day, it seems!
I'd have to back with Reece Cooper's solution. I followed the filepath to the .tmp file it gave me in the error report box, and then I renamed that to "Minecraft_staging.exe" and the old one I renamed and later deleted.
Yeah this is troubling... it's strange, especially for double slabs, where water cannot even be part of the block given that it takes up the full 1 m^3, but you still can't place water on the block, on any of its six faces.
Can back this up - I'm messing around with a survival world in End Generation Forest Hills Buffet. I think the way that Minecraft sets up the spawn location is based on randomly selecting a coordinate relatively close to (0,0) +/- about 200 blocks, something like that, but it doesn't check for land.
Definitely can confirm this in 18w11a:
Example:
Seed: -923760149
Tp Command: /tp @p -784 45.00 -2510 90 45
TP and you will see that the water falls and the lava falls, but then the lava stops magically above the water, doing nothing.
[media][media]
I can confirm this bug is still present, made a new world in 18w06a and the same issue spans over whole snow biomes:
[media][media]
I was just about to report on this - I'm no authority on the matter, but to me it looks like its own bug. I was just playing around underwater in 1.14.4 and noticed that the ambient occlusion doesn't seem to work facing the west direction for underwater blocks. Above water it works, and underwater it works facing north, east, and south, but not west. I just started up a new world and found this:
[media]