mojira.dev

CoalBuster

Assigned

No issues.

Reported

MCPE-65759 Furnace UI - Little visual error Duplicate MCPE-45270 Villagers do not link to the nearest bed/workstation Works As Intended MCPE-42950 Graphical overlap new villager UI Cannot Reproduce MCPE-38342 Auto-jump inside scaffolding not high enough. Cannot Reproduce MCPE-36863 Crops don't break in low light Confirmed

Comments

I think there's multiple things playing here. First of all: the toggle works, all the "press .. to open chat" messages disappear. Why this is still considered a bug can have 2 reasons I think. Either, people are unable to find said toggle, or, when the toggle is turned ON again, the hint is still unreasonably spammed in chat, where people would expect it to show up only once at the start or at least less often.

My guess would be that most people consider this "bug" fixed only when the whole "feature" is completely removed from existence, but I may be wrong. 🙂

IMO, the bug is already fixed.

Sorry, don't know exactly where the search for a similar issue went wrong. Better watch my filters next time.

Oi. Ai. My fault, that made the bot reopen it. Sorry Jay.

No, indeed not an issue anymore to my knowledge. Was fixed pretty soon after reporting for me.

Confirmed: This "bug" also applies to (Android) Mobile/Tablet. Here, only the toggle in the touch section needs to be set correctly. But it is easy to end up in the keyboard or controller section, and assume the toggle does the same. Though it might be useful for some people switching a lot between controller and touch for example to have these 'profiles', it can be confusing for most people (note: no expert).

Not fixed yet in beta 1.14.0.4 nor beta 1.14.0.6. Reproducible by placing a dispenser facing upwards, filling it with some bonemeal, topped with (multiple) grass blocks. Whether a flower, sapling or nothing is placed on doesn't seem to matter. When the dropper is powered it has a high (but not always) chance of crashing the game immediately.

Also happening on 1.11.1. Note that it also seems to happen when you initially join a world/realm.
Added a screenshot (thanks TigerPlaysMC).

As stated before, the issue has been fixed in the beta version 1.11 (1.11.0.8+). This is different from the stable version, which - at the time of writing - is still 1.10(.1). In the future please don't forget to mention the version in which you found the bug.

I can confirm the bug has been resolved in the 1.11.0.8 beta (at least for my hardware). Loading 2/3 of the shulkers from my enderchest into my inventory gives no to very little (unnoticeable) lag when opening inventory/crafting bench with crafting book opened. Hope it will hit the release soon.

After some more testing I'd say it is not on the loading of chunks, but saving of them. Cannot turn off auto save on Win10 so cannot really test/confirm it's that.

Experiencing same issue. This report might be the same as MCPE-43441.
I'm also experiencing "general lag" since 1.10. Up to this update the game has always run smooth like butter on my hardware (i5 7th gen, GTX 1050Ti, Win10).

Note that this is different lag than that caused by the inventory/crafting book, which is present since ~1.7 and got way worse in 1.10 (MCPE-27167 or MCPE-41772).

The best description of this lag is 'chunkloading'; it's mostly noticed on world startup and moving around. Where previously the chunks would load smoothly, now the game seems to struggle more with them and lag is caused. Also asking more of the CPU.
For some reason the bug doesn't seem to affect flat worlds. Flying over normal terrain causes the occasional yet frequent jitter. I'm unable to tell if a specific kind of terrain (dessert, ocean, plains, hills) or the presence of structures (villages, ocean monuments) has any effect on the lag experienced.

Another remark: as of 1.10, the lag no longer seems to be avoidable by closing the crafting book.

Has been present since 1.8 at least indeed, intensified in the latest 1.10 release. Only one filled shulkerbox now already is capable of making computers cry.

Pretty annoying visual glitch that has been around for a while (I think I've seen it also in 1.7). Placement dependent; up to multiple sides at the same time affected. Windows 10 Edition - 1.9.0.

Same issue experienced: leaves broken with shears are visually the same, but do not tend to stack with the same type of leaves mined using any Silk Touch tool (tested pickaxe and axe). This bug has been around longer than 1.8.1; I think since one of the Aquatic updates. Can't remember nor test since when exactly. Windows 10 Edition - 1.9.0.

Made a video trying to explain the issue; whilst confirming it's still present in 1.9.0.

Still present in 1.8.1 Windows 10. Lag happens whenever opening an inventory (for example personal inventory and crafting bench) that will also show the recipe book. Not having the recipe book opened or opening an inventory that doesn't show the recipe book (chest/enderchest/shulkerbox) will prevent lag from happening.

The type of stuff inside the shulkerboxes or the amount of shulkerboxes in your inventory doesn't seem to affect the amount of lag experienced; the amount of stuff inside the boxes does.

Just noticed on 1.6.1, Windows 10. With slow falling applied, I could still 'dive bomb' and get hurt.

Well, it seems you were able to reproduce the issue, as the issue I tried to describe is not that they don't pop off, but that it takes those 2-4 minutes you described for the crops to realize that the light is too low. In earlier versions they would pop off almost immediately.

I'm able to confirm this issue from happening (Win 10; 1.5.0.14). I've attached some screenshots showing before and after leaving in various situations I've caught happening constantly:

  • Sheep on track (with blocks); passenger floating.

  • Sheep off-track (without blocks); minecart floating.

  • Villager off-track; minecart floating. (actually lever on ground beneath cart)

  • Two villagers on track; one normal, the other floating (seems the latter didn't want to move yet).

I was also able to catch the sheep-situations on camera, but as the pictures already describe a lot I've left them out for now. Hope this helps to further describe the issue. Although it doesn't seem to break anything for me for now, I would still like to see this bug fixed.

Â