Alexander D

I've been playing for a while now, the instant I was allowed back into my world.

I said it before in my excitement to finally bury this ******* terrible bug(s) plaguing the switch, and I was overzealous, but this time after waiting a bit and really fleshing it out I feel like almost all the issues for the Switch have been fixed.

The last true update that had Minecraft for the switch operating at absolute gorgeous prime, was 1.7. 1.8 was the update that screwed it all up, and we've been wanting to go back to the great levels of buttery smoothness of before. Playing in the nether and the overworld, I feel like that smooth gameplay is finally back, 

-No crashing, ever, at all.
-No lag during autosaving or any other times so far
-Chunk loading appears to have been improved dramatically. 

-Everything just generally feels smoother and nicer. 
-no bugs or quirks that pop up randomly. For ex, no lag when breaking blocks
-unsure if this was a bug relating to this specifically or not, but I was unable to use backups for my realm. they always failed. I emailed CS and other peeps to get help and went all over and they were flat out unable to help, so that it was fixed is freaking awesome for me.

I'm like, super impressed. I'd like to say to the mods that if a majority of players here (or at least most of them) feel like gameplay has been generally improved. I think having this ticket finally get resolved (yay) would be a good idea. It's 300+ comments over like 6 months of like tons of frustrated and upset switch owners. So if any small bugs here or there or anything new pops up or persists relating to general gameplay, a new ticket is probably way more helpful for everyone. Plus, finally seeing this getting resolved would be one of the highlights of my minecraft 2019 year LOL. 

Been a long time coming, but I'm really, really happy. My game plays so much better. I hope its the same for everyone else!

"so there are potentially a lot of people who are currently using cross-play and Realms without a problem

The problem with this assertion is that:

1) you are using upvotes as an affirmation from users as 'a problem exists'

2) this site itself is not well known amongst the general populace. seriously, it really isn't. even amongst the general internet populace who use twitter and reddit and 'frontpage' type websites and play minecraft, I'd wager very good money a large portion of them wouldn't know where to go to report bugs

This can't be used as any indication whatsoever, but nearly every person I've ever talked to who uses a switch experiences these bugs, sans one person. I got a call from my mom a few months ago when another update went online asking me why she couldn't connect to my world (lol). Can I use my informal 'mom call poll' to assert that 100% of switch users are experiencing these bugs? Where is the line you're drawing here?

People in the switch youtube community have been talking about this for months now (a majority of them do youtube for a living, so they simply switch their videos... to Java. Seriously, go scout out a few and ask them how they're doing bedrock vids on switch. (They aren't)). People have been complaining on twitter and reddit and all over. A member of the developer team says these bugs affect his own play at home. I'd feel it's safe to say a majority of users feel these bugs.

In fact, a vastly, vastly better metric than the one you proposed is measuring this issue against other issues. What kind of issues get these kinds of upvotes? What kinds of issues get 200+ comments? What kinds of issues are duplicated by 48 separate ones? Also - you counted upvotes here, but are we going to count upvotes in the duplicated issues? Plenty of people probably upvoted or found those issues but not this one. Each duplication should count as at least one upvote - the OP/thread creators one. 

I bet if we compare the relative impact this bug and issue tracker has to other issue trackers, we can find a semi-reliable way of measuring community impact. Also, Ali's post has merit because a lot of the stuff he is talking about desperate switch users are trying out themselves I mean it's bonkers lol. I even tried to not update my game when 1.12.0 came out, but once Realms turn over, that's it for my world. Unlike other versions of Minecraft, there is no 'rolling back' your version. We don't get to play on Java 1.12.2 or 1.17 like the majority (the majority of the modded/'elite' minecraft community) and get to pick and choose when was the best, most convenient time for us to play. It sucks ass and it points to just how garbage this is and how tired everyone is of waiting. People are desperate to gimp their games just so they can play for a few minutes. People are desperate and distrust any single update MJ pushes out so they're trying not to update. Again, this is "hearsay" (although I can provide screenshots from forums/reddit/chan/etc if necessary) but Ali isn't the only one who talked about 'guys, just don't update to the new version' when it came out.

Like I said, these are bedrock users, not java ones. When you have bedrock users talking about that, you got serious problems, mang. 

So I was talking to an old friend last night and he told me he had horrific issues on the Switch basically since 1.8.0. However, he says since purchasing a realm last week, he has absolutely 0 issues. I talked to him about all the issues that I have. He doesn't have any. Lag, stuttering, framerate dips, nothing.

I say this in context of the thread above: they were asking for peoples usernames and realms so the developers could take a look. I was simply wondering if it would be useful at all for the team to take a look at his realm? I don't do the job of these coders, so I have no idea what is useful and what isn't. I thought perhaps they would be able to compare his seemingly "good" realm with a seemingly "bad" realm or world, and be able to pinpoint differences? Like "wow, this happens here in world X but doesn't happen in world Y, maybe we can investigate this".

Anyways I don't have a reddit account and never will, but if there is someone I can contact, or put in contact with him, or give his e-mail (again, if this would be helpful at all) please let me know! Dear God this has been running on for nearly... One third of a year now, so anything to help bury this ****ing terrible bug(s) ravaging the switch. 

No, I play a multiplayer realm that usually has 2-3 people on it (around 8 in the evenings when we all play). I host the realm. 

Also do you mind editing your posts in the future instead of constantly double and triple posting? It makes the thread easier to read. Thanks. 

Muting the chat did absolutely nothing for me. 

If it helped you, it's honestly probably entirely placebo. I can't really imagine a bug with the chat interacting with the framerate to cause these kinds of issues (plus the freezing, plus the loading issues, plus everything else) and would place my money on the issue being elsewhere. 

Hey Isiah. This bug affects literally almost every single Switch out there. Been getting worse since 1.8.0. Every version 1.7 and previous was a-ok.

The community members are tracking it here:

https://bugs.mojang.com/browse/MCPE-41479

Please add any new info there, and make sure to upvote the issue and follow it for new updates. That bug tracker is the only place we've ever gotten mods to properly respond to us.

Auldrick, how are bug reports not sorted by platform when you literally need to input a platform I.E, Switch, Xbox One, in order to upload a ticket? (Which are then sorted by service, as I stated, such as bedrock or Java)?? I mean, lol. 

>I didn't have as much a problem with this compared to what people here are saying

Maybe that's because we play on the Switch, while you play on Windows 10? This gamebreaking glitche(s) and bug(s) have been confirmed to be plaguing the Switch version of bedrock since the 1.8.0 update? You realize these bug reports are sorted not just by service, but by platform as well? This bug report (which has been duplicated by like 45 different links, including over 10 on the front pages that haven't even been linked yet) is for the Nintendo Switch. 

I'm kind of rolling back my previous content. While seemingly singleplayer was improved in 1.10.0, glaring flaws shined through. While it has turned it from literally unplayable to "well, this is okay", lag is horrific when opening chests. Autosaving seems to be hit or miss for players as well, being an issue for some and not others. The buried lede here is multiplayer.

Doesn't matter if it is online or local multiplayer. The lag is atrocious. Unplayable in every meaning of the word. Below is a laundry list of issues encountered:

• Chests taking 1-2 minutes to open (can be worse during autosaving)

• Constant freezing of 3-8 seconds, occasionally longer, encountered anytime. Reproducible simply by playing the game for longer than 5 minutes.

• Breaking a block like wheat, dirt, whatever, the block will break and seem gone, but nothing will drop. A minute or two later the item will finally drop and you can pick it up, albeit with significant lag

-Breaking a block, like above, but instead of the item dropping, occasionally you will get this issue where all the blocks simply reappear instead

• Placing blocks will sometimes give you an issue where all the blocks you place are invisible. Takes 1-2 minutes to appear.

• Placing blocks will, alternatively, give you an issue where you can place the block, it appears, you stand on the block and continue to build... Until all of a sudden every block you've placed down disappears (in order of which you placed them), and then you fall (often to your death)

• In what will likely become a fan favorite gamebreaking bug, occasionally every mob (villager, rabbit, wolf, zombie, anything) will freeze and pivot back and forth in place. Attempting to attack the mob (zombie) will result in damage appearing for a split second and disappearing. If you have, for example, fire aspect, they will be lit on fire for half a second but it'll disappear. Attempting to trade with villagers, nothing will pop up. This often goes on for up to three minutes. Suddenly - all the mobs will move in erratic, fast forwarded fashion, making up for the lost minute(s). Some will trace a huge path, running up and down several chunks at once and even skip multiple frames from going so fast. The trade will finally open/the zombie hit will conspicuously die. If you were hit during that time (impossible to know if a zombie, or creeper had wondered in during this 'lag freeze' issue) you will suddenly take multiple hits. You can take 2, 4, 8 hearts of damage. I've even died this way by having this issue occur in a mineshaft with multiple spiders. When the freeze stopped, I suddenly heard audio for multiple hits, found myself poisoned, and I immediately watched my hearts drop to 0 and I died. This glitch is essentially endemic to the multiplayer experience now.

 NOTES: Turning down anti-aliasing does nothing. Doing different features does nothing. Playing local or online multiplayer changes nothing. All of this was tested with multiplayer with 2-3 people, all on the switch, one on PC. Glitch occurs on new worlds (smaller than a few MB's) and big worlds (150+ MB). 

COMMENTS: Overall, multiplayer was literally better somehow on 1.9.0. I genuinely believe, because there is no other option or alternative to believe in, that this was obviously known during playtesting for 1.10 but the devs and team released it anyways. There is no way 1.10.0 got released. I'm sorry, but just because 'this is a hard bug to fix' doesn't cut it when we are paying a premium to play this game on the Switch compared to PC. Most, if not all of us who have this on the switch play it nearly exclusively for multiplayer. Why else buy a game that all of us have on every other platform, on the very newest console out there? This is a sad situation. 

And honestly, you'd think a gamebreaking bug would have the devs go like "Well, we have to fix this FIRST and IMMEDIATELY'. Instead, being told "Well, sometimes we fix the little things because it's easier!". Lol. That's hilarious. Super epic that the dev team will focus on fixing something like a bug that occurs when placing an item on a stand, rather than, I dunno, the bugs that render an entire population of bedrock users and an entire platform from being able to access core gameplay. Again, this is just Microsoft signalling their priorities.

WORKAROUND: Buy a realm. No, seriously. When I had heard there was some sort of issue with the servers, a thought popped into my head. "It couldn't be!" I said to myself, but I had to confirm what kind of issue the servers were having. Since the issues appear to be happening exclusively on the normal servers accessed during free play for multiplayer, but not for paid play/realms, it's pretty clear what issues Mojang is having. I'm laughing really hard right now. Would absolutely LOVE a dev/mojang or microsoft rep to come down here and explain exactly what this online issue is. Seriously, I bet the F2P peeps would love to know. Hilarious stuff you guys. 

@BRYCE: Toycat is great. You know why he doesn't have any issues? Read the above paragraph. Yep - he has a realm!

Hey Auldrick. Thanks for all your replies and the work you've done on behalf of the users. I know for many people, especially for me, volunteers and mods such as yourself often tend to be the first point of contact for the playerbase, so when we get someone who reaches out on our behalf such as yourself - it goes a long way. Don't want to ramble so that's all I say on that but thank you.

Feel like I shouldn't have ranted as hard as I did earlier, but seeing 1.10 finally come out and "seemingly" no fix for this report was frustrating. Obviously you've explained to us now a little bit about how the ticketing system works and why it wasn't initially shown in the changelog. My bad! Hearing that things should get better makes me really happy. 

Anyways - can't wait to test out 1.10! I'll report in this thread (I feel a slight duty to, considering my earlier posts from a few week(s) ago pointed out a lot of problems) what I think got fixed over a quick 1 hour playthrough. And as you said, if there are any new problems, creating a new ticket is probably best. If gamebreaking lag is still a thing we can all discuss here again of course, but from the looks and sounds of it, Bedrock for the Switch is now running a lot smoother! I'm excited to play. Thanks to everyone for all the work finally resolving aspects of this bug! And thanks for taking our complaints in stride, Mojang moderator team members! Like I said before, it goes a long, long way! 

EDIT: 1.10.0 TESTING: 

I'l be updating this section as I go along. Not because I think everyone needs to read my thoughts, but just thought as a resolution to the thread would be nice. Loaded into the game - once everything loads, character moves smooth as butter again. Fantastic! In areas where you've loaded the chunks fully, movement and framerate is as smooth as ice. There is, not what I'd call 'stuttering', but perhaps a very small framerate drop when running and loading new chunks very fast. However, this has so far in 20 minutes of gameplay not caused any crashes, which is good. The chunks are loading noticeably faster than before.

Autosave function - that (separate ticket I think?) appears to be fixed! Game has autosaved for me many times and it has not slowed my game down or caused a crash. 

Overall, gameplay seems improved on switch. Obviously it can be optimized, but this is very far from the unplayable state of 1.9.0. Very far away! Game is completely playable and I can't wait to dive in and play for 8+ hours now LOL. I will report back with a few things I am looking to test, however. Such as playing in an area with over 50 mobs (villagers, pigs, etc) when it rains (this often caused me horiffic lag spikes and framerate drops) and general gameplay when loading chunks fast on a horse and travel (exploring in 1.9.0 on Switch was untenable. Especially in the ocean. You might be waiting in, quite literally, a sea of nothingness for one minute before even the chunk you are on loads. Not an exaggeration. So far this appears to be fixed but would like to stress test the game a bit)

So happy right now. What was at least 70-80% of the issue is gone. 

Second comment: (You can append this to the first post if you want Mods, just wanted to be more clear). I noticed one issue with the game. Likely related to just the gamebreaking lag in general.

My game freezes often when the autosave happens. This isn't what I noticed. What is possibly new is that my game tends to stutter worse or flat out freezes when I tie multiple mobs to a lead. It happens almost every time. Leading like 3 or more dogs, cows, alpacas, whatever, will cause my game to freeze.

Obviously this is heavily related to my above post of bugs and issues I've noticed, but I have no idea what is or isn't helpful to devs, so I figured I'd mention this.

Auldrick, here is the problem.

I have been directed to multiple places. I know this isn't "the place" to air grievances. Fine. I've respectfully done so on twitter. I've done so on Discord. They refer me to here. If I tell them I can't do anything here, they just mute me. They don't take anyone seriously and find it annoying. I post about it on the other site that specifically is aimed at taking suggestions/comments for the game. They don't even give me the decency of approving the post for others to see the thread.

Here's the problem with what you said: yes, the devs may only have a specific amount of time. They fix little issues. But this is an issue that affects thousands of players. It has now been constant, unplayable, crashing, horrific lag for, as of right now, over a month. We've all been patient. We've been messaging discord mods. You guys here. Trying to talk to people on the other sites. Nothing. Ignored or told to wait.

How do you guys not see the optics of this? Anyone who purchases the game now will see how terrible it is and never play it? My friend got a refund from nintendo. I have never heard of Nintendo giving refunds for games like this. Only completely broken games. That is unbelievable to me.

Heres the issue. We've all been screaming for a hotfix, or to roll it back. If the fix will take over a month or even half a year? Who knows at this point. Players would rather play with LESS stuff but have a REAL experience, than be able to go "Wow, I made a campfire. Oops, I crashed for the 50th time. Teehee!"

Here's my own issue with your words. If the devs only have so much time, you think they would focus on a GAME BREAKING BUG that affects AN ENTIRE CONSOLE PLATFORM. What are we paying DOUBLE for? Why did Microsoft purchase Minecraft? You can't seriously, genuinely tell me with the influx of cash that somehow devs are stretched for time.

Nope, what's being signalled here is priorities, and Microsoft, Mojang, and others telling everyone on the Switch: Sorry. You are not a priority. I apologize to you mods. I understand you are volunteer moderators. This is NOT your fault and I do not blame you. But our frustrations are very real and we can't air them anywhere else. This is the most upvoted and pressing issue for the Nintendo Switch and Bedrock users, and now we're being told, after being told to wait for the next update, nothing is being done. This is akin to spending money on a game and not even being able to PLAY it for a month. Actually, that's exactly what it is.

There's no way this bug passed playtesting. It just didn't. People were aware of it and didn't care and it frustrates me. If Microsoft seriously can't fix this or roll it back in a month, we genuinely deserve either a full explanation from a developer WHY this is happening, or we deserve refunds. I don't want to go to Nintendo and go through all that... But I can't even PLAY this game. It's unbelievable and very striking how little is being communicated to the users who essentially support this game with our time and money.

Again, I'd like to suggest rolling the update back. I actually DID submit feedback at feedback.minecraft.net, and it was just a couple of lines asking the devs for more information, but it never got posted. Seriously, we are continually hearing that "we think it may be X, but right now have no ETA for update...". When I first posted, it was a week. Then two weeks. Now over a month. Now I clearly see this issue may persist for many months now. In fact, they may just roll out the full Pillage update without initiating any hotfix. You can clearly see this is one of, if not the main issue affecting the Nintendo Switch. I'm really trying hard to be nice and no insults and everything in my posts, but its so unbelievably frustrating. When the update first hit I thought "this is so bad, no way they'll let their entire Switch fanbase play like this for too long" and now it's been a month and...

It would be great to get some communication from Mojang, or even anyone, the devs, on a few things. One being - how long are we going to wait? Two - if rolling the update back isn't feasible, please just explain why and give us something to hold on to. You can clearly see from this thread alone that it's pretty much affecting everybody, and that most people are literally saying they aren't even going to play the game anymore. 

Anyways, since Mega Spud seems to be taking the helms on this one, I wanted to ask you - going to have a big play session on the weekend (Friday, Saturday). Will be playing alone for a few hours, then my friend will come over to my house and we will be playing together (We can play both online and locally). On saturday, we can even invite other friends to join our world (one plays on switch, another plays on his laptop). 

Is there anything you want us to test out? Some workarounds you guys have been testing? You know from my post all the issues I have and can test out and what we've already tried. If there is anything else you want me to write down after the weekend in an update, we can do that too. Let me know the types of things the devs find of particular use (I.E- feedback they find useful and feedback they don't find useful) and it can instruct me better to provide potential new feedback to the developer team. 

We can test all sorts of things in different tiers. I play in docked mode on switch, friend plays in mobile mode. We can test multiplayer when its local, we can test it online with fellow switch users or even crossplay. I will still report back anything new or interesting I find out, but if there's anything that could enhance our (likely 24+ hour play LOL) time, let me know.  I'd literally do anything that could help finally kill this/these horrible bug(s). 

"Please remember that there is not always a simple fix that will resolve the issue immediately"
There actually is though, and it's quite literally what's been suggested over and over - rolling the update back. If the "problem is not an easy one and may take long to fix" do you know what's better than having your players play a laggy, unplayable version of the game for a month before you finally initiate a hotfix? Rolling the update back to the last playable version, so people can play the game for that month.

I'll add more information, but just like my last post, (and like how Mojang makes duplicate issue threads """"""""resolved"""""" instead of the more accurate term "duplicated", because it looks better) this will probably be hidden no matter how relevant any info I post because it's not 'nice enough'. But, regardless, here is a summary of the issues that I alone have experienced all in one single world. Here is some new, relevant information about the BUG only 🙂

-Horrific Lag, stuttering
-Toggling features of the world makes no difference (turning off clouds, draw distance, etc)
-Size of world makes no difference to lag (tested with main world (98mb) and three new worlds, one was explored (43mb savefile) and two newer fresh ones (15mb each)

• Item frames makes no difference to lag
  -Playing in docked mode seems to be worse. Playing handheld mode still experienced all of the above, but maybe seemed to be less active? Unsure
  -Game likes to freeze when things get messy. At night when it rains and you're in a village, game likes to stutter and lag even worse. Sleeping helps.
  -Game likes to freeze specifically when it tries to autosave. Sitting still ""fixes"" this in that it is less likely to freeze, but can still occur. Game did freeze once when I was sitting still doing nothing, but it's less likely than when you are moving around.
  -Game likes to freeze when opening chests or inventory during lag spikes.
  -Issue with loading both chunks and chunk sections. Not only is it incredibly slow (I.E, walking or riding up to a completely invisible chunk, mobs appearing visible "floating" in a sea of white) it causes issues with the game. When the chunk finally loads strange issues can occur.
  -LOSS OF MOBS! This is one I noticed last night and may or may not be related to the bug specifically. When experiencing horrible lag and a potential "crash", IE, frozen screen, I left my switch running for a few minutes. Sometimes the game stays frozen forever, sometimes after a few seconds to a few minutes, the game will unfreeze. When this happens, strange bugs can occur in the world such as unloading mobs in your area. I had three horses wearing diamond armor attached to leads in the backyard of my house. After this, I went back and one of the horses had completely despawned. Looked all over, even dug under the world to see if he "glitched" there. The funny thing is, his lead still was attached to the post. As in, the rope and lead itself was gone, but the texture of the "rope" being tied to the post was still there. Just that and nothing else, and 'releasing' the lead did nothing (and caused the lead to disappear completely. It did not drop). this is very common with my animals like Horses and Donkeys, so far. 

That's most of the helpful information I can offer. Here is some info that I feel is more unreliable, but may be useful to see what other people have seen or experienced with them, to see if maybe some of these things have happened to them.

-Playing with a friend LOCALLY, had a completely normal time. I had warned them when they came over that our Minecraft plans for the weekend were FUBAR'd. However, we go into my world, he connects locally, and... My world acts fine? I mean, by no means has it reverted to 1.8.x levels of smoothness and visual clarity, but the stuttering is mostly gone and the lag is more of the usual type of lag that pops up every now and again. There was absolutely 0 game crashes.
-Playing with a friend ONLINE is hit or miss. Played with two friends and my game had horrific lag, and so did my other friends, but my third friend was mostly fine. When the third player logged out and it was just me and my other friend, our lag levels seemed to die down. So when we play together in a maximum of 2, it was generally okay. Again, playing with two players I didn't experience game crashes. Playing with three players, the issues were very close to crashing the game multiple times (screen freezes for more than 4, 5 seconds during autosaves, etc)
-The smoothest gameplay I can accomplish in minecraft right now is: playing by myself, locally (doubt it makes a difference but whatever) and mining in the ground. Game has never frozen when I've been mining. Game has frozen multiple times when going to and from the mine. But when I am down in a mine or small cave system, mining stuff or even strip mining, there tends to be 0 issues at all. Once you get back out of the mine, it can be hit or miss. Your "smooth" gameplay can stay for a bit or it can get laggy again. It all eventually comes back, but yeah. You'd think, based on this, that the issue is with the entities/particles on screen and you could work around the lag and crashes by toggling things like lighting and bobbing off, but like many others who have done this, I have done this as well and it makes no difference. For example, I had a mining sessions playing on a fully gimped, simple, everything turned off/lowest render distance settings. Mining was fine. Coming out of the mine and running, loading chunks fast, caused the lag to reappear. Game crashes occur just as often. Turning everything back on changed nothing. It didn't cause the lag to get notably worse, it still existed, and going back into the mine made the game run normal again.

I'll update this post rather than make a new one whenever I find new bugs or anything related to the lag, what makes it worse, what may cause it, etc. 

1.9 has made the game completely unplayable on the Nintendo Switch. This honest to god warrants a refund for any current owners, because the game is completely unplayable. All the major issues that seem to be affecting the nintendo switch only, like 'spawning into your world only to die immediately', or 'waiting 5 minutes to load your world', or '1.9 update causing horrific stuttering or lag spikes nearly constantly', you can't play the game at all. What is the point of playing for an hour only for the lag to get so bad your game freezes, and when you log back in, the game kills you and you lose 30 levels and all your stuff? Mojang, this is truly terrible.

The game is completely unplayable! UNBELIEVABLE stuttering just when looking around your world! I have also had my game randomly frozen two times, one of them resulted in the complete loss of my best horse and diamond armor and a saddle! What is the point of updating your game and making it slower? How can you push out an update that makes the game unplayable for so many people and not catch it beforehand? I have requested a refund from Nintendo even though I know 99% they will not give it to me, even though the rep told me that refunds are given in cases of 'theft or the game cannot be played on the system'

Well, technically, this game can NOT be played on the Nintendo Switch right now. Is there any way to go back to the previous update? Because I've only had the game for a week, and I've barely played it and when the weekend has finally arrived and I have time, it's completely broken? What a waste of money.