Richard Craig
Assigned
Reported
Comments
Agreed, THIS IS NOT RESOLVED! They deleted my own bug report on the issue. Are they removing VR support? Are they proving to us that Microsoft is going to ruin this beloved thing that has brought joy to so many? Are they trying to sweep this monumental screwup under the rug?
My in-game max is 56 chunks, but editing options.txt doesn't actually extend it any farther, even though my PC is more than capable. My Nvidia Shield TV has a max of 14, and it too won't extend any farther even if I edit options.txt to a longer render distance. The in-game options will show whatever distance I've put into options.txt, but the actual render distance is unaffected. I know from older versions that the Shield TV is more than capable of running as far as 30 chunks with no slowdown. It should be up to the user and not predetermined by some arbitrary calculation that's forced upon us.
Confirmed on 1.2.2 on Windows 10 and on Nvidia Shield TV.
Same issue here. When reloading a world, all parrots un-sit regardless of the owner. This also has the side effect of parrots sometimes disappearing if for instance the host loads, another player's parrot un-sits, then that player joins but is in a completely different location, at which point the parrot completely disappears.
I have noticed the same thing. All edges where blocks intersect don't appear lit properly, and lighting on segmented blocks such as fences show separate shadows on each rendered cuboid.
I can confirm that the 1.2.1 update that just rolled out fixes this issue!
My render distance is set to 56, and I still have this issue.
Likewise having the same issue. Seems to affect all mobs, hostile and passive. Saving/quitting and reloading or moving to the nether and back sometimes causes spawning to resume, but it stops shortly thereafter. I killed everything in the viewable area around my home base and have been playing for several hours uninterrupted, and not a single mob has spawned. Difficulty is set to Hard.
On Windows 10 and Android, it works like any other update and loads your previous worlds just fine, no hunting required.
I've updated to the 1.2 beta and am happy to report that I'm no longer having this issue!
All great points! I'm hoping that the unified nature of the Better Together update might entail some improvements to the DB system. And to be fair, I've been running at a 56 chunk render distance... Hate to scale it back as that's been a major part of how I explore my world, but it's better than ruining everything I suppose. Here's to hoping 1.2 fixes this even if this Jira ticket has gone ignored by Mojang... I'm sure this issue affects several aspects of performance.
I make regular backups, but that doesn't really help the problem of being unable to expand our world. If I have to keep reverting to a backup, what's the point in doing anything at all? It's certainly good advice to always keep a backup, though! I may just run the world on an old laptop as the host since it's only the host that experiences CPU spiking; my partner doesn't experience any lag on the same world, only me since I'm the host.
Having the same issue, and my world is slowly becoming unplayable. Why is this still not being looked at? This is a major, game-breaking bug.
Still not fixed and really don't understand why this was changed when it worked perfectly for years. Can't it just be changed back? This issue becomes six months old in two days. This was my favorite VR experience, and you've robbed us all of it through six months of a worldwide pandemic when we needed it most.