Twentydragon
- Twentydragon
- twentydragon
- Europe/Stockholm
- Yes
- No
4 issues
Key
Summary
Status
Reporter
Assignee
Created
MC-130505
Changed Description:
Upon loading up an extant world or creating a new one, the game mostly runs at 55-60 fps, but will intermittently and completely stop for 0.25 to 1.5 seconds. This does not seem to happen if the player stands still.
With the debug screen open, a single spike visibly causes the frame rate to drop to 27, 14, or even 0.
Pressing Shift + F3 to open the debug menu with graphs sometimes causes the game to crash with an unknown error.
EDIT 2018-10-24 22:24 - I just managed to get the graphs without a crash. Attached is the FPS graph showing one such spike.
Added Attachments:
Added Attachments:
Thanks for finding the original. I think we might have been filing these at the same time, because I couldn't find it when I searched.
I can confirm Viciarg de Gernande's observations, with the addendum that it does also affect blocks that the player is mining, especially if it drops an item to pick up.
I've seen this same issue in forests. One tree's trunk was completely replaced with dirt, as well as parts of my cobblestone wall. There are also vines sitting in bubbles in the middle of the ground beneath the forest, as well as a random line of growing bamboo towers.
Text colors have changed, and now even white text is darker and less visible than the light grey you show here.
The text colors were indeed much better and more readable when they were "too bright". White text should appear white (or at least light grey), as opposed to the medium to dark grey it currently appears.
I concur. It would be very useful if this feature could be disabled or remapped.
A workaround for now:
If you replace the affected air blocks (or air blocks neighboring the affected ones) with leaves through a command, the leaves will decay away and slowly return the lighting to the expected state. However, this is only temporary and leaves you with a lot of saplings, sticks, and potentially apples on the ground.
This does not work if you use a non-decaying block, as it will not update.
I had built a village near my base in my game (it counted for raids and everything), but when updating to 19w14a, all six villagers have completely vanished.
Also, this is a possible duplicate of MC-147474
I also had my villagers vanish, and they were in a village I built right next to my base. No raid, no lightning. I would have seen or heard either of those events.
The villagers were there when saving and quitting from 19w13b, and after converting the world to 19w14a, they were gone.
Well, that's unfortunate. As it stands, this makes spruce signs useless, as neither black nor white text is presently legible on them.
This occurs even when the villager is below solid (non-transparent) blocks like grass.
Example:
My villagers' beds are inside a room with a slab ceiling and a grass roof immediately above that. While inside this room, villagers will launch fireworks following a defeated raid.
I understand the desire for this bug to get fixed, but you have no way to know it was postponed "for no reason" (comments being deleted have no bearing on that statement; they delete unhelpful discussion so they can focus on the bug at hand).
Also, the workaround is simple: press Escape to close menus for now. It's not that difficult to get used to, even if I would rather just be able to press Tab to close it as normal.
The arrow keys also seem like a suitable replacement for using Tab.
Effectively, you could have both, and when Tab is rebound to open/close inventory, then Tab (and only Tab) would have its accessibility feature disabled. The arrow keys would still work as normal.
In text fields, this would have the effect of being able to focus into the field, and then to get out again, you would have to press up at the start of the text field (as it makes sense for the first press to act as Home on the first line) or down at the end. Left and right would simply shift between characters.
Now that villages appear not to simply despawn anymore, it's very aggravating to have 12 of your 13 villagers killed by a pillager and vindicator who have spawned inside
the village.
It shouldn't be terribly hard to get used to pressing Esc to exit menus. It's not ideal, but it's become second nature to me and only took a day or two.
This appears to have been intended behavior before, not a bug, but a recent video from Slicedlime indicates the behavior has been changed in snapshot 20w06a to now always prioritize repair.
https://youtu.be/GUZqS7vjP3Q?t=530