mojira.dev

Smyon Pa

Assigned

No issues.

Reported

No issues.

Comments

I experience similar problems on Windows 10. The well-running world under 1.17. became unplayable after an update to 1.18.0 with effects described in other posts, e.g.:

  • Block disappear after mining but reappear back after several seconds. Sometimes the particles from mining appear later and the block is dropped after a few 10 seconds. 

  • It's impossible to place a torch or a bed most of the time. 

  • The attack doesn't have any effect on mobs. 

  • Pressure plates have a significant delay. 

There are usually 2-3 other players connected via the LAN, however, even after their logout, the lag was still there. Similar lag, although shorter - up to 10 seconds- appeared from time to time for the fresh started world.

I de-activated "fancy graphics" "fancy leaves" and a similar option decreased "render distance" to 10. However, it seems the rendering itself is ok. Even during the lag, I have a constant FPS of around 50.

There was a partial solution that helped in my case:
1) reduce the simulation distance - in my case to 6 chunks.
2) I killed most of the animals in my farms (I had almost 200 animals there). My base is very close to the spawn point, if these chunks are active permanently, it maybe contributed to lag.

It seems the world is playable again. The lag appears only from time to time for several seconds. Nevertheless, it always appears for the first 10 seconds after the "night" when players wake up from beds.

The issue appeared at Windows 10 (bedrock) platform immediately after the update to version 1.16.220. All old paintings are invisible (and if they are broken and placed as the new paintings they remain invisible). With 1.16.210 were paintings ok. 

I could confirm the same issue for Bedrock Windows 10 version 1.16.220 with a portal used many times without any problems until today (in the world played for the last 3-4 months - most probably it was created with version 1.16.201). I entered the portal in the overworld at coordinates 335,82,-95. The portal is normally linked to the one in Nether at coordinates around 29,71,-12 and was working reliably until now.  However, this time I appeared in Nether at coordinates 335,87,-95 (i.e. more-less the same coordinates as its overworld counterpart).

The minor issue (besides the troubles with the incorrect position of the portal) was that the newly created portal in the nether (the unexpected one) - was not shown. The portal was probably there since the block of obsidian appeared after an attempt to place another block at the position where the portal was located. After the reload of the game whole portal was shown correctly.

I entered the portal a few minutes after the game was started and there were quite unpleasant lags - the game was slowed down few times for few seconds with stopped graphics. Even the transfer from the overworld to the nether took an unusually long time.  Thus maybe it could be indeed related to some autosave as discussed above. 

Extra notes: The issue described above appeared shortly after the game was started. After the start of MC there was shown a message on an update to 1.16.220. However, the same issue happened to another player in the same world mentioned above (accessed via LAN multiplayer from Bedrock for Android version most probably still v. 1.16.210) a few hours before the update at host game at Win 10 was loaded. In this case, it was much less convenient - the player entered the overworld roughly at coordinates 1544,77,-670 and was thrown in the nether to -1930, 107,327. After the next use of the portal, the player appeared at skyblock with x coordinated around 15500. However, also in this case it happened few minutes after the game was started.