autouzi
Assigned
Reported
Comments
Thank you! It started for me after the 1.19.30.04 update along with MCPE-157192. The recent comments in MCPE-157192 mention BDS servers and realms and started after the same update.
A lot of the recent comments mention BDS servers or realms. May I ask if this is the correct place for the recent bug reports, or should it be reported in the section for BDS: https://bugs.mojang.com/projects/BDS/ ?
Apologies for the delay. Here are some screen recordings: https://imgur.com/a/5mUQtN8
Thank you for the response! Please note the dark shadows occur also on dirt blocks and trees, not just dirt paths. I did try the update to 1.19.31, but it did not fix the issue for me.
My world was created directly after the release of 1.18. I am having both issues. Some areas are fixed with a torch, other areas get dark again when breaking the torch. The issue happens in new chunks and in chinks I have fixed with a torch. My issue is only present in the BDS software, after updating to 1.19.30.04. The lighting bug does not occur when moving this same world to single-player, BDS only.
Please see above. The issue effects Windows and Linux BDS software, including Realms. I have already made a new big report that mentioned it does not effect single-player modes, but it was closed as a duplicate.
Reply from @unknown:
Yes, thank you for reminding me. There have been several "duplicate" reports lately, and we may decide to use one of them to track this presumably new problem, or we may decide to create a new report that combines them for the devs. Stay tuned.
I should have mentioned my BDS server is on Ununtu.
Thank you for your time! I moved my saved world from my BDS server to a PC and opened it as a single-player offline game. When doing this I cannot reproduce the issue, but moving the world back to the server causes the issue to come back. The issue is the same as above, dark shadows everywhere with a gradient on some edges, that go away if you place or remove a block. I cannot upload the second image, even after resizing, but please take a look at my original post MCPE-162513
I still think this is a separate issue since it is only occurring for me with the BDS software, but not in single-player mode
My post was closed. Please comment and vote on the OG post so mods will know this issue is worse in the latest BDS release. Thanks! MCPE-39439
This issue started for me after the 1.19.30.04 BDS update, but does not occur when I move the BDS world to single-player, so it is related to the BDS software in my case. There needs to be a way to update and clear cache for Bedrock worlds like in Java. I've had so many problems with Bedrock in the last two years, Microsoft should not market Bedrock as their primary platform when it is broken and buggy.
Happening since upgrade BDS to 1.19.30.04. This update includes several other bugs as well. What a shame.
Having this issue as well with the new 1.19.30.04 on a Linux BDS. Gets stuck at the loading screen after using a portal. Restarting the game spawns you in the nether but at the overworked coordinates.
This was also fixed for me in 1.19.40 BDS for Linux. Thank you for your help Auldrick!
Reply from @unknown:
You're welcome, but allow me to explain something. With millions of players, it's not practical for the bug tracker to track individual customer incidents the way a customer service site does. Instead, we're here to collect and consolidate your reports of bugs and pass them to Mojang. When Mojang fixes a bug, they notify all of us (usually) via the changelog, and that's when we normally mark a bug report as Fixed. So it's not really informative to notify us that it's fixed for you, unless you're the only person who has reported the bug. Instead, what we need is for you to let us know when it's not fixed after we mark the report Fixed. When that happens, we'll reopen the report and tell Mojang they need to keep working on it.
When multiple people have the same bug, it's possible that there are multiple independent causes. In that case, they may not all get fixed at the same time, so some people might find that it was fixed while others still have the problem. When somebody comments that it's fixed for them, the ones who aren't yet fixed might become concerned that Mojang will stop working on it (or has already stopped), even if we haven't marked it Fixed yet. They might even re-report the bug unnecessarily, thinking a new one is needed. For this reason, we would actually prefer that you not tell us when it's fixed for you (again, unless you're the only person reporting it).